- Adding a to-do list at top of doc, to show what is planned and known to be missing before it can be released to the official Qubes doc PR.
- Splitting the tips section in tips related to Kickstart, and tips related to general boot issues.
- Adding new tips to both kickstart and boot issue tips.
- Removing text about Kickstart files in culture, this is outside the purpose and scope, and helps reducing the amount to read.
- Minor fixes such as typo's found 'here and there'.
Considerations, whether to construct a separate doc for the boot issue sections, since people needing the kickstart doc may not have these extra issues, and it isn't strictly speaking related to kickstart issues (although they do often come together). An idea being considered might be to make a separate doc for booting issues, and then link to it from here instead.
- Removing the backup script section from the script and any associated backup commands and warnings. This is done to streamline the simplicity and purpose of the script. Reminding users to take backups is outside the scope and purpose, and should be covered in separate scripts/docs. A backup reminder may be re-introduced if a proper GUI window can be made.
- Removing #-lock on script, so that it can run normal current updates out-of-the-box.
- Improved context and wording, as well as removing lingering redundancy and repeats.
- Overall intention in changes is also to make the script easier to read and getting started.
- Added a To-do table for planned improvements. Any help to reach these to-do goals sooner, are very welcome, and so are of course also other suggestions, feedback and improvements.
Various different improvements in the doc, however it'll need a few more updates before it's ready. I'll try squeeze in more before next summit if time allows it.
Suggestion for a folder, qubes-projects, which allows sub-folders with more individual freedom on content-structure, for as long it is kept inside this single sub-folder for every project. It also makes it easier to find all Qubes projects in a single location, whether briefly documented, or extensively documented, keeping them all together makes it easier to navigate. For example Qubes-TV may have a couple of different documents here, or Qubes-Binary-Router documentations. Projects like these and other projects that people may put up, or found elsewhere on the internet, could fit neatly in such a specialized folder. Thoughts on this?
Examples
- /contents/docs/qubes-projects/qubes-tv/broader-content-structure-freedom.
- /contents/docs/qubes-projects/qubes-binary-router/broader-content-structure-freedom.
- etc.
