Open SamVanhoutte opened 2 years ago
We can maybe include this when we generate a new version of the docs, bc that's usually the moment that we determine that we mark the current available features. Besides the Docusaurus generation, we can include in the package.json
a script command that does both (Docusuarus versioning and lazy docs generation).
Just an idea.
Option 1 : generate md files in CI-build and commit to branch
This was tested and tried, but resulted in endless loops of CI-build. Snippets for ci-build.yaml:
Option 2 : Generate the documentation in the Netlify action
Option 3 : find a way to automatically force the generation of the docs at client side / build side
This is the current implementation, but requires the dev to consider rebuilding the documentation, before committing. As this is performed by a test, this hopefully means, the test will be executed locally, before pushing to the repo.