From 3204575bfcd1f12db5945c8959073d40915cfdfe Mon Sep 17 00:00:00 2001 From: José Mota Date: Fri, 6 Apr 2012 19:40:37 +0100 Subject: Import all posts. --- _posts/2011-07-05-blogrite-on-indexes.html | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 _posts/2011-07-05-blogrite-on-indexes.html (limited to '_posts/2011-07-05-blogrite-on-indexes.html') diff --git a/_posts/2011-07-05-blogrite-on-indexes.html b/_posts/2011-07-05-blogrite-on-indexes.html new file mode 100644 index 0000000..a7e6646 --- /dev/null +++ b/_posts/2011-07-05-blogrite-on-indexes.html @@ -0,0 +1,23 @@ +--- +layout: post +title: Blogrite — on indexes +tags: +- Development +status: publish +type: post +published: true +meta: + _edit_last: '1' +--- +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. + + +All of this considering an automated index page. There might be another ways of accomplishing this. I'm open to suggestions, throw 'em away. -- cgit v1.2.3-54-g00ecf