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
Currently, the documentation is more spontaneously structured construct. With some additions to our ecosystem in the near future, that will also get more attention, we should structure our documentation holistically, so that it also accounts for the synergy between them.
Projects that have synergies, from the user POV:
rustic
rustic-server
rustic-scheduler
app documentation
Projects that have synergies, from the developers POV:
libraries of the various apps
the apps themselves
the documentation of the libraries
The text was updated successfully, but these errors were encountered:
Accounted for the informational split between users and devs with creating https://github.com/rustic-rs/dev-docs which is hosting the developer documentation.
Next, I would like to brainstorm topics that we didn't account for in both and open corresponding issues for that.
Currently, the documentation is more spontaneously structured construct. With some additions to our ecosystem in the near future, that will also get more attention, we should structure our documentation holistically, so that it also accounts for the synergy between them.
Projects that have synergies, from the user POV:
Projects that have synergies, from the developers POV:
The text was updated successfully, but these errors were encountered: