Resolved - Kestrel code stats

Changed to resolved on 20Aug2013.

As of July 16, 2013

• ~7,100 lines of code
• 22 custom-created modules
• 44 templates

Bigger than I had originally planned. I thought it would be much smaller. I only needed functions to create and edit blog posts and a function to create microblog posts. Simple. I guess not.

A lot of support code was required, and then I got carried away with adding some social features that were not originally planned. It's painful to think that I may remove a good chunk of code to get back to the original, simple idea of a personal information storage tool.

But ...

Since the code exists, and I spent the time creating it, and since a remote chance exists that other people may use the site, I may keep the following users and following tags code. [kept the following code in Junco - 22jul2013]

I'll remove the code that supports liking and unliking. [completed on 22jul2013]

The reply-as-a-blog-post code will be saved, but I think I'll change the way that I do replies. [this code removed by 22jul2013]

If I'm assuming that other people may use the site, and that's the reason for keeping the following code, then I must add or keep some kind of replying mechanism. But not the traditional commenting system.

The new reply system will function similar to reply as a blog post, but a bit simpler. Meaning:

• no title line required
• possibly limited formatting options
• one reply per post - (have to ponder this one some more)

22jul2013 - leaning toward a microblog post as the reply. flat threading. -- done in late July/early August 2013

So the reply would work similar to the commenting system at Toledo Talk, but the comments or replies would appear on a separate page from the initial blog or microblog post. done in late July/early August 2013

What about replies to replies? [only if it's a new blog or microblog post, otherwise all replies will be displayed flat-threaded under the parent post. 22jul2013] -- done in late July/early August 2013 - code allows for replies to replies.

How will the replies be displayed on the one page? [flat-threaded in order the order created, youngest to oldest. 22jul2013] -- done in late July/early August 2013 - displayed as flat thread, oldest to youngest with replies to replies displayed on their own separate, flat-thread page.

Will the discussion be convoluted and hard to follow? [still a possibility, but i'll know more when testing. 22jul2013] -- done in late July/early August 2013, and yes, discussions could divert into separate threads and be difficult to follow, but links exist to see parent posts and parent discussion threads.

A reply post will appear in the user's stream making the reply post. done in late July/early August 2013

Maybe add a "replies" link to the top of the site, so that the logged-in user can see what replies he or she has received. It would be, in theory, another stream display, just like with blog posts, microblog posts, search results, following users, following tags. done in late July/early August 2013

#junco
#resolved