You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main goal for using docusaurus was to be able to keep the site ampersandtarski.github.io in sync with the features that are in production. For this reason, we planned to generate the one-pager site each time something is pulled into the main of each repo.
That sulution has a drawback: It doesn't allow for easy fixing of current documentation. The strict rules we have in place to ship to main are hindering.
For this reason I see an even better solution. Let's creat a specific branch in each repo that contains documentation that should be incorporated in the one-pager site. I propose a uniform name of such branch, documentation. The purpose of that branch will be that it contains the 'current' documentation. Fixes of documentation can be done in that branch. Whenever that branch is updated, that will trigger the build of docusaurus.
Whenever main is updated, we should (automatically?) merge to documentation, so the build of docusaurus is triggered.
This way of working will ensure that the documentation on the site is always up-to-date with the features in main. It also enables us to work on technical debt of documentation itself.
No description provided.
The text was updated successfully, but these errors were encountered: