- AMELIE MAY UPDATE
- AMELIE MAY MANUAL
- AMELIE MAY CODE
AMELIE MAY UPDATE
It may be completely unintuitive for anyone who didn't literally build it from the ground up.Ĭurrently, Amelie only runs on my own website, but please let me know if you decide to use it and I'll update that here!įinally, you may be wondering, why is it called "Amelie"? Well, it is small, sometimes unpredictable, brings joy to all who encounter it, and also is married to the Mice King.It's never been tested under any major load, so it may all go bananas in that case!.
AMELIE MAY CODE
The engine and the view templates were built hand-in-hand, so a serious redesign would require some editing of the engine code.Since it doesn't have an admin panel or web-based CMS, using the engine is more technical than other alternatives.It's only ever been used by one person, and he (me) made it, so it has little error checking.
AMELIE MAY MANUAL
Publishing posts to the blogroll is manual and can be error-prone. Unless it's behind a caching server, doing file lookups and generating the HTML on the fly makes it not the speediest. The generic "static" folder allows it to serve any type of file or media. No database to manage all content is loaded from files on disk. 
No admin panel or login to the app of any kind. Much of the configuration is dynamically loaded, and can be edited without a deploy. But it also doesn't need Dropbox! It just needs folders of files, which can be edited however you choose. Small, lightweight, and purpose-built for blogging. We should also talk about what Amelie does and doesn't do well: The visual design/overall structural flow of the default templates is also hugely inspired by Casey Liss and Marco Arment's sites. Honestly, you should probably just use Camel since Casey, you know, develops code for a living. But fair warning there may be unintentional inspiration snuck in. I don't recall ever actually reading anything beyond Camel's README so I think the only technical inspiration was using signs to highlight metadata. In terms of inspiration, the idea of starting from scratch with a lightweight, new engine written in Node came from seeing Casey Liss do the same with his engine Camel. It's also based primarily on Express because at this point I've been using Express for making my webservers for gosh, four years? Five? So, as far as design goals go, Markdown, Dropbox, and not having an admin panel were the big functional ones, and Javascript/Node.js were the big implementation ones. Like every good control freak, I liked the idea of owning all my own code from start-to-finish. (I also wanted to be able to do link posts). And I never have to implement a login or admin system for my site. Which means all I really have to do to publish a post is add a new markdown file in my Dropbox folder. Write all my blog posts as simple markdown files,. I wanted to get better at Node.js, Javascript, and server side code. Yes in fact, it is a dumb and bad thing to do, but it's a dumb and bad thing I did for a few reasons: 
"Why, Andrew, did you build your own blog engine? That's a dumb bad thing to do!" you may ask. Say hi to "Amelie," a tiny, quirky blog engine built in Node.js.
0 kommentar(er)
