NanoBlogger

Official Announcement: Development is suspended indefinitely until further notice. Life goes on and my interests lie elsewhere these days. What started off as a project to learn shell scripting has enjoyed years of niched interest from around the world and for that I thank you! It's been a lot of fun!

Official Announcement: Development is suspended indefinitely until further notice. Life goes on and my interests lie elsewhere these days. What started off as a project to learn shell scripting has enjoyed years of niched interest from around the world and for that I thank you! It's been a lot of fun!

Here's the road map for future development of NanoBlogger. Branch 3.5 This branch will focus only on merging NB-extra into NB. No addition will be brought, excepted translations; Nothing will be deleted (excepted for bug fix); Bugs are to be ... [More] fixed. So, we keep the former numbering convention (3.5.RC1, 3.5.RCn,3.5.0, 3.5.n, ...). Branch 4.* This branch will start after the first release of NB-3.5.RC1 . The development will be kept separated from the trunk until the ultimate release of branch 3.* . The goal is to prepare the next HTML version and to provide a good HTML code that makes it easy to write CSS. Branch 3.6 This branch will focus on adding a menu bar. No addition will be brought, excepted for the templates (and style sheets involved by menu bar) and translations; No deletion, excepted for bug fix. Branch 3.7 This branch will focus over reducing the amount of features (like TIDY or feed links) No addition, excepted translations; Deletion of some features. Branch 3.8 This branch will focus over the blog.conf file. This branch could be the ultimate one. Provide an easy way of options for unique/multiple main pages; Provide an easy way of options for archives pages, etc.; No addition, excepted for translations; No deletion, excepted for simplification of management of archive pages and bug fix. [Less]

Here's the road map for future development of NanoBlogger. Branch 3.5 This branch will focus only on merging NB-extra into NB. No addition will be brought, excepted translations; Nothing will be deleted (excepted for bug fix); Bugs are to be ... [More] fixed. So, we keep the former numbering convention (3.5.RC1, 3.5.RCn,3.5.0, 3.5.n, ...). Branch 4.* This branch will start after the first release of NB-3.5.RC1 . The development will be kept separated from the trunk until the ultimate release of branch 3.* . The goal is to prepare the next HTML version and to provide a good HTML code that makes it easy to write CSS. Branch 3.6 This branch will focus on adding a menu bar. No addition will be brought, excepted for the templates (and style sheets involved by menu bar) and translations; No deletion, excepted for bug fix. Branch 3.7 This branch will focus over reducing the amount of features (like TIDY or feed links) No addition, excepted translations; Deletion of some features. Branch 3.8 This branch will focus over the blog.conf file. This branch could be the ultimate one. Provide an easy way of options for unique/multiple main pages; Provide an easy way of options for archives pages, etc.; No addition, excepted for translations; No deletion, excepted for simplification of management of archive pages and bug fix. [Less]

NanoBlogger 3.5 RC1 released! Download the tarball here. This release focuses on bug fixes and consolidating files into a single package. Summary of changes: Merges language files to base and does away with nanoblogger-extra package. Bug Fix: ... [More] Description was not being loaded from entry's metadata. Bug Fix: Archive template was subsequently being overwritten due to invalid file reference. Bug Fix: Title for year archives was not set. Bug Fix: Failed to update category database upon entry timestamp modification. Bug Fix: Attempts to fix Markdown freeze bug (possibly due to inconsistent behavior found in various implemenations). [Less]

NanoBlogger 3.5 RC1 released! Download the tarball here. This release focuses on bug fixes and consolidating files into a single package. Summary of changes: Merges language files to base and does away with nanoblogger-extra package. Bug Fix: ... [More] Description was not being loaded from entry's metadata. Bug Fix: Archive template was subsequently being overwritten due to invalid file reference. Bug Fix: Title for year archives was not set. Bug Fix: Failed to update category database upon entry timestamp modification. Bug Fix: Attempts to fix Markdown freeze bug (possibly due to inconsistent behavior found in various implemenations). [Less]

There is an exciting future for NanoBlogger. Denis Benard of NanoBlogger francophone, has proposed an excellent and very pragmatic roadmap. I'm looking forward to revisiting the project and picking things up where I left off.

There is an exciting future for NanoBlogger. Denis Benard of NanoBlogger francophone, has proposed an excellent and very pragmatic roadmap. I'm looking forward to revisiting the project and picking things up where I left off.

There is an exciting future for NanoBlogger. Denis Benard of NanoBlogger francophone, has proposed an excellent and very pragmatic roadmap. I'm looking forward to revisiting the project and picking things up where I left off.

I've had a lot of responses since I last posted here expressing interest in joining the project. Thanks for all your responses, If you haven't made it on the team and feel that you should be on it, then please email me and let me know. I tried my ... [More] best to save and review each email sent to me, but that doesn't mean that yours did not get lost or overlooked. Here's looking to the future of NanoBlogger! [Less]