Proposal: Richer project descriptions

Just going to toss out an idea myself and others have been kicking around for a few years that I'd really like to see implemented.

It would be nice to take advantage of the fact we require descriptions of projects for submission to eboard for PR/record keeping purposes. Concretely, I'd like the following functionality (and happy to implement myself):
- [ ] project descriptions may include some form of richer text, preferably markdown or something similar, possibly user choice.
- [ ] Images and other attachments (but hopefully not malicious code) may be attached.
- [ ] Projects must be marked as published in some fashion. Ideally anything that is a major project should be worth bragging about.
- [ ] Public facing project blog should be exposed, attributing contributions to project authors, this should either be linked to by the main site or incorporated.

No files, tests, or entry points are named. Start by locating the existing project submission and description flow, then determine how rich text, attachments, publication status, and project blogs would fit together. Done means a decided, scoped implementation plan covering these requirements and their safety implications.

Written by the indexing model from the issue text.