

Looks like markdown is converted to html syntax. In-text:
<sup class="footnote-ref"><a href="#fn1" id="fnref1">[1]</a></sup>
And footer section:
<hr class="footnotes-sep">
<section class="footnotes">
<ol class="footnotes-list">
<li id="fn1" class="footnote-item"><p dir="auto">Don’t want to give them the traffic. <a href="#fnref1" class="footnote-backref">↩︎</a></p>
</li>
</ol>
</section>
From there they can be stylized. Pretty neat. More info




For the music, jellyfin can do this and it uses subsonic api which means you can connect to the music server with some mobile and desktop apps. Alternatively i like navidrome for more specialized music service that still uses subsonic api. Some people prefer not having a second service if jellyfin is good enough for their needs.
For backups look into borg if your NAS doesn’t have anything native.
Look into doing let’s encrypt DNS-01challenges via something like acme.sh if your domain registrar has an api. this will let you get your own certs for local use without exposing the subdomains on the domains dns. If you’re going to make them public then that is less important but it’s still a good way to automate renewals and deploying regardless.
Pihole unbound can offer a recursive dns server. Very easy set up.
Outside of the obvious segmenting public zones and firewall, you could self host an SSO service. This would allow you to easily put forward auth on a dev build if you were needing to keep it selectively private until/if you made it public.
In general though, i just wait until i come across a problem or need and then i see if a service exists to solve that. Occasionally looking through the awesome selfhosted list or similar helps find blind spots i didn’t know i had.