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.
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
If it's really just three pages I would just build them with static HTML and CSS. Maybe use PHP to have common elements in a separate file, but that's about it.
CSS can become tedious, especially if you are targeting mobile device and tablets and building this in plain HTML CSS and PHP is way too much work and the end result will probably still not be very responsive and won't look so great.
This approach is definitely an overkill and if the OP doesn't want to use this as an educational project I will strongly suggest not to go this route. Just use some of the tools the other has suggested here, like Grav, Hugo, etc.
Another neat trick is to generate your website on your own PC and only publish the static version.
You can publish static files to a CDN service, which costs very little compared to traditional hosting that includes a dynamic language and database.
A CDN is also usually distributed across the world and has cool features like built-in scalability and redundancy which means very little chance of outages, can deal with traffic spikes, and fast response no matter where the visitors are from.
I have done this, but instead of PHP, I have used Server Includes, which is a performant and simple way to add repeating headers and footers etc without extra dependecies. Nginx, Apache and Caddy all supports Server Includes, but with different syntax. I have used Caddys templating language, which I am most comfortable with.
Oh man this brings back memories! It is indeed a simple way to get some basic "site template" without needing a lot of infrastructure.
It actually works great for slightly more complex stuff to, like converting markdown to HTML etc. Caddys documentation is made using Server Includes for example.
This is also what I suggest. I moved from WordPress to Grav. It’s good, but a lot of work to customize.
Here’s a very useful resource of code snippets to make your website attractive and functional, without aCMS. https://www.w3schools.com/howto/default.asp
I love grav. Yes its a chore intially but ive move 30+ site from wp to it and all my clients love it