Since we're planning to move our eslint-config to a separate repository this week. We now have full freedom to focus this repository on improving everything surrounding the documentation of our standards.
With this, we should also look into ways to make it easier to add and change this documentation. I think one of those ways would be start implementing a CI workflow using Actions.
As a kickoff we could add these actions:
an action that runs generate-table-of-contents, so contributors wouldn't have to do it themselves.
an action for alex.js, as the documentation will grow, we need to make sure that the language is considerate and inclusive.
Since we're planning to move our eslint-config to a separate repository this week. We now have full freedom to focus this repository on improving everything surrounding the documentation of our standards.
With this, we should also look into ways to make it easier to add and change this documentation. I think one of those ways would be start implementing a CI workflow using Actions.
As a kickoff we could add these actions:
generate-table-of-contents, so contributors wouldn't have to do it themselves.Thoughts?