Right now the Create Account page has these labels/forms and
descriptions:

**Username***This is the name other users will identify you with.**Password***Try
to use a strong password!
**Confirm password***Type it again here to make sure there are no spelling mistakes.**Email address***Your
email will never be published.

I think these are still my placeholders.


-  Some of these could go (especially the one under "Username" I
   think)
-  Some of them should be changed to something more
   useful/descriptive. Which ones though, and what should they be
   changed to?
-  There are probably several other form pages that could use
   descriptions, but we should open additional bugs for those (like
   this one:
   `http://bugs.foocorp.net/issues/467 <http://bugs.foocorp.net/issues/467>`_)

I unwittingly triggered an extra MongoDB version dependency because
I was running MongoDB v1.2.2 on omgmg (bad Caleb, bad!). The
symptom is as follows:


-  media items show up on root.html, but the link to
   /u/this-is-my-slug gave 404 errors. However, the
   /u/objectid\_string link worked. That is, until later Elrond found
   one for which the slug link 404'ed and the objectID link 500'ed. I
   don't have the traceback.

Chris investigated, figured out the problem was probably a MongoDB
version issue, cleaned up the mess by upgrading MongoDB, and
narrowed the issue down to older MongoDBs not being able to drop
indexes...or something like that. The exact cause remains unknown,
but what is known is that there is another MongoDB version
dependency lurking in the inky shadows somewhere between v1.2.2 and
v1.8.3.

If the dependency is met by v1.3 then the docs are correct.
Otherwise the docs are incorrect.

We could narrow down the version dependency in two ways:


1. Actively by stepping through MongoDB releases on one machine
   from v1.2.2 until the ambiguously defined issue is resolved.
2. Passively by keeping an eye out for this error in IRC, and
   asking users to report their MongoDB versions here before
   updating.

I'm happy to do `#1 </issues/1>`_ using the old omgmg envball and
Chris's 404 test (below). Meanwhile please consider #2.

test -
`http://omgmg.dyndns.org:6543/u/isylja/m/spielkind-2/ <http://omgmg.dyndns.org:6543/u/isylja/m/spielkind-2/>`_
gives 404 error. First MongoDB version without the 404 error meets
the "dependency." That's the best I can think of for now.

We need a new design for
`http://mediagoblin.org/ <http://mediagoblin.org/>`_ for the 0.1.0
launch! This is the site about the software project, not an actual
instance of the software. The colors should match a little bit
closer to our MediaGoblin software, though the look and feel does
not have to be the same (in fact, maybe shouldn't be, as the
software is designed to be non-invasive so that the media can stand
out, but this is marketing material, and so the design **should**
stand out on `http://mediagoblin.org <http://mediagoblin.org>`_)

I made a vague ascii art mockup for the frontpage.

::

    |         |_blog_|_wiki_|_Download_|
    |                                  |
    |           MediaGoblin            |
    |                                  |
    | .------------------------------. |
    | | Art   Text describing GMG    | |
    | |       goes here!             | |
    | |        - bullet              | |
    | |        - point               | |
    | | .-------. .------. .-------. | |
    | | |       | |      | |       | | |
    | | |scrnsht| |scrnsh| |scrnsht| | |
    | | |       | |      | |       | | |
    | | '-------' '------' '-------' | |
    | '------------------------------' |
    | .--------. .--------. .--------. |
    | | Run it | | Use it | | Join us| |
    | |        | |        | |        | |
    | '--------' '--------' '--------' |
    |  .----------------------------.  |
    |  | News!                      |  |
    |  |  - Headline!               |  |
    |  |  - Headline!               |  |
    |  '----------------------------'  |

The idea of this is like so. There's something similar to the
top-navigation like we have now in the upper right, but the rest of
the frontpage is broken up into three primary sections


-  **First section sells it:** provide a cute image of the
   mediagoblin mascot, provide text perhaps with bullet points
   explaining it generally. Directly underneath the text/image but in
   the same block is a carousel of screenshots
-  **Second section directs you:** Three columns, each one targeted
   with information to properly direct members of our three target
   audiences (Administrators, site-users, contributors)
-  **Third section informs you of updates:** Just headlines from
   the blog with datestamps which link directly to recent entries.

Example detail of an element from the second section:

::

    .---------------------.
    | Run it              |
    |---------------------|
    |  Run MediaGoblin!   |
    |  Be awesome!        |
    |                     |
    |   - Here's the docs |
    |   - Maybe another   |
    |     bullet          |
    '---------------------'

We should also:


-  consider reorganizing other sections of the site
-  add archiving features to the blog, probably the yeararchives
   plugin
   `http://pyblosxom.bluesock.org/registry/archives/yeararchives.html <http://pyblosxom.bluesock.org/registry/archives/yeararchives.html>`_