I exported a Wordpress site as a static site and have been hosting that on Gitlab. I’d like to start updating the blog again and I’m wondering how to go about it.
For the blog, I’ve been adding/coding the entries manually, which I still prefer to using Wordpress. Now I have someone who needs to take over the blog and I need something more simple for them.
I’ve looked into DropInBlog ( https://dropinblog.com ) but it’s way beyond our budget, so I’ve been thinking to either:
-
Give them git access and let them add a text file and image to a special directory when they want to post. Then I can have a script run a few times per hour which converts that into a blog post. I’d also need to update the blog index with my own code.
-
Let them use something RSS based with a nice interface and scrape that to generate the blog. Mastodon is one option, as is Wordpress. Ideally the blog they maintain would not be accessible to others on the web though. I don’t want to split our SEO presence.
Does anyone have a better suggestion? The website doesn’t use a framework like Jekyll or any of those. It’s just HTML, CSS and JS.
Maybe look at Astro and develop a lightweight blog post admin panel to create, edit, and delete posts. Should be relatively easy and you should be able to render out a static site from it each time you need to update it.
I thought Jekyll just compiled the input files to html/css/js and created a static site?
Hugo, too? I hear Hugo is easier.
I haven’t used either of them.
They do. The issue is that I already have a static site. I don’t want Jekyll or Hugo to overwrite those. I suppose I can choose which sections I push to Gitlab Pages. Maybe one of those would work in that case.
If Markdown formatting is enough for you, I would look into using a static site generator, like Hugo or Jekyll.
If you want to keep your existing content as static files but same website skeleton and layout instead of copying and editing files you’ll copy one and create the layout template. Then content and new posts and pages can be generated from Markdown files. If you set up CI they won’t need to run Hugo or what you’re using, only push the Markdown files to your Git repository.
Whatever you want to do primarily depends on: Your formatting, styling, functionality, and interfacing needs for the editor, and what you’re willing to use or invest for setup.
Hugo runs from a single binary. The source layout is reasonable. With a single layout the folder structure doesn’t have to be complex.
I’m not very familiar with alternative [Markdown] static site generators.
