Content People - Obsidian Hub

# Content: People ## Ideas to reduce the overhead of these pages *There is some overlap between these ideas...* ### Change author template to simplify manual intervention, when running `update-releases.py` **Status: DONE** **Note:** *This is being tracked in [Make automated edits of Author/People pages less error-prone · Issue #348](https://github.com/obsidian-community/obsidian-hub/issues/348)* The reasoning behind [[Content Comments]] is to greatly reduce the number of lines that need to be reverted when the author pages are updated, from minimal edits to to the authors template(s). It will help contributors see the intention for links and `^` too... **Change this: DONE** ```markdown   ``` To this: ```markdown   ``` **Change this: DONE** ```markdown  ``` To this: ```markdown  ``` **Change this: DONE** ```markdown  ``` To this: ```markdown  ``` **Change this: DONE** ```markdown  ``` To this: ```markdown      ``` **Change this: DONE** ```markdown  ``` To this: ```markdown     ``` ### Create-and-include separate files for machine-generated content **Decision**: **Rejected** Get the same benefit by replacing chunks of code inside the single files, such as is done for MOCs and Uncategorized Plugins. Make the Python script that creates Author pages put the generated text in to little files for inclusion in the main file. See [[#Divide up the jinja templates in to component parts]] below. For example, we would end up with something like this: Part of `chrisgrieser.md`: ```markdown ## Author of %% Hub Content: Don’t edit below %% ![[chrisgrieser.plugins]] ![[chrisgrieser.themes]] %% Hub Content: Don’t edit above %% ``` In `chrisgrieser.plugins`: ```markdown ### Plugins - [[obsidian-extra-md-commands|Extra Markdown Commands]] ``` In `chrisgrieser.themes`: ```markdown ### Themes - [[Shimmering Focus]] ``` The big advantage of this is that the rest of the author file, with manual edits, will not get over-written. For discussion: - Would need to identify a sub-dir to put the files in - If manually creating new author pages, would need to create the 2 extra files and put them in the right location ### Divide up the author jinja template in to component parts. **Status: DONE** **Note:** *This is being tracked in [Make automated edits of Author/People pages less error-prone · Issue #348](https://github.com/obsidian-community/obsidian-hub/issues/348)* This follows on from the rejected [[#Create-and-include separate files for machine-generated content]] above. The idea is to break up the long Jinja template files in [.github/scripts/templates](https://github.com/obsidian-community/obsidian-hub/tree/main/.github/scripts/templates) in to separate files. This would allow us to use the individual templates to selectively update parts of individual notes. ## Odds and Ends - [ ] Rename [Author template](https://github.com/obsidian-community/obsidian-hub/blob/main/00%20-%20Contribute%20to%20the%20Obsidian%20Hub/01%20Templates/T%20-%20Author.md) to `T - Person.md` - and link to it... %% Hub footer: Please don't edit anything below this line %% # This note in GitHub <span class="git-footer">[Edit In GitHub](https://github.dev/obsidian-community/obsidian-hub/blob/main/00%20-%20Contribute%20to%20the%20Obsidian%20Hub/03%20Contributor%20Notes/03.02%20Design%20Decisions/Content%20People.md "git-hub-edit-note") | [Copy this note](https://raw.githubusercontent.com/obsidian-community/obsidian-hub/main/00%20-%20Contribute%20to%20the%20Obsidian%20Hub/03%20Contributor%20Notes/03.02%20Design%20Decisions/Content%20People.md "git-hub-copy-note") | [Download this vault](https://github.com/obsidian-community/obsidian-hub/archive/refs/heads/main.zip "git-hub-download-vault") </span>