The developer documentation of the RSD is a bit 'all over the place' at the moment. Some part are well documented, some part are outdated, others lack documentation completely.
We should think about a clear structure for developer documentation, where I see the split between:
- tech savvy users who add issues and discuss features (or want to know more about how the RSD is set up).
- developers who want to host an RSD and change the theming
- developers who want to work on the RSD itself
We should having a section in the README that points to the relevant developer docs. Currently, there is only a section pointing to the frontend development. The docs should also include info on code style for each part, testing requirements, etc.
The developer documentation of the RSD is a bit 'all over the place' at the moment. Some part are well documented, some part are outdated, others lack documentation completely.
We should think about a clear structure for developer documentation, where I see the split between:
We should having a section in the README that points to the relevant developer docs. Currently, there is only a section pointing to the frontend development. The docs should also include info on code style for each part, testing requirements, etc.