7. OS X
Lightweight CMS written in PHP and reminiscent of Blosxom #
"Stacey is a lightweight content management system.
No database setup or installation files, simply drop the application on a server and it runs. Your content is managed by creating folders and editing text files. No login screens, no admin interface." RSS/Atom support; requires PHP 5+.
/blosxom | Sep 04, 201142-line blog engine in Bash #
___.sh is a "recursive, multimarkdown, sed & bash static HTML blog 'engine'" by Nicolas Hoibian. See it in action.
/blosxom | Jul 25, 2011A simple weblog generator written in Python #
Pelican, by Alexis Métaireau, calls to mind similar engines like Blosxom and Ode; blog entries can be created in any text editor and a simple CLI tool (re)generates the static pages. Support for Disqus comments, themes, and PDF output. (Via Brian Lane's post on HackerNews. See also the creator's original announcement.)
UPDATE: Bert JW Regeer points to an even simpler Python script by Oben Sonne called Poole. Example site
/blosxom | May 29, 2011Getting Google to index your Blosxom blog correctly #
I originally asked (and answered) this question on Doctype, and reproduce it here (with slight modifications) for other Blosxom users:
Blosxom creates multiple copies of the same entry in different directories. For example, a given entry would have:
I wanted Google to prefer the first entry, since it makes finding content easier. I tried using robots.txt to exclude indexing of the topic and date indexes, but then Google ignores or cannot find the unique URLs either.
- its own unique URL
- a place in the topic index
- a place in the month index
- a place in the year index
I ended up adding
<meta name="robots" content="noindex, follow">
to the blog index pages via this this one-liner
find -name index.html -print0 | xargs -0 perl -pi -e 's/<head>/<head>\n<meta name="robots" content="noindex, follow">/g'
at the end of my static publishing routine.
That way, search engines can find the canonical URLs, but will ignore all of the topic and date index pages.
UPDATE 1: Just found someone with the same issue who also solved it with "noindex, follow".
UPDATE 2: After a few weeks Google was properly indexing my site, and continues to do so after more than a month.
UPDATE 3: Another report of using robots meta tag to fix search engine indexing.
/blosxom | Aug 13, 2010Blosxom.com and Blosxom plugin registry listing mirror #
After reading this, I decided to post an archive of Blosxom.com and the Version 2 Plugin Registry Listing, including the code for all 465 plugins (602 counting the various versions):
Those desiring to dig deeper into Blosxom may enjoy Frank Hecker's annotated blosxom.cgi and Rob Reed's annotated Blosxom bundle.
/blosxom | May 14, 2010Rob Reed builds a better Blosxom with Ode #
I first contacted Rob Reed last year while looking for a copy of his annotated Blosxom bundle (not to be confused with Frank Hecker's version). Rob quickly and kindly obliged, and also informed me of a new publishing platform he was working on called Ode,
Release 1.0 has just become available for download today.
- a single Perl script
- with content generated from plain text files
- and look/layout determined by standard (X)HTML and CSS.
I asked Rob for permission (which was graciously granted) to post some of the thoughts he has shared over the last few months via email (emphasis mine):
- On Blosxom: I'm a big believer in (the vision of) blosxom. In fact, as crazy as it may sound, blosxom played a part in my decision to go back to school to get a masters in computer science. Of course there was more to it than just blosxom, and it's certainly not necessary to get a degree in CS to understand blosxom, but I think blosxom is an important project, and I wanted to explore that idea. So, long story short, it's fair to say that Ode owes a lot to blosxom. Anyone who understands the why of blosxom will almost certainly get what Ode is all about.
- On Ode: The project's motto is "Ode is simple" with the qualification that "Simple means you know how it works". I wanted to do something that blurred the line between end user and developer by making Ode accessible to anyone who was interested. To that end in addition to the normal sort of documentation there's a narrative walk-through of the source code similar to what I did with blosxom but with more discussion about not just what the code is doing, but why. I put together a lot of other resources as well, including diagrams related to the flow of execution, and a bunch of other stuff.
- On Twitter: ... like inventing the telegraph after the telephone and insisting that its limitations somehow represent unique value.
- On Facebook: Ask yourself if you're comfortable handing over all of your content to a service that you have no control over for the luxury of wading through ads, and then hoping that they don't change the terms of service at a moment's notice in such a way that you're no longer comfortable with their policies ... Perhaps more important is the fact that we already have a web. If you're like me, you don't see the need to build a web on top of the web and put it in the hands of a single commercial entity. Something about that just doesn't feel like a step in the right direction.
- On hiring developers: I don't agree with most of what [name removed] has to say about what it takes to be a successful software developer (and what to look for when hiring developers). In fact, if I could invent a machine into which I could feed everything he's written about hiring developers and have it spit out the exact opposite, that advice is probably closer to how I'd do it. I'm a believer in loyalty, potential, personal responsibility, and shared ownership of projects, even in a professional setting. I also don't believe in tricking people into revealing to you whether they'll be good at the job you're interviewing them for; or testing as a substitute for getting to know people. I'm surprised at how invested companies are in hiring people who are good at getting hired, not people who will be good at the job they're being hired to do (and also who will be pleasant to be around for the next 1-10 years).
- On "social networking": The web has been social from the very beginning :) ... that gets to the heart of what ode is about. I wanted to put together a simple platform that would allow a user to experience the web as it was intended to be - a distributed, collaborative space where everyone is able to contribute (as well as consume). A "more than the sum of it's parts" platform that plays well out on the open web. A tool for anyone who believes that permanence and substance are of primary importance.
/blosxom | Mar 25, 2010Blosxom alternatives, microblogs, etc. #
This blog post is updated sporadically. Last update: 2012.09.10
- BashBlog is a simple blog system in 500 lines of bash with support for RSS, automatic validation, and more.
- Chisel is "a simple Python static blog generation utility".
- Chyrp "is a blogging engine designed to be very lightweight while retaining functionality. It is powered by PHP and has very powerful theme and extension engines, so you can personalize it however you want."
- FlatPress "is an open-source standard-compliant multi-lingual extensible blogging engine which does not require a DataBase Management System to work."
- GugoDoc is "a little [Python] script that generates a static html website from a collection of markdown files."
- Jekyll "is a blog-aware, static site generator in Ruby." (via Jalada)
- NanoBlogger (first covered over 5 years ago; still under active development) "is a small weblog engine written in Bash for the command line. It uses common UNIX tools such as cat, grep, and sed to create static HTML content."
- Ode is "a single Perl script, with content generated from plain text files, and look/layout determined by standard (X)HTML and CSS".
- plain-blog is a self-modifying Perl script which generates a static blog. The author, Spencer Tipping (formerly at Google), runs a fascinating consultancy.
- Pelican is a simple, static weblog generator written in Python with support for themes, Atom/RSS feeds, importing from WordPress, Dotclear, or RSS feeds, and more.
- PluXml "is a script to create a site or a blog, no need for knowledge in programming nor d' need; a database on its lodging, a traditional environment php is enough for him. PluXml wants to be light and easy d' use thanks to an interface d' simple administration and the storage of your writings in easily transportable XML files." (translation via Babelfish)
- Poole is a Markdown-driven static website generator written in Python.
- PyBlosxom "is a lightweight file-based weblog system. The project started as a Python clone of Blosxom but has since evolved into a beast of its own. PyBlosxom focuses on three things: simplicity, extensibility, and community."
- reprise - "Minimal static blog with atom and tag support." Available as a single Ruby or Python file.
- simpleblog is "a simple Python blogging system" that uses static rendering.
/blosxom | Dec 03, 2009Migrating from WordPress to Blosxom #
Yes, you read that correctly. In this degenerate age, when even Rael Dornfest powers his blog with WordPress, there are still those who appreciate Blosxom's simplicity and security. For those who were lost but now have been found, Antonio Zamora explains how to migrate from WordPress to Blosxom.
/blosxom | Aug 31, 2009Blosxom explained line by line #
Frank Hecker has generously provided an annotated version of Rael Dornfest's blosxom.cgi. A must-read for Blosxom users who want to understand what's going on under the hood.
/blosxom | Oct 22, 2005Ping-O-Matic #
Ping-O-Matic allows you to ping the following services quickly and easily: Weblogs.com, Blo.gs, Technorati, Feed Burner, Syndic8, NewsGator, Feedster, My Yahoo!, PubSub.com, Blogdigger, BlogRolling, BlogStreet, Moreover, Weblogalot, Icerocket, News Is Free, Topic Exchange, Audio.Weblogs, RubHub, GeoURL, A2B GeoLocation, BlogShares.
/blosxom | Oct 20, 2005