Blogrite has been having a steady grow since I announced it; slow but growing still. Single pages finally work and I’m pretty happy with the results. Thanks to Ruben Fonseca for helping me out with this issue I had bugging me for quite some time.
I have reached a milestone. The next thing I need to build is an index page that inevitably fetches all the posts I have. But how am I supposed to do that with files? If I didn’t build Blogrite to allow multiple content providers, I would fix the posts’ location into the filesystem and perform system calls like find or tail or something else. I wouldn’t have to think about an index file that would be built everytime I write something new, in order to increase performance. But since this is not the case, I need to come up with a solution.
What I do know is the responsability of getting the index content is the provider’s.
If I hosted content live along with the system – like I mentioned above –, find or tail system calls would be fine.
If I used Git, I could use a post-commit hook and have it change that post info in an index file.
Dropbox would be a totally different story. Are there any hooks in the service for automated scripts? (honestly I don’t think there are, feel free to prove me wrong!)
All of this considering an automated index page. There might be another ways of accomplishing this. I’m open to suggestions, throw ‘em away.
I have been working with Utopic Farm‘s jQuery Form Validator for a while, it’s a good plugin. But I have been forced to change it to suit my needs. I thought it would be a great idea to just fork it and release the changes I made previously.
I asked Tolga Arican what the license what kind of license they had for the plugin, they said none. I decided to fork the project and host it on Github, so I could make improvements to the plugin and share them with everyone. Enjoy! Props to the Utopic Farm team for building such a great plugin.
I told you before I would post a video on the development of Blogrite after Rubynorte. So here it is.
Topics included
It works!
Well, sort of. The first request is a 200, all the other ones throw me a 404 CSS file!
ERB for rendering the templates.
Classes over modules for extension?
I appreciate your feedback, you can clone the project at Github.
After fixing the bugs I still have, I intend on fetching the list of posts at the root. Or I can let the final user create an index.txt for a landing page.
I have talked a little faster today but still a bit longer than I had wished for. I’m excited to bring good news about Blogrite, I’m steadly growing my knowledge on Ruby. Rack is really interesting, I’m loving how simple and easy to learn it is so far.
Testing is fun when you start to think of features you want to implement and quickly draw a quick test that will fail and you try to make it pass. I can’t wait to start the refactoring phase, when everything is working the not-so-right way.
Still not much to show you, sadly. I’m having trouble setting my tests up so the rest flows well. If you guys help me out on this, I will be sure to mention you in the following video, you deserve it.
