this post was submitted on 25 May 2024
19 points (95.2% liked)

Selfhosted

39856 readers
440 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Looking through the writefreely.org instances on their website, a lot of the links are dead or closed for registration. The one that is open and working is promoting a paid version. Is hosting a writefreely instance heavy on resources, attracting the wrong people or just not "cool" enough?

you are viewing a single comment's thread
view the rest of the comments
[–] theshatterstone54@feddit.uk 1 points 5 months ago (1 children)

Is Hugo good for, say, a portfolio website? I know its good for blogging, but I've been thinking about a simple portfolio website hosted on Gitlab pages (I wish I could selfhost, but I can't due to a lack of hardware and restrictions from my student accommodation and their network policy), and was wondering if Hugo would be a good choice for a portfolio website, maybe just having one page per project or something like that?

[–] sxan@midwest.social 4 points 5 months ago

Hugo isn't a server, per se. It's basically just a template engine. It was originally focused on turning markdown into web pages, with some extra functionality around generating indexes and cross-references that are really what set it apart from just a simple rendering engine. And by now, much of its value is in the huge number of site templates built for Hugo. But what Hugo does is takes some metadata, whatever markdown content you have, and it generates a static web site. You still need a web server pointed at the generated content. You run Hugo on demand to regenerate the site whenever there's new content (although, there is a "watch" mode, where it'll watch for changes and regenerate the site in response). It's a little fancier than that; it doesn't regenerate content that hasn't changed. You can have it create whatever output format you want - mine generates both HTML and gmi (Gemini) sites from the same markdown. But that's it: at its core, it's a static site template rendering engine.

It is absolutely suitable for creating a portfolio site. Many of the templates are indeed such. And it's not hard to make your own templates, if you know the front-end technologies.