Yesterday, I tested the Minow framework with another theme that I personally like because of simplicity and card-layout – Shaken Grid. As earlier, I am not the owner or maintainer of the theme, I just ported it to Minow.
I did this experiment to identify theme-requirements early (lean methodology) with minimum efforts and resources.
Read more …
Minow (Minow Is Not WordPress) Engine can now read data from data-store. It’s not generic enough though – right now hard-coded to Google App Engine, but nevertheless.
Here’s what I’ve done since last push:
- Model for localized content is ready
- Basic logic to retrieve content for a given locale (not parent, no fallback) is ready. For example, if the language is “hi_IN” (Hindi-India), it – as of now – can get you the content for “hi” and/or fallback to “en_US” / “en”.
As of now, the language is a query-parameter… will enhance to parse “accept-languages” header with priority (q=0.3 etc)
- Nest theme has been updated to use the “real” data
- Implementation exists to lazy load data from the store – don’t load the posts until they’re really required. A lot of WordPress templates do not have blog on their landing page
- And of course, a piece of code generate sample data 😉
Read more …
I think this is a dream for almost every blogger… well, at least my and at least hundreds of thousands of others.
Most of the other results that you’ll find on search engines relating to WordPress and Google App Engine are about running WordPress on GAE/J by using Caucho Quercus – a bridge between PHP and Java. However, if running / simulating PHP on Java was that easy, PHP on GAE would not have been most starred issue.
And that made me think… how about creating, may be, yet another blog engine for GAE. And what better than taking clues from WordPress.
So, that gave birth of Minow, acronym for Minow Is Not WordPress. Yes, it’s a recursive acronym – see http://en.wikipedia.org/wiki/Recursive_acronym for what I mean.
Read more …
My earlier “Hello World” case studies are now live at http://m10v-helloworldapp.nodester.com/
btw, in case you are wondering how I got the Mojit up and running using “
node server.js” than the regular “
mojito start“, read my last post at http://www.m10v.com/2012/06/yahoo-mojito-on-standard-node-servercloud/
And here goes what it looks like:
Getting started with Yahoo! Mojito is pretty straightforward. The only catch is, you must issue a
mojito start command.
The problem that we get into is that most of the public Node.js clouds have no idea about this new command. All they know to do is
Recently I tried my hands with Nodester (www.nodester.com). Standard mojito code failed since server.js only instantiated an HTTP server but did not listen.
With inputs from Terry on making the server listen, I was able to run Mojito application on Nodester.
The original discussion between Terry and myself is at http://groups.google.com/group/nodester/browse_thread/thread/e35c7eb3b122ff01
The running application is provisioned at http://gvtestapp.nodester.com/@HelloMojit/index
UPDATE: The application is now available at http://gvtestapp.nodester.com/