update-kb-article

Updating knowledge base articles across multiple files and languages requires a coordinated workflow that applies renames, content updates, and screenshot swaps across s/article/, s/topic/, portal/, and docs.json while enforcing explicit approval before modifying localized directories.

Planning KB article edits before execution involves surfacing impacts across related files and generating an actionable plan that complies with style guides like Domo-KB-Style-Guide.mdx, ensuring you review and explicitly approve the changes before any modifications are applied.

Yes, you can swap screenshots and update file paths in existing documentation by applying cross-file changes that maintain accuracy and consistency across the knowledge base, provided you confirm the execution plan before the updates are finalized.

Updating localized KB directories requires explicit user approval to enforce guardrails, ensuring that no localized content is modified automatically without your direct confirmation during the execution phase of the article update workflow.

To ensure knowledge base content follows your style guide during updates, the editing process enforces compliance with established content templates like New-Article-Template.mdx and Domo-KB-Style-Guide.mdx to preserve voice and structure across all modified articles.

You can coordinate renames, content updates, image swaps, and cross-file path changes across portal and docs.json files to maintain accuracy and consistency throughout the knowledge base, with a required planning phase before any execution begins.