add Obsidian Plugin Stats webapp

[ooker777]

Edited

Added

Checklist

• before creating a new note, I searched the vault
• new notes have the .md extension
• (if applicable) attached images have descriptive file names
• (if applicable) for new notes in the folder "04 - Guides, Workflows, & Courses", I added a link to them in one of the "for {group X}" overviews: https://publish.obsidian.md/hub/04+-+Guides%2C+Workflows%2C+%26+Courses/%F0%9F%97%82%EF%B8%8F+04+-+Guides%2C+Workflows%2C+%26+Courses

[claremacrae]

Many thanks for doing this!

[claremacrae]

This is fine, but I just wanted to record my thoughts on why...

Looking at the other categories in this folder, you will see they mostly don't contain explicit links.

They all work via backlinks - see this, for example:
https://publish.obsidian.md/hub/02+-+Community+Expansions/02.04+Auxiliary+Tools+by+Category/iPadOS+Apps

The advantage of this is that if an auxiliary tool changes what platforms it supports, only one file needs to change - the note for the tool - rather than having to keep 2 lots of data synchronised.

However, the template for this category does contain a "Tools in this Category" heading - and a few of the existing files do contain it too.

So I am happy for this link to remain.

[ooker777]

why isn't the template populated automatically? Because relying on backlink isn't reliable, as by default a new plugin will list all categories. For example, Docker isn't an iPadOS app, but it appears on the backlink of that category.

[claremacrae]

@ooker777 - I see you have created your PR from your main branch.

You should always create a branch on forked repos, before committing changes that are to go in to a pull request.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request

By not creating a branch and putting the PR in to the default branch (main, master or whatever), you run the risk that it will be very difficult to add later commits to your fork, or get new changes from the parent repo.

For example, these problems would happen if the PR was declined. It could also happen if the maintainer squashed the changes.

[ooker777]

Good tip. Thanks for letting me know.