Opened 9 years ago

Closed 9 years ago

#291 closed defect (fixed)

New proposal for MediaGoblin front pages

Reported by: Jef van Schendel Owned by:
Priority: minor Milestone: 0.2.1
Component: component1 Keywords:
Cc: Parent Tickets:

Description

Currently, when you install MediaGoblin, you'll get the standard
front page which decribes what MediaGoblin is, with the whole "Hi
there, media lover! MediaGoblin is..." bit (as you can see on
`http://omgmg.dyndns.org:6543/ <http://omgmg.dyndns.org:6543/>`_).

I'd like to propose a different kind of front page. Since
MediaGoblin will be federated and all that, we'll have multiple
instances running, which people can customize as they want. One of
these could be a website for Pokemon images, while another one
could be for Harry Potter fanart. These will have different uses,
different audiences, different names and probably customized
styles. The only thing they have in common is that they're powered
by MediaGoblin.

So, I propose we kind of push the MediaGoblin "promotion" to the
background. We've already got "Powered by MediaGoblin, etc" in the
footer. I think we can remove the MediaGoblin logo in the top left,
since these sites won't *be* MediaGoblin but just *run* by it. Then
the front page could be used to explain what kind of website it is,
and maybe mention that you can use your MediaGoblin account here.

`Here's kind of what I have in mind. <http://schendje.fedorapeople.org/temp/old_new.png>`_
The top one is the current edition, obviously. :)

What do you guys think?



Subtickets

Change History (3)

comment:1 Changed 9 years ago by Christopher Allan Webber

That looks good to me.

I think there's one of two ways we could accomplish this...


-  via theming
-  via a config file option for frontpage text

Actually, they're not really mutually exclusive either.



comment:2 Changed 9 years ago by Will Kahn-Greene

The original url for this bug was http://bugs.foocorp.net/issues/637 .

comment:3 Changed 9 years ago by Jef van Schendel

Component: component1
Milestone: 0.2.1
Resolution: fixed
Status: acceptedclosed

Pretty sure we fixed this, so closing it.

Note: See TracTickets for help on using tickets.