Completed Date Modification and Info Extraction

These two features were expected to be completed in a single method
but later on while coding they got divided into two because I spotted
a method that was simpler to do so. The next methods will deal with
adding a post to the index and then adding it to the archive
Add post to index functionality complete

This is fairly self explanatory. Up to 15 posts (modifiable through a
global variable) are now added to the index file and when the number
of posts equals 15 on the index page, the oldest page gets pushed out.
Next feature set to be completed is to add to the archive after which
the main set of functionality will be done
Completed Checking for month and date

Completed the code to check whether the month and the date exist in
the archive file. Now working on adding the month and year if they
don't exist after which I will work on completing adding files to the
archive. This is just a partial checkpoint commit
Add link to archive.html

Once the month and date are checked for and inserted into the archive
file, the script then inserts a link to the post into the archives.
The final step here is to create the archive file itself and add posts
to it which honestly, I think might be overkill. I don't like the
design so I might skip it for now and keep it just in develop and move
everything else to master.
Finalized Base Generator Code

This commit finalizes the basic code that does the following steps
each time a post is published:

Add a timestamp to the post.

Add the text to the index: In the future this needs to be truncated
text. Not the whole thing. Although again this is kinda debatable. I
really want to give people a painless reading experience but at the
same time if I want to encourage them to comment on the articles then
clicking through would be the best thing. Someday I'll figure out how
to integrate A/B testing into this thing and then we'll know for sure.
Till then it stays as is

Check if the time of the post exists in the archive.html file. This
process actually has an issue around the way it is coded which I
realized a little later. If a post gets pushed for publishing at
something like 23:59:59.90 on the last day of a month/year (new year
resolution posts anyone?) it'll most likely get captured as 2014
January while the post itself might be 2013 December. But this seems
like such an edge case I thought I'd handle it later while refactoring

Add the year and month to the archive file if it doesn't exist and
then add any posts under that created month.

And that's it. Still a lot of features to develop from here but from
this point it's pretty simple to start publishing and I will be doing
just that
Merge branch 'add_initial_framework' into develop
Merge branch 'develop'