Could you create a seat to update the documentation accordingly ?

[Nepiii]

Hello, i'm relaying heavily on the documentation (thanks for these pages all convertibles in .md, this is gold) but it doesn't follow well the updates since openrig is evolving quickly.
In example, i've a seat in one of my factory that pull the changelog from github to analyze if the update is worth and which system could be adapted natively (because sometimes I already have develop the feature that the new open rig release cover).

So my question is, would it be possible to also maintain the documentation online ? Because i'm mainly reading it for the "concepts" and philosophy of open rig.

[mvschwarz]

Thanks, @Nepiii, and glad the Markdown docs work for you. Yes: the upcoming release includes a full refresh of the developer docs, each page checked against the code: the reference pages, the as-built architecture docs, README, CONTRIBUTING and DESIGN. The site's reference and as-built pages render from the repo's docs/ at the latest release, so the refreshed versions appear online with it. After that, we're moving to refreshing the developer docs with each release, rather than page by page as changes land. Your changelog-reading seat is close to how that work is done here: agents on our team refresh the docs and check them against the code as part of a release. We'd welcome hearing how your seat decides whether a release is worth taking.

[Nepiii]

Thanks a lot ! :)

The seat decide by scanning the memories of each projets. He then ask a Jev agent to identify if it's worth taking the time to do the upgrade, upgrade in a closed environnement (generally with the upgrade of others tools in my stack), and then prepare the release and show it to me then I can leverage more and more features.

[mvschwarz]

Thanks for describing it, @Nepiii, and for the detail of trying each upgrade in a closed environment before it reaches your projects.