[Deliverable] Review Documentation and Define Guidelines

[fryorcraken]

Owner: core research

(No FURPS)

• Audit the current developer and contributor documentation
  • Inventory existing documentation
  • Remove outdated or duplicate content.
• Define and implement basic new documentation structure
  • Define content boundaries for docs site, Github, forum, videos, etc.
  • Reorganise existing content for clarity
  • Improve landing page + persona-based Get Started
• Define document management process for Waku teams to
  • Make docs part of dev lifecycle process
  • Assign doc owners for different parts of the docs repo
  • Onboard existing and new contributors on contributing to documentation: location, format, providing feedback

[fryorcraken]

@jm-clius I am happy with stage 0 and 1 of https://forum.vac.dev/t/virtual-offsite-recommendations-waku-documentaiton/519/3

Shall we just iterate on the DoD (aka the checkbox in the description of the issue) to match stage 0 and 1?

[jm-clius]

@fryorcraken updated the issue description to match the forum stages 0 and 1. @s-tikhomirov can you do a sanity check? The only change I've made is to move "define content boundaries" under the "new doc structure" task (IMO it exceeds the scope of an audit).

[s-tikhomirov]

Looks good to me! Happy to see this moving forward.

[fryorcraken]

Some community feedback:

• Add AI Integration Tools for Documentation to improve developer experience docs.waku.org#247
• Proposal: New Starter Template Strategy for Waku Ecosystem docs.waku.org#246

[fryorcraken]

Ownership moved to EcoDev-Docs team