Make a simple page, with link back to home, and link to reporting feedback.

It is already stored for every comment, just update the model to actually require it.

Involves removing blank=True, null=True, and migrating db.

I wrote my own commenting system for practice with recursion. Not the best idea for a production site, but this is partly a learning project for me.

After watching performance as use picks up, would probably be worthwhile to integrate django-mptt into the comment system. Perhaps replace the commenting system with something more widely used, but that's probably not necessary.

I'd like this to be able to handle front page exposure on HN. Caching the most expensive pages will make for a much snappier user experience as well.

Main pages that benefit from effective caching: index, new, discuss.

Focus on using memcache.

Search through:

• submitted links
• submitted textposts
• comments

Rank by:

• date
• points
• number comments

There will be some domains from which we do not want to accept submissions, such as paywalled news sites. Set up a model to store these domains, and make sure they are ignored.

It's helpful to know where articles are from, as well as their titles. Show just the top-level domain for each submission.

Submissions should be archived after a specified time period, something on the order of 72 hours. An archived submission can still be commented on, but its ranking_points are no longer recalculated. It can't be upvoted.

This will help from having to look through too many submissions when building the active front and new pages.

Implementation:

• Submissions should have an active flag that defaults to True.
• When recalculating ranking points, grab all active submissions. First step, find any that are older than set age. Set these inactive.
• Does this affect comments at all?

When a submission receives many comments, it's hard to scroll down and see just the first-order comments.

• Every comment should have a collapse button that hides all of that comment's descendents.
• The discussion page should let you hide all comments below a certain nesting level. ie see just the first-order comments, then expand any of those you are interested in.

Grabbing all comments for a discussion page would be easier if every comment had a direct association with a submission. Don't want to call it parent_submission, because that implies it's a first-order comment on the actual submission, not a reply to another comment.

There is some redundancy in templates. Could do a better job of identifying common pieces of information, and making template fragments for the main pages.

This would be a link on the nav bar, which shows users all of their own recent comments, with the associated comment threads. Allows people to follow up on the conversations they have started, and the ones they are participating in.

Should be a straightforward implementation.

The view functions can use a lot of refactoring, but they could also be split into a few separate files.

It would be helpful to know other people in the community. Everything is optional, though:

• Three core beliefs about education.
• What is your role/ main interest in education?
• For teachers:
  • What ages/ grade levels do you teach?
  • What subject areas do you teach?
  • Where do you teach?
• What do you think is already working well in education?
• What would you most like to see improved about education? (Might require response to what is working well before showing this? No, but strongly encourage it.)

With the variety of mobile devices people use, it is inevitable that people will accidentally upvote some submissions. Enabling people to undo an upvote leads to less frustration on the part of users, and more accurate voting for each submission.

Right now, you can only see the top 30 submissions (/index page), or the newest 30 submissions (/new page). Need a /more_submissions/x/ page, which gives the next 30 submissions.

Right now a submission is simply rejected if you submit a link that has already been submitted. Instead, it should redirect you to the discussion page for that submission, and upvote the submission for you.