TOC and file renaming #88
Conversation
root-hal9000
commented
Jul 6, 2024
root-hal9000
commented
- renamed all files to be lowercase and have no spaces
- Updated all references to those names in file content
- Recreated table of contents into readme.MD Issue Add readme / TOC #2
- Separated "importing docs" text into a separate file
- Added a few %%{WARNING}%% tags to links that go to zadams repos. Issue Doc Review: ALL - Replace '%%{WARNING}%%' Token #87
- renamed all files to be lowercase and have no spaces - Updated all references to those names in file content - Recreated table of contents into readme.MD Issue TriliumNext#2 - Separated "importing docs" text into a separate file - Added a few %%{WARNING}%% tags to links that go to zadams repos. Issue TriliumNext#87
Alumniminium
added
documentation
Oops, sorry about that, they had been deleted (I originally renamed them with a bash script) but I had issues commiting and re-cloned to copy my changes over and didn't notice that. Will do |
|
OK, deleted the old files - anything else here or should I merge. If someone merges, create a new initial-review branch from main after merging this. Also, I forgot to note that I did make some slight changes to the order of the TOC as suggested in issue #2 - mostly just moving things for newer users up the TOC in places where order didn't necessarily matter (e.g.: desktop installation before all the different server installation instructions) |
|
was all of this work scripted? I presume yes or mostly. Perhaps put them in |
Only the renaming of the files to lowercase/no space (and replacing of the links referring to them). The TOC was manual as there's no inherent structure in the files for that and I made some slight changes to the order. Sorry, it was more clear with separate commits but I wound up having to squash it all It was a quick and dirty thing, but I can add it |
|
oh god i should have merged that from the terminal and not from the web... what just happened |
Just got out of the meeting, not sure what you're referring to, although I see a couple of new branches? Also, I should have made the PR to the main branch, no? We should merge this into main, and then pull the initial-review branch from there |
|
Done. I've merged that branch into main and created an 'initial-review' branch from the new main. @root-hal9000 |
