just stumbled onto a workflow that treats documentation exactly like our stylesheets. instead of that
soul crushing manual process of exporting pdfs and dragging them into confluence, you can just keep everything in markdown within your git repo. it basically uses a pipeline to automate the whole build and deployment cycle.
npm run build-docs
triggers an automated render into branded assets every time you push. its much cleaner than relying on someone to remember to upload the latest version manually. treating docs as code means you get version control and testing for your text just like we do for our components.
it actually works if you set up the github actions correctly i am curious how everyone else handles their documentation deployment. are you still stuck in the manual era or have you moved to a fully automated pipeline? no more broken links is the main goal here.
full read:
https://dev.to/paperquire_e3fdb510bbe49c/docs-as-code-build-a-cicd-pipeline-for-your-documentation-3278