It's flu season, and a bad case of NIH is going around.

In this post, I am specifically addressing what I'm doing to avoid introducing NIH in Firmant. More importantly I am addressing how I wish to remove NIH from the existing codebase.

This post provides a little insight into Firmant's testing strategy as well as provides guidelines on how to leverage unit tests to ensure the stability of Firmant on your platform.

Firmant's first third-party patch has been committed!

Just an update on the Firmant project. In the spring and summer I was funded to work on Firmant through RCOS. This semester I'm working on it independently, but still keeping the RCOS community informed.

....

I've been actively hacking on Firmant recently. Much effort has been put into eliminating needless code, primarily leftovers from older designs that have since been phased out.

...

Part of being a useful web platform is catering to a multitude of users and their individual languages. This is a test of unicode functionality in order to accomodate users who wish to use their native characters.

Thanks to Professor Moorthy at RPI for providing the following snippet to test unicode support: இது ஒரு பரிக்ஷை

This post is an introduction to Firmant. Firmant is a relatively young blogging framework useful for hosting your own weblog.

Firmant is written in Python with a minimal set of external dependencies. Dependencies include:

....