This is the project website for Ode (pronounced oh-dee), a personal publishing engine for the web. Ode is unique in that it is designed to be simple – not necessarily easy.
Simple means understandable (at least it does here).
In July I first announced that I was thinking of moving the community forum for Ode.
After recently upgrading to the latest version of Vanilla from an early release candidate, it seemed like as good a time as any.
The new address is: http://forum.ode-is-simple.com
Please update your bookmarks.
Here's a little poem to help you remember:
The community forum for Ode has moved.
The address was ode-is-simple.com/vanilla2_forum,
and now it's forum.ode-is-simple.com.
Hope to see you there.
Maybe not the most beautiful of poems but informative :)
There's a new discussion forum for Ode at ode-is-simple.com/vanilla2_forum.
Though I already mentioned this earlier I think it deserves a post of all its own.
The forum software is Vanilla, which I've chosen because it at least wants to be straightforward.
Though I am hosting this site, I don't want to get heavily involved w/ related issues. Unfortunately, I've run into some problems, and expect that you might as well. If we can agree to stick to the basics and we should be ok.
!--jump--!
Currently there are no discussions posted, but I have prepared some initial categories. Feel free to take a look. If you do have an interest in this project I recommend that you register as a member.
Registration requires that you submit:
(Gender? What's that about? I couldn't tell you.)
That and a captcha and you're in.
I hope to see at least a few of you there.
Just a small update to the release. There is in fact no change to Ode itself or bundled theme(s), and addin(s). (The version and build numbers are unchanged.)
There is no need to download this release if you have r1.
What is different?
!--jump--!
1 - I've added .html formatted versions of both the abbreviated and detailed the installation instructions.
The previous release included only plain text instructions which were inconvenient for some users because of issues related to text wrapping and line ending inconsistencies across platforms.
I am keeping the plain text versions of the instructions in along with the new html formatted versions for those users who prefer to use a plain text editor.
For anyone who is using the plain text installation instructions be aware:
You may need to convert line endings for your platform.
These instructions were prepared on Mac OS X using the default line endings for that platform. They should work for Mac OS X and other Unix-like operating systems but will need to be converted for Windows, Mac OS Classic (OS 9 and earlier), and possibly others.
The installation files are not hard wrapped.
You will need to wrap the lines at some reasonable width or turn on soft wrapping in your editor.
Again, you can avoid these issues by using the html formatted version of the installation instructions.
2 - I've added a changelog.
Just a quick post to officially announce that Ode release 1.0 is available (and also).
You'll find a download link for the release in the sidebar at ode-is-simple.com/home.
You'll find several new posts related to installation and addin development on the blog.
Why the new site? I wanted a place to post regular updates about the project and other related news and info without disturbing the introductory info at ode-is-simple.com/home. (Please bear with me as I straighten all of this out.)
!--jump--!
I will be working on this consistently in the foreseeable future.
Next, I will be focusing primarily on documentation describing Ode's features (most of which are not obvious). Expect an overview by early next week.
Also look for:
More themes, addins, documentation, a community site, and more.
Stay tuned.
Who has 2 thumbs and can't seem to quite get his project released? This guy (he says gesturing toward himself with both thumbs).
Another deadline and another delay. This time only a day or two but I'm not happy about it. No excuses. There aren't any snags. Everything is just taking me longer than I had expected.
So it's Sunday night at 11:39 PM and I don't have Ode posted. It's not going to get done in the next 20 minutes. My best estimate is tomorrow. I'll pull a name out of a hat and let someone know they've 'won'.
The new deal is this: if I don't post it by Tuesday, March 9th at 11:59pm EST, someone's getting $40. Two days later I'll make it $80. Two days after that $160 and so on. If there's any good news it's that I must care about this enough to lose $20 rather than just throw something up. I don't think I care another $40 worth, so I'd bet it's going to be up by Tuesday night.
Ode release date slips again. If it's not available by the end of this week I'll give one annoyed prospective user $20.
No excuses (but also no problems). I'm just trying to make sure that there are no silly hang-ups (def: hang-up, noun informal, an emotional problem or inhibition) - that's not the meaning I intended but it's probably the right word to use :)
A first release means dealing with a number of issues that I've put off until now. I do not anticipate this sort of delay with subsequent releases, which is good because I'd bet there will quite a few of them. (Did I mention that upgrading Ode is as simple as replacing a single file?)
So here's the deal. I will have a first release of Ode available for download before 11:59pm EST this Sunday (2010/0307) OR else...
!--jump--!
...if I miss this release date I'll give away to one lucky person:
a $20 iTunes gift certificate OR a $20 amazon.com gift certificate OR some other gift certificate of their choosing (as long as purchasing it isn't especially difficult - at my discretion) OR I'll make a donation in the amount of $20 to a charity of their choice.
To be eligible:
leave a comment here, send me an email at ode.is.simple at gmail dot com, follow odeissimple on Twitter, or mention @odeissimple in a tweet.
If you've already done one of these things, consider yourself in the running.
Again, I'll pay IF I fail to have a release posted by 11:59pm EST this Sunday (2010/0307) which includes at least:
So it's a win-win, but only for one person I suppose. For the rest of us it's win-lose as usual.
Ode release 1.0 slips past projected date (but closer than ever).
I had hoped to make Ode available for download by the end of last week. That didn't happen. Ode itself is done. I'm working on putting together the documentation. More specifically, I'm working on the HTML version of the annotated source code. Why delay the release of the source for something like this?
!--jump--!
In my mind, and considering some of the intended goals of the project, the annotated version and the 'production' script are inseparable. This being the case, the HTML version of the annotated script is crucially important. Why? Consider the differences. While the smaller of the two weighs in at approx 242k and 6500 lines, the larger annotated version (which again largely serves as documentation for the project) is 1.3MB and 37,000 lines. HTML version of the annotated source connects the two, allowing a user to look up a corresponding section in the annotated version by referencing line numbers in the production script.
I'm just about done with this part of the project and now expect to have everything posted by the end of this week. Feel free to contact me if you have any questions or comments (robreed at gmail dot com)
A first release of Ode by next week. What does that mean?
Barring something unforeseen, I plan on having a first release of Ode posted before the end of next week (that is by the end of the day Friday, Feb 19, 2010).
Why not wait until to post this until the release is ready?
I want to give myself a target date.
Question: Could the release date slip?
Answer: Yes, I suppose it could but I'll do my best to see that doesn't happen. I'm thinking of this as a long term project. It has taken a while to get to this point, and I apologize for that, but in all likelihood it will also be around for a long time, and that will ultimately be the more important measure.
What exactly does that mean:
!--jump--!
I'll be posting two versions of the script:
I'll also be posting at least one theme initially. The idea is that several simple (understandable and well documented) themes will be available for you to use and modify however you see fit, including one, two, and three column designs - one of which should serve as a good starting point for your own unique designs.
There will be no addins available immediately but I will get those out asap. You should expect the release of one, two, or more addins a week until I've released everything I'm working on.
I said that will be two versions of the script itself, both will be executable (and functionally identical) but you will probably prefer to run the latter on your server as it is a fraction of the size of the annotated file.
I'll also be posting an HTML formatted version of the annotated script (that you can refer to online or download) that will help you to translate between the two by looking up annotations associated with line numbers in either version.
The addins you can expect shortly include:
Markdown - Adds support for the John Gruber's Markdown syntax
Indexette - Adds the ability to index posts to improve performance and other enhancements intended to stabilize post dates.
Twittererer - Adds the ability to tweet posts to the site (automatically or manually) w/ support for URL shorteners (bit.ly to start).
Editedit - Adds the ability to post with a form in a web browser. Includes a live preview of posts (including HTML and Markdown support courtesy of John Fraser's Javascript implementation of Markdown)
Jump - Adds to ability to split posts at an arbitrary point in the body so that only that portion of the body preceding the jump point shows up on category pages with a link to the permalink for the individual post which displays the entire post. Useful from preventing category pages from loading slowly when posts include media (place the media after the jump point) and helpful for analytics (allows a user to better gauge what content people are reading).
Sitemapper - Adds automatic Sitemap protocol compliant http://www.sitemaps.org/protocol.php sitemaps.
Feedback - Adds support for comments withs support for Markdown, previews, email and twitter notifications, and reCAPTCHA
We'll build from there.
Name change - There may be a name change at some point. Expect a post about this.
T shirts - I'm a big believer in project, product, and event t-shirts (and an opposer of douche-y ironic and other 'cool-kid' Ts.). Expect to see a disproportionate number of T shirts relative to the size of the project :) All proceeds go to support Ode and it's community (Ode-fest 2011 anyone? :)
ode-is-simple.com - I plan on splitting the site in a traditional website and a weblog for news and announcements. Currently it's sort of both and kind of neither. That isn't working very well. (Hard to believe, huh?)
More, better Ode - Improvements to the script itself, new addins, themes, documentation, etc.
Community - This is the one thing that's really out of my control. If you build it will they come? Time will tell. I'll do my best to make a case for the project of course (if I don't who will) but whether our not it gets used by others is largely out of my control. I'll persist with it regardless.
Feel free to email me with any questions or comments. (You should be able to find a link somewhere in the sidebar over there -->.)