ghostToHugo
mod_blog
ghostToHugo | mod_blog | |
---|---|---|
3 | 4 | |
132 | 108 | |
- | - | |
0.0 | 5.5 | |
over 1 year ago | 4 months ago | |
Go | C | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ghostToHugo
-
How to Start Your Blog in 2023
Couple that with the regular "your theme is no longer supported" messages, I got fed up of burning time to keep up with their updates, which offered no benefits to me. I quit and moved to Hugo (using a ghost-to-hugo migration tool [1]).
[0] https://ryansouthgate.com/goodbye-ghost-hello-hugo/#im-no-lo...
[1] https://github.com/jbarone/ghostToHugo
-
Looking for a quick replacement for Ghost (ghost.org)
For me I found a useful CLI tool to do the conversion for me. https://github.com/jbarone/ghostToHugo I made some tweaks to that above version https://github.com/robrotheram/ghostToHugo
-
Migrating from Ghost Pro to Hugo static on AWS for 24 cents
ghostToHugo is the converter, it didn't work for me, I found that if you had a bookmark with a nil description it would cause the tool to fail. I've fixed the bug and committed it back to the repo so it works if you have the same problem as I did. You can check out my commit here.
mod_blog
- Mod_blog: A Blogging Engine in C
- CGI programs have an attractive one step deployment model
-
How to Start Your Blog in 2023
I used to write raw HTML, but have since come up with my own markup system [1]. The posts themselves are still stored in HTML because I don't want to get stuck with a sub-optimal markup language. By storing the rendered HTML, I can change how the markup language works (and I have).
The blog engine itself [2] is one I wrote starting back in 1999, and still in use. It works, does exactly what I want, so there's no reason to change it. And to see it in action: <https://boston.conman.org/>.
[1] You can see an example here: <https://github.com/spc476/mod_blog/blob/master/NOTES/testmsg>. The markup engine is written in Lua: <https://github.com/spc476/mod_blog/blob/master/Lua/format.lu...>.
[2] <https://github.com/spc476/mod_blog/>
-
Websites Die
It comes down to the person running the website has to care. That's it. It doesn't matter how simple it is if the person doesn't care.
In my own case, I've been running my own website for 24 years now [1]. The URLs I started out with have remained the same (although some have gone, and yes, I return 410 for those) and the technology hasn't changed much either (it was Apache 24 years ago, it's still Apache today; my blog engine [2] was a C-based CGI program, and it's still a C-based CGI program. The rest of the site is static, and there's no Javascript (except for one page). I can see it lasting at least six more years, and probably more. But I care.
[1] Started out on a physical server (an AMD 586) and a few years later on a virtual server.
[2] https://github.com/spc476/mod_blog
What are some alternatives?
geeky-hugo - Geeky is a Personal Hugo blog theme focused on high speed. Geeky is fully responsive, Superfast, and powered by Bootstrap v5.
ghostToHugo - Convert Ghost blog export to Hugo posts
WriteFreely - A clean, Markdown-based publishing platform made for writers. Write together and build a community.
Hugo - The world’s fastest framework for building websites.
Isso - a Disqus alternative