Storm is the next iteration of this lingering idea to have a developer friendly blog engine with no database and only the needed and essential working parts. Last iteration was Rain.
The main reason Rain was developed is to create a blog engine that is really integrated to my current workflow in developing Web Application. Said workflow is:
Write in Text Editor -> Git Commit -> Git Push.
And the rest is taken up by
Continuous Integration setup.
However, Rain proven to be difficult to use with Nginx, which I need to use in new setup. As a result, Storm was written from scratch to enable me to enjoy Rain but in Nginx environment with long overdue features.
Well, look at how simple it is. This is the whole code for index page:
<?php require_once('header.php');?> <?php foreach(posts() as $post): ?> <div class="post"> <h1><a href="<?= $post->permalink; ?>"><?= $post->title;?></a></h1> <div class="body"> <?= $post->content ?> </div> <div class="ender"> published at <?= $post->published_at; ?> by <a href="/search=<?= urlencode($post->author)?>"><?= $post->author; ?></a> </div> </div> <?php endforeach;?> <?php pagination();?> <?php require_once('footer.php');?>
- PHP 5.6
- Git 4.Good text editor (Pick your poison)
What Storm did not have:
- User login online.
- Category. but we do have tags
- Dashboard. This is not
- WYSIWYG editor. Again, this is not
- Comments. Use Disqus instead.
- CDN compatible
- Simple Analytics
- Subscription / Newsletter with AWS integration
Which brings this
rant post to its main caveat: if you are not web developer, and not familiar with git workflow, most likely Storm is not for you.
For 1% of you that fall in that little spot: hey buddies!
ps: If you have any suggestion to further simplify Rain, please do so in github issues. Better yet: fork and pull request.
pps: Rain was released under MIT opensource license. Have no fear of using it in any way whatsoever.