Replies: 3 comments
-
|
I see your point and you rub salt in my wound. Please keep in mind raspiBackup evolved over the last 12 years and step by step new features suggested by the community were added by me. Then I documented the new feature ... another one ... and so one. I agree with you in the meantime raspiBackup has so many features which should be documented and consolidated from scratch. A good documentation is not created by the creator of a tool who has development insights and doesn't know about the questions of users. Said that a new doc for raspiBackup has to have to be created by somebody - or even a team - and not by me. If you are willing to lead and recrute the team or create a doc I'm fine. We can discuss the details. I'll answer any questions you have and will help to make the doc complete and organized but I will not write any text in the doc. Please note I document bilingual - in English and German - and I still want to have raspiBackup documented also in German. |
Beta Was this translation helpful? Give feedback.
-
|
There's going to be a raspiBackup V2 documentation available. It will take time got get all the doc from the website copied and updated to github pages so be patient. @daquino94 Feel free to contribute 😉 |
Beta Was this translation helpful? Give feedback.
-
|
The new raspiBackup documentation is available now 😉 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I love this repository and the project in general but I think that the documentation would need to be reviewed as it is very scattered and on sites that are now graphically dated and also very disorganized. would it be possible to create a parallel repository where you could recreate the documentation? you could use MkDocs which is based on md
Beta Was this translation helpful? Give feedback.
All reactions