> I propose the following > - /doc -> for .md files except README.md > - /doc/assets -> for anything and everything attached to the .md files > (images, document specific example files, etc.).
OK, could we "take a break" after having merged all open documentation-related PRs to then prepare a PR that just moves everything (with or better still without our reference doc) into the new folder structure? I would like to prepare a PR then for the Synology FAQ changes where I need to add screen shots and don't want to merge this structure change into one PR: https://github.com/bit-team/backintime/issues/1674 On Mon, 2024-05-13 at 13:18 +0000, [email protected] wrote: > Hello > > Am 13.05.2024 15:03 schrieb Hakan Bayındır: > > I don't think having more repositories will make things simpler. > > I do think the same. > > Am 13.05.2024 15:03 schrieb Hakan Bayındır: > > I propose the following > > - /doc -> for .md files except README.md > > - /doc/assets -> for anything and everything attached to the .md files > > (images, document specific example files, etc.). > > Sounds perfect to me. > > I also do have in mind to migrate our reference documentation (currently > in "common/doc-dev"), the user manual (in a separate repo > "bit-team/doc") and our "developers documentation " (also in > "common/doc-dev") into our primary repository. In this case a root > folder "doc" or "docs" would be perfect. Because of that now creating a > "doc" folder is a good step into the future. ;) > > Best > Christian > _______________________________________________ > Bit-dev mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mailman3/lists/bit-dev.python.org/ > Member address: [email protected] _______________________________________________ Bit-dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: [email protected]
