Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
I would recommend learning basic HTML CSS and making a website without external tools. This way the maintenance cost is 0 as your website will likely work forever.
Write all your HTML first then your CSS, it will be easier this way. Use vanilla JS if you need to but avoid external libraries , same for php.
This, and don't forget to use W3's HTML and CSS validators.
To add to this a bit, if the site is just a single page that will be fine. If your site has a bunch of pages that all need to share the same theme and headers and footers and such it may be worth learning a simple templating system that runs before the site is sent for hosting.
That way if you need to update something in the design or theme you can do it once, rather than on dozens of pages.
Personally I use eleventy for my little site.
https://www.11ty.dev/