mahdirahani

Collaborative Post Notes is a simple but powerful internal communication tool for WordPress teams. 
It adds a clean, threaded note system inside the post/page editor, allowing editors, authors, and content teams to communicate directly while working on content — with no external tools (Telegram, WhatsApp, etc.) needed.
This plugin improves your editorial workflow, reduces miscommunication, and keeps all discussions connected to the content they belong to.
<h3>🟦 Why use Collaborative Post Notes?</h3>
Managing content in a team often leads to scattered messages across multiple platforms. 
This plugin solves that problem by keeping all notes, replies, and discussions inside WordPress, right inside the editor.
<h3>✨ Key Features</h3>
<ul>
<li>Threaded (nested) notes — reply inside discussions like a mini comment system </li>
<li>Internal-only — notes never appear on the frontend </li>
<li>Lightweight — uses minimal database space, optimized for speed </li>
<li>Auto-recorded username & timestamp </li>
<li>Perfect for editorial and content teams </li>
<li>Supports posts and pages </li>
<li>Clean, distraction-free UI </li>
<li>No configuration required — works instantly</li>
</ul>
<h3>🟩 Ideal For:</h3>
<ul>
<li>Editorial teams </li>
<li>Multi-author blogs </li>
<li>News websites </li>
<li>Agencies with content workflows </li>
<li>SEO/content strategy teams </li>
<li>Anyone who collaborates inside WordPress </li>
</ul>
<h3>🧩 How It Works</h3>
<ol>
<li>Open any post or page </li>
<li>Scroll to the Team Notes metabox </li>
<li>Add a top-level note or reply to existing ones </li>
<li>Notes automatically store user + time </li>
<li>Everything is saved with the post</li>
</ol>
<h3>🔒 Private & Secure</h3>
These notes are not public, not accessible through template files, and never appear on the frontend.

Collaborative Post Notes

A lightweight, threaded internal notes system for WordPress posts and pages. Perfect for editorial teams, content creators, and multi-author websites.

10up

Jeffrey Paul

Josh Levinson

observerteam

brs14ku

Eight Day Week provides a set of tools to manage your print workflow directly in your WordPress dashboard–right where your posts are!
Primarily, it offers an interface to group, label, and manage the workflow status of posts in a printed “Issue”.
Features:
Create “Print Issues”
<ul>
<li>Add and order sections, and articles within sections</li>
<li>Assign article statuses specific to your print workflow</li>
</ul>
Limit access to Print Roles
Two custom roles are added by this plugin to best model a real-world print team.
<ul>
<li>The Print Editor role offers full access to the creation interfaces, such as Print Issue, Article Status, Print Publication, etc.</li>
<li>The Print Production role offers read-only access to a Print Issues. The XML export tool is also available to Production users.</li>
</ul>
View a Print Issue in “Read Only” mode
<ul>
<li>Circumvents the post locking feature by offering a read-only view of a print issue</li>
</ul>
XML Export to InDesign: Classic Editor vs. Gutenberg Exports
When exporting content from WordPress for use in InDesign, there are key differences between Classic Editor and Gutenberg (Block Editor) exports. This section highlights how each type of export behaves in InDesign and offers guidance on how to handle these differences.
<ul>
<li>Classic Editor exports use basic HTML tags like <code></code>, <code></code>, and <code></code>, making them straightforward for import into InDesign.</li>
<li>Gutenberg exports include additional metadata such as HTML comments (<code></code>) that define block-level structures, which may require manual adjustments after importing into InDesign.</li>
</ul>
Import Differences:
<ul>
<li>Classic Editor: Imports cleanly into InDesign without extra metadata.</li>
<li>Gutenberg: May include block-related metadata, requiring users to clean up the imported content or manually adjust formatting.</li>
</ul>
Recommendations:
<ul>
<li>Classic Editor: Best for simple imports with minimal manual work.</li>
<li>Gutenberg: Recommended for users comfortable with removing metadata or adjusting block-based settings after the import.</li>
</ul>
<h3>Filters & Hooks</h3>
Eight Day Week provides a number of filters and hooks for customizing and extending the plugin.
Modules
Eight Day Week follows a module-style approach to many of its features. These can be turned on or off via filters, and all work independently. 
These are: 
Article Byline 
Article Count 
Article Export 
Article Status 
Issue Publication 
Issue Status 
Any of these can be disabled by returning a false value from the following filter format:
<pre><code>add_filter( 'Eight_Day_Week\Plugins\load_$plugin', '__return_false' );
</code></pre>
The <code>$plugin</code> value is a slug version of the plugin name, i.e. article-byline.
Article Table
The information displayed in the list of articles within a Print Issue is filterable. Custom columns can be added via the following filters: <code>Eight_Day_Week\Articles\article_columns</code> and <code>Eight_Day_Week\Articles\article_meta_$column_name</code>.
Sample usage:
<pre><code>add_filter( 'Eight_Day_Week\Articles\article_columns', function( $columns ) {
 $columns['byline'] = _x( 'Byline', 'Label for multiple, comma separated authors', 'your-text-domain' );
 return $columns;
} );
add_filter( 'Eight_Day_Week\Articles\article_meta_byline', function( $incoming_value, $post ) {
 return implode( ', ', wp_list_pluck( my_get_post_authors_function( $post ), 'display_name' ) );
}
</code></pre>
Print Issue Table
The information displayed in the list of Print Issues is filterable. Custom columns can be added via the following filter: 
 Eight_Day_Week\Print_Issue_Columns\pi_columns. Note that this is a convenience filter, the base filter is <code>manage_edit-print-issue_columns</code>. See <code>includes/functions/print-issue-columns.php</code> for sample usage.
Article Export
The export of posts in a Print Issue is highly customizable, from the file name of the zip, to the file name of the individual files, to the contents of the files themselves. The best reference would be to read through <code>includes/functions/plugins/article-export.php</code>. <a href="https://github.com/10up/eight-day-week/wiki/Sample-Eight-Day-Week-filters-for-the-Observer" rel="nofollow ugc">Here’s</a> a few examples used on the Observer.
Sample Eight Day Week filters for the Observer
Examples from Observer’s eight-day-week-filters.php:
<pre><code><?php

add_filter( 'Eight_Day_Week\Plugins\Article_Export\xml_outer_elements', function( $elements, $article ) {
 $elements['subHeadline'] = get_post_meta( $article->ID, 'nyo_dek', true );
 return $elements;
}, 10, 2 );

add_filter( 'Eight_Day_Week\Plugins\Article_Export\xml_outer_elements', function( $elements, $article ) {
 if( function_exists( '\Eight_Day_Week\Plugins\Article_Byline\get_article_byline' ) ) {
 $elements['byline'] = \Eight_Day_Week\Plugins\Article_Byline\get_article_byline( $article );
 }
 return $elements;
}, 10, 2 );

add_filter( 'Eight_Day_Week\Plugins\Article_Export\xpath_extract', function( $extract ) {
 $extract[] = [
 'tag_name' => 'pullQuote',
 'container' => 'pullQuotes',
 'query' => '//p[contains(@class, "pullquote")]'
 ];
 return $extract;
} );

add_filter( 'Eight_Day_Week\Plugins\Article_Export\dom', function ( $dom ) {
 $swap_tag_name = 'emphasized';

 $extract_map = [
 'strong' => [
 'solo' => 'bold',
 'inner' => 'em'
 ],
 'em' => [
 'solo' => 'italics',
 'inner' => 'strong'
 ],
 ];

 foreach ( $extract_map as $tag_name => $map ) {
 $nodes = $dom->getElementsByTagName( $tag_name );
 $length = $nodes->length;

 for ( $i = $length; -- $i >= 0; ) {
 $el = $nodes->item( $i );
 $emphasized = $el->getElementsByTagName( $map['inner'] );
 if ( $emphasized->length ) {
 $em = $dom->createElement( $swap_tag_name );
 $em->nodeValue = $el->nodeValue;
 try {
 $el->parentNode->replaceChild( $em, $el );
 } catch ( \Exception $e ) {

 }
 continue;
 }

 $new = $dom->createElement( $map['solo'] );
 $new->nodeValue = $el->nodeValue;
 try {
 $el->parentNode->replaceChild( $new, $el );
 } catch ( \Exception $e ) {

 }

 }

 }

 return $dom;

} );
</code></pre>
<h3>Known Caveats/Issues</h3>
Gutenberg exports 
Gutenberg-based exports include some additional metadata/details that a Classic Editor-based export does not. <a href="https://developer.wordpress.org/block-editor/key-concepts/#delimiters-and-parsing-expression-grammar" rel="nofollow ugc">Gutenberg stores block data in HTML comments</a>, so you’ll notice those comments (in the form of <code></code>) appearing in the Eight Day Week XML export. Note that the XML is still valid–you can test and confirm that yourself using an <a href="https://www.xmlvalidation.com/" rel="nofollow ugc">XML validator</a>–though depending on your version of InDesign you may get different results upon importing a Gutenberg export compared to a Classic Editor export. Our testing showed that those HTML comments in a Gutenberg export did not affect the import into InDesign however. You can test how this works in your version of InDesign with these sample XML files: <a href="https://raw.githubusercontent.com/wiki/10up/eight-day-week/BlockEditor-sample.xml" rel="nofollow ugc">Gutenberg XML</a>, <a href="https://raw.githubusercontent.com/wiki/10up/eight-day-week/ClassicEditor-sample.xml" rel="nofollow ugc">Classic Editor XML</a>. You can also test how this works with full ZIP exports of Print Issues containing a <a href="https://raw.githubusercontent.com/wiki/10up/eight-day-week/BlockEditor-SampleExport.zip" rel="nofollow ugc">Block Editor sample</a> or a <a href="https://raw.githubusercontent.com/wiki/10up/eight-day-week/ClassicEditor-SampleExport.zip" rel="nofollow ugc">Classic Editor sample</a>.

Eight Day Week Print Workflow

Optimize publication workflows by using WordPress as your print CMS

Collaborative Post Notes vs Eight Day Week Print Workflow