build\/assets\/<\/code>. The corresponding human-readable React, TypeScript, and CSS source code is publicly accessible at:\nhttps:\/\/github.com\/Veridis-Dev\/veridis-news-desk<\/p>\n\nProduction asset mapping:\n* src\/AdminApp\/main.tsx<\/code> -> build\/assets\/app-*.js<\/code> and build\/assets\/app-*.css<\/code> (Newsroom React workspace)\n* src\/EditorApp\/main.ts<\/code> -> build\/assets\/editor-*.js<\/code> and build\/assets\/editor-*.css<\/code> (Block Editor sidebar)\n* build\/manifest.json<\/code> maps hashed Vite asset filenames for WordPress runtime loading<\/p>\n\nBuilding from source requires Node.js (>=22.12.0) and npm:<\/p>\n\n
\n- Clone repository: git clone https:\/\/github.com\/Veridis-Dev\/veridis-news-desk.git<\/li>\n
- Install dependencies: npm ci<\/li>\n
- Generate production bundles: npm run build<\/li>\n<\/ol>\n\n\n
\n- Upload the
veridis-news-desk<\/code> folder to the \/wp-content\/plugins\/<\/code> directory, or install the ZIP file via WordPress Admin Plugins -> Add New -> Upload Plugin.<\/li>\n- Activate the plugin through the 'Plugins' menu in WordPress.<\/li>\n
- Access the newsroom interface via the 'Veridis News' menu item in the WordPress admin sidebar.<\/li>\n<\/ol>\n\n\n
\nDoes Veridis News Desk replace the WordPress editor?<\/h3><\/dt>\nNo. It integrates alongside standard WordPress editing workflows, providing a dedicated Newsroom dashboard and an optional Editor Mode sidebar within the Block Editor.<\/p><\/dd>\n
Does it modify existing posts?<\/h3><\/dt>\nNo. Veridis News Desk does not replace or rewrite your article title or body content. It stores editorial workflow metadata alongside WordPress posts, while features such as Follow-ups and settings use their own plugin-managed storage.<\/p><\/dd>\n
What happens to data when the plugin is removed?<\/h3><\/dt>\nBy default, Veridis News Desk preserves all editorial metadata, custom database tables, and settings upon plugin deletion. If you prefer a complete cleanup, you can disable the \"Preserve data on uninstall\" option in Settings prior to deleting the plugin.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.0<\/h4>\n\n\n- Added a newsroom Dashboard with publication totals, urgent work, deadline watch, Article Health, and Follow-ups at a glance.<\/li>\n
- Added Newsroom List and Board views with search, filters, sorting, pagination, and compact story metadata.<\/li>\n
- Added editorial statuses, assignees, priorities, deadlines, and clear overdue and due-today views.<\/li>\n
- Added an explicit assignment workflow: ideas may remain unassigned, while active editorial work requires a responsible user.<\/li>\n
- Separated the public WordPress author from the current workflow assignee; the first assignee establishes the byline and later reassignment preserves it.<\/li>\n
- Added a Story Drawer for reviewing and editing editorial details, sources, Follow-ups, and Article Health actions.<\/li>\n
- Added Article Health checks for featured images, excerpts, sources, and photo credits, with workflow-aware fixes.<\/li>\n
- Added Follow-ups for tracking callbacks, updates, deadlines, status, and responsibility for each story.<\/li>\n
- Added a focused Editor Mode with editorial controls, save protection, and a reliable return to the previous Newsroom context.<\/li>\n
- Improved first-run and filtered empty states with clear paths to create the first story.<\/li>\n
- Added English and Romanian interface localization through the WordPress user locale.<\/li>\n
- Integrated access and assignee eligibility with standard WordPress roles and capabilities.<\/li>\n
- Improved narrower-width Board navigation, metadata labels, validation timing, subdirectory URL handling, and other release-candidate interface details.<\/li>\n<\/ul>\n\n
0.9.0<\/h4>\n\n\n- Canonical article model foundation.<\/li>\n
- Settings and data-retention controls.<\/li>\n
- Newsroom, editorial workflow, board, Follow-ups, Article Health, and Editor Mode foundations.<\/li>\n<\/ul>","raw_excerpt":"A newsroom and editorial workflow for managing stories, assignments, deadlines, sources, follow-ups, and publishing readiness in WordPress.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/376106","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=376106"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/veridisdev"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=376106"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=376106"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=376106"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=376106"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=376106"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=376106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}