GNU MediaGoblin Wiki - User contributions [en]

Design/Specs/Media processing

2013-02-10T22:46:36Z

Schendje:

While uploading media (don't mind the awful color and padding):

[[File:media_processing_uploading.png]]

In case of upload errors:

[[File:Media_processing_errors.png]]

These indicators are links to the media processing panel, which currently looks [[Media:Media_processing_panel_current.png|like this]], but should look more like this:

[[File:Media_processing_panel_mockup.png]]

All uploads from the last 24 hours are shown ("View older media" loads older entries). Uploads are sorted by (reverse) entry time. Uploads currently being processed and failed uploads are shown with a different background color.

Design/Specs/Media processing

2013-02-10T22:46:26Z

Schendje:

While uploading media (don't mind the awful color and padding):

[[File:media_processing_uploading.png]]

In case of upload errors:

[[File:Media_processing_errors.png]]

These indicators are links to the media processing panel, which currently looks [[Media:Media_processing_panel_current.png|like this]], but should look more like this:

[[File:Media_processing_panel_mockup.png]]
All uploads from the last 24 hours are shown ("View older media" loads older entries). Uploads are sorted by (reverse) entry time. Uploads currently being processed and failed uploads are shown with a different background color.

File:Media processing panel mockup.png

2013-02-10T22:43:39Z

Schendje:

File:Media processing panel current.png

2013-02-10T22:42:03Z

Schendje:

Design/Specs/Media processing

2013-02-10T22:04:50Z

Schendje:

Design/Specs/Media processing

2013-02-10T22:02:18Z

Schendje:

While uploading media:

[[File:media_processing_uploading.png]]

In case of upload errors:

[[File:Media_processing_errors.png]]

These indicators are links to the media processing panel.

Design/Specs/Media processing

2013-02-10T22:01:43Z

Schendje: Created page with "While uploading media: File:media_processing_uploading.png In case of upload errors: File:Media_processing_errors.png"

While uploading media:

[[File:media_processing_uploading.png]]

In case of upload errors:

[[File:Media_processing_errors.png]]

File:Media processing errors.png

2013-02-10T22:01:04Z

Schendje:

File:Media processing uploading.png

2013-02-10T22:00:44Z

Schendje:

File:Mockup.png

2013-02-09T00:58:17Z

Schendje: Schendje moved page File:Mockup.png to File:Dropdown mockup.png

#REDIRECT [[File:Dropdown mockup.png]]

File:Dropdown mockup.png

2013-02-09T00:58:17Z

Schendje: Schendje moved page File:Mockup.png to File:Dropdown mockup.png

File:Dropdown mockup.svg

2013-02-09T00:57:22Z

Schendje:

File:Dropdown mockup.png

2013-02-09T00:56:51Z

Schendje:

Design/Specs

2013-02-09T00:54:45Z

Schendje: Created page with "Design specifications for MediaGoblin features * Design/Specs/Dropdown: a dropdown mockup * Design/Specs/Media_processing: media processing panel, processing and erro..."

Design specifications for MediaGoblin features

* [[Design/Specs/Dropdown]]: a dropdown mockup
* [[Design/Specs/Media_processing]]: media processing panel, processing and error indicators

Design

2013-02-09T00:51:18Z

Schendje: Add Design/Specs; change "usability" to "interaction design"

Welcome to the Design Shack™, where we collect all things design in and around MediaGoblin.

* [[DesignDecisions]]: general musings on the MediaGoblin name, software choices and licensing decisions
* Graphical design
** [[Design/Appearance]]: about MediaGoblin's appearance and style; good reading material if you'd like to contribute
** Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html
* Interaction design
** [[Design/Specs]]: design specifications for features
** [[User_Experience]]: a collection of user test reports
** [[Feature_Ideas]]: feature suggestions and brainstorming space (for more specific features or bugs: use the [http://bugs.foocorp.net/projects/mediagoblin/issues bug tracker])

== Join us ==
MediaGoblin's design is not a fixed thing. Rather, it's in a constant state of flux and we are always trying to improve it. If you'd like to help, [http://www.mediagoblin.org/pages/join get involved]!

MediaGoblin.org v2

2012-05-06T16:07:01Z

Schendje: /* Reasons for the redesign */

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. However, it could use some serious updating. I had several things I wanted to improve:

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media!" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and bug tracker, but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links"? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity
* Includes several changes to the layout

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

MediaGoblin.org v2

2012-05-06T15:56:12Z

Schendje:

This page tracks the MediaGoblin.org website redesign and is maintained by [[User:schendje|schendje]].

== Reasons for the redesign ==

I was also the one who created the current [http://www.mediagoblin.org MediaGoblin.org] design. Whoever, it could use some serious updating. I had several things I wanted to improve:

* '''Immediately and clearly explain what MediaGoblin is and what it does.''' I do not think this is clear at all on our current homepage. It begins with "The perfect tool to show and share your media!" which sounds positive, but doesn't really explain anything. It goes on with four more bullet points, about the community and the GNU project among other things, but none of these provide any information about MediaGoblin's functionality.

* '''Provide an easier way to get started with MediaGoblin.''' The current design has a big line of text in the middle saying "Get started with the latest MediaGoblin release", which seems pretty straightforward. But then it provides you with three choices, or maybe three steps, and it is unclear which one you should pick or start with.

* '''Remove the need for a separate tour page.''' Currently, we point visitors to our Tour page to learn more. This page contains plenty of information and screenshots, which is good. However, I think it would me more effective if MediaGoblin was introduced like this right on the homepage. Therefore, I wanted to combine the homepage and the tour page into a single page.

The homepage should also contain other information, such as links to the repository and bug tracker, but in my opinion its primary function should be to explain what MediaGoblin is and to get people started with it quickly.

== Request for feedback ==

One of the reasons I created this page was to gather feedback. If you are interested, please keep checking this page for any updates and let me ([[User:schendje|schendje]]) know what you think. The best place to reach me would be the MediaGoblin IRC channel, which is also where I'll announce any updates.

'''Quick note #1:''' these mockups are free for you to adapt. A picture is worth a thousand words so if you'd like to change something, download and edit the [http://schendje.fedorapeople.org/goblin/homepage/wireframe.svg SVG source file] and show it around!

'''Quick note #2:''' virtually all of the copy in the current mockups is placeholder text. Therefore, comments on the content of the page will not yet be of much use. I will be working on replacing it with proper copy as soon as possible, so we can also gather feedback on that part of the design.

== Mockups (most recent one at the top) ==

=== Third iteration ===

http://schendje.fedorapeople.org/goblin/homepage/wireframe3.png

* Almost the same as previous, but added screenshots
* A short explanation for this layout: http://schendje.fedorapeople.org/goblin/homepage/layout_explained.png

Questions:
* Is it obvious that the images are screenshots? They can of course be clicked to show a bigger version.
* What is a good position for the "quick links"? They will be in the top corner on any other page on the website, but I think they may demand too much attention if we put them at the top of the homepage as well.

=== Second iteration ===
* Slightly higher fidelity
* Includes several changes to the layout

http://schendje.fedorapeople.org/goblin/homepage/wireframe2.png

=== First iteration ===
A first low-fidelity wireframe: http://schendje.fedorapeople.org/goblin/homepage/wireframe.png

=== Old design ===

A mockup of the current MediaGoblin.org design: http://schendje.fedorapeople.org/goblin/homepage/final.png

User:Schendje

2012-05-06T15:23:13Z

Schendje:

I'm Jef and I have [http://www.jefvanschendel.nl a website].

For MediaGoblin, I design things and pretend to be able to code.

To contact me about MediaGoblin-related things, look me up on the MediaGoblin IRC channel.

Main Page

2012-05-06T15:22:53Z

Schendje: Fixed link to Join page

= Want to Join the MediaGoblin Community? =

We’re really glad that you want to join the MediaGoblin community!

There are a variety of ways to help and support MediaGoblin and to join the team. If you want to code, great, if not, even better! MediaGoblin interested contributors in many different roles: users, system administrators, technical writers, testers, evangelists, UI/UX and graphics designers, cheerleaders, and dreamers.

This wiki covers a variety of ways that you can get involved with MediaGoblin as well as instructions on how to get started.

== Hang out with the MediaGoblin folk ==

MediaGoblin has a mailing list and an IRC channel where we hang out. See [http://mediagoblin.org/pages/join.html our join page] for links.

Please drop by and say “Hi!” And, if you’re looking for something to do, just ask---there’s always work to be done.

== Take Part in the Monthly Meetings ==

Each month is a [[Meeting]]. You can take part and help decide on the future of MediaGoblin. Or just be around and see what's happening live!

== File Bugs / Triage Bugs ==

Issue reports are critical for all projects. Identified bugs give developers a basis for beginning work, and providing an idea of what features and issues are most important to users and the overall usability of the software. If you identify errors, flaws, unexpected behaviors, or deficits that impede use, file a bug.

* [[File Bugs]] -- notes on filing new bugs/issues/feature requests
* [[Feature Ideas]] -- notes on possible features
* [[Triage Bugs]] -- notes on triaging

== Write Code / Fix Code ==

If you are a coder and you would like to write code, the repository is hosted on gitorious. Clone or fork the repository and start poking around. Become familiar with this manual for an overview of how the software works and is used. Consider the contributor wiki for more information about the project, our preferred methods, and guides for developing MediaGoblin. We even have tips on becoming a coder and we’re willing to help!

* [[HackingHowto|Hacking]] - notes on making and sending in code contributions
** [[BeginnersCorner|Beginner's Corner]] - resources for those who are new to Python, MongoDB, or Git.
** ''Started from an older version of the Hacking Howto? We switched from buildout->virtualenv, so look at [[Moving from buildout to virtualenv]] for information on how to move over.''
* [[Git workflow]] - How to go about submitting patches via git.
* [[Templating]] - How our templating structure is set up
* [[Code overview]] - Overview of the structure of the codebase

== Send Encouragement / Spread the Word ==

Sometimes, a nice word, simple encouragement, and interest in the work we’re doing is enough to inspire a tizzy of productive work. Just a bit more interest and encouragement can even make the difference between a complete feature and limited functionality; between a completed milestone and lost momentum.

Similarly, MediaGoblin, and the movement for free network services, is always in need of encouragement. Use free network services, understand the principals behind the movement, be able to articulate the benefits of free network services and the problems with psudo-free applications that don’t respect the users’ freedom.

Write a blog post, post a status update, drop by the listserv or join #mediagoblin on freenode.net and let us know. See [http://mediagoblin.org/join/ our join page] for links.

== Write Documentation / Edit Documentation ==

* [[Documentation quick start]] - How to contribute to the documentation effort.
* [[ManualStandards]] - covers the standards for writing the user manual (forthcoming.)

== Test MediaGoblin ==

Do you have access to the web? Do you like sharing your opinions? If so, we need your help to test MediaGoblin! Testers play around with the current test instance, note what operating system and browser they use (notes on multiple set-ups are also helpful) and take some notes. That's it! It's a very important task that doesn't require any special knowledge and you're done in under an hour. Ready to help?

* [[User Experience]] - user experience testing. Includes link to an instance you can try!
* [[UnitTests|Unit Tests]] - all about the unit tests

== Translate MediaGoblin ==

If you know English and another language and feel comfortable translating elements of the interface or even the documentation, we’d love to have help translating the software and resources.

* [[Translations]] - How to translate stuff or update the translations

== Become a User ==

Coming soon!

We’re building MediaGoblin for us and for you but really you’re one of us and I am you and we are we and MediaGoblin is the walrus.

We're planning to launch our own public instance of MediaGoblin in the near future--probably in the September/October 2011 time frame. When we do, sign up for an account, use the service and relish in the thought that this service comes with a heaping side of Freedom and you can salt and pepper it to your liking.

== Help Others ==

Have you spent time with MediaGoblin? If so, your experience and wisdom are invaluable and you’re the best person we can think of to help other users with their questions.

Hang out on the IRC channel and help answer new peoples' questions. See [http://mediagoblin.org/join/ our join page] for links.

== Run your own MediaGoblin Instance ==

Are there things about our instance you want to change? Are there things about other instances you wish were different? Want to test upcoming changes? Want to create patches to implement things you need? That’s great—you can run your own instance!

* [[Configure_MediaGoblin|Configuration]] - Learn about MediaGoblin configuration files and file options.
* [[Deployment]] - General deployment advice
* [[Scaling Down]] - Minimizing MediaGoblin's resource requirements
* [[Virtual Machine Hosting]] - Deploy your own publicly available MediaGoblin server using [http://aws.amazon.com/free/?utm_source=adwords&utm_medium=cpc&utm_campaign=CPC_Google_AWS_ec2&utm_content=TextV01_PP_V01_EC2&trk=CPC_Google_AWS_ec2 Amazon's free EC2 tier].

== Create a Theme ==

Coming soon!

MedaGoblin development is premised on the idea that the entire interface for the platform be completely theme-able. If you have a design or theming background, consider developing themes for MediaGoblin. New themes help test the theming system, provide attractive and appealing interfaces for prospective users. If you want to start a new theme but don’t know where to start, touch base with the development community on the list or in the IRC channel for more information.

= Technical project documentation =

* [[DesignDecisions]] - covers design decisions (FIXME - this needs to be split up)
* [[Storage]] - How MediaGoblin's internal storage system works.
* [[Processing]] - What happens after you submit your image/video/etc? Processing! More about that.
* [https://gitorious.org/mediagoblin/mediagoblin/blobs/master/extlib/README External Library Policy] - covers use of external libraries
* [[User:Cwebber/braindumps]] - Chris Webber's braindumps (you can help refactoring these into real sections of the site!)
* [[Multiple media support]] - Design plan for multiple media support

= Inner workings of the secret sanctum =

* [[IRCBot]] - covers our irc bot
* [[ReleaseProcess|Release Process]] - covers the release process
* [[Update the website]] - Learn how to update mediagoblin.org!

MediaGoblin.org v2

2012-05-06T14:30:31Z

Schendje: Created page with "This page describes the MediaGoblin.org website redesign."

This page describes the MediaGoblin.org website redesign.

Meeting

2012-05-05T16:00:14Z

Schendje: /* Next Meeting */

== MediaGoblin Monthly Meeting ==

'''When:''' 9:00 am Pacific Time first Saturday of the month. [http://www.timeanddate.com/worldclock/converter.html Convert time to your timezone]. Print current UTC time: <code>date -u +"It's %F %T UTC"</code>

'''Where:''' IRC #mediagoblin on irc.freenode.net

Always announced several days in advance on the [http://lists.mediagoblin.org/pipermail/devel/ mailing list] as is date adjustments, agenda discussion and other meeting preparation.

'''Purpose:''' The idea is to discuss the past month, what happened, what was good, what should be done better. And to create roadmap for the upcoming month and assign tasks to people willing to handle them.

Typical Agenda topics:

* What happened in the last month, what was good, what could be better next time?
* What should be done next month?

Meetings are logged. [http://mediagoblin.org/irclogs/ Logs for past meetings.]

== Next Meeting ==
May 5th, 2012, 9:00 am Pacific Time (2012-05-05 16:00 UTC)

* Post-release reflections
** Woohoo, release!
** How did this release process go?
*** We should talk about that conference.
** What's left to clean up?
*** Mongokit->SQL "style" query conversion?
*** Other cruft code?
* What are our next goals?
** Plugins
** Federation
** Favoriting
*** Take that, Pinterest! ;)
** Galleries
** Theming
*** Using sass would be neat
** Access restrictions
*** User management, or having a "secret url" that is not in the photo index that you can share with friends and generate as needed for any media type
** What about traffic? Some of us will host GMG on limited plans.
** Some kind of coding guidelines? Do we have a philosophy like "Keep it Simple, Stupid"
*** This concerns things like: Should plugins land in core eventually, do we want to support ALL THE MEDIA TYPES, ...
** Things that have been hanging???
** Bugtrackers and milestone?
** More??? We should organize things!
* jancborchardt and his team of UX wizard-students
* Website redesign

== Past Meetings ==

=== 2012-04-07 16:00 UTC ===

* Post-SQL stuff
* Pending 0.0.3 release!
* Are there stray patches/branches to be merged?
* Our glorious upcoming plugin future! (Update from Will)

=== March 3rd, 2012, 9:00 am Pacific Time ===

* [[GSOC 2012]]
* State of the SQL transition (preview: it's super close, but we need help!)
* Plugin discussion (Will can't make this, but we should talk about use cases)
* MediaGoblin at upcoming conferences
* PageKite accounts

=== 2012-02 (held on 2012-02-04) ===

[http://mediagoblin.org/irclogs/irc_meeting_2012-02-04.txt IRC log]

* Code style guide? See also: http://issues.mediagoblin.org/ticket/197
* Kuneco/federation
* API
* More testing discussion?
* Theming?
* Preliminary plugin discussion
* Status update from the "SQL Team".

Some of the decisions:

* file an issue about proper <audio> support.
* some TODOs recorded

=== 2011-12 (held on 2011-12-03) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-12-03.txt IRC log]

* We plan to create a plugin system. Do we want to create that soon or push it off until things settle a bit more? ([[User:Willkg|Willkg]] 08:54, 10 November 2011 (EST))
* [[Feature Ideas]]: What should we do about the wiki page? Keep it and have it as a monthly topic for "what next"? Convert everything to long waiting bugs?
* Possibility of an [[SQL Database Backend]]?
*: 'executive summary' (well, you should read the long docs): "We could move to sql. It's probably replacing one type of pain by another type of pain, but those are somewhat comparable. Leaving the main question: Do we want to occupy our main devs for some long time with this task and loose momentum?"
* Schendje's [http://wiki.mediagoblin.org/Feature_Ideas/Activities activities proposal]
* "Coming up next" blogpost draft by Deb Nicholson
* Jef's requests:
** Ticket #466 "Use of "Submit" in site copy is sterile and not as friendly and welcoming as it could be". I'd really like to change this soon to something more suitable. How can we improve the wording here? Some alternatives have been mentioned in the bug report, but which one should we pick? Link: http://bugs.foocorp.net/issues/466
** The concept and naming of "favourites". We'll (hopefully) be able to "favourite" media soon, which I *think* means that 1) it'll work like a "I like this" comment, a quick token of appreciation, 2) it'll be added to your list of favourites so you can save and promote it, and 3) we could maybe use the number of favourites as a ranking. What I'd like to know is: is that the intended purpose? If so, should we name them favo(u)rites or something else? "Like", "love", "save", "appreciate", "heart", "high five" and many more could all be contenders. And the name should be consistent with the action and purpose, of course. So I'd like to clear up how and why we will use favourites and what we should call them.

=== 2011-11 (held on 2011-11-05) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-11-05.txt IRC log]

* What happened in the last month, what was good, what could be better next time?
** Release:
*** Good: 0.1.0 released!
*** Bad: postponing vs not postponing
** Sites and deployment documentation:
*** Good: new mediagoblin.org
*** Good: deployment documentation
*** Bad: py-bcrypt’s site was down just after the release, so the virtualenv deployment didn’t work, and it wasn’t clear how to fix it.
** Live instances:
*** Joar has a live instance!
*** But what does it mean? Should ordinary users start using it?
**** Details at [[User:Joar/mg.wandborg.se]] -- [[User:Joar|Joar]] 17:01, 6 November 2011 (EST)
*** nyergler added a note about "heartbeat"/status to API notes
* What should be done next month?
* Starting real work on federation (via OStatus)... and do we split any of this work out into its own library?
* An API
* Creative Commons licensing tools
* Merging in the multimedia/video branch
*: (this is *very close* already actually thanks to the hard work of Joar Wandborg! But we need some help on the gstreamer front to fix a few issues... if you or someone you know is an expert in this area we could really use their help to make the videos that come out smoother!)
* Rollover items from 0.1.0
* Multiple file upload interface
* Drag and drop uploads interface (probably related!)

=== 2011-10 (held on 2011-10-01) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-10-01.txt IRC log]

This month's meeting was a quickly announced short meeting. The project is getting back on track and next month's meeting will be scheduled more properly. A bunch of people were around.

The most important decisions:
* The project will keep monthly releases. They're the heartbeat of the project.
* Release 0.1.0 this sunday/monday.
* New website will hopefully be deployed in the next few days.
* And the following things are planned to happen during this month: Most importantly federation. The developers have decided to make up their minds on what federation aactually should mean for MediaGoblin. Concerning code, probably "activity streams" are the first goal. If there is no (good) python library for this, a new stand alone library may be created. If so, a name for it has to be found. It should have something about communication in it. And the other thing to happen during this month is an ongoing discussion about "bus factor".

=== 2011-09 (held on 2011-09-03) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-09-03.txt IRC log]

=== 2011-08 (held on 2011-08-06) ===

[http://mediagoblin.org/irclogs/irc_meeting_2011-08-06.txt IRC log]

User:Schendje

2012-03-16T21:18:05Z

Schendje: Created page with "I'm Jef and I have [http://www.jefvanschendel.nl a website]. For MediaGoblin I design things and pretend to be able to work with code."

I'm Jef and I have [http://www.jefvanschendel.nl a website].

For MediaGoblin I design things and pretend to be able to work with code.

Design/Appearance

2012-01-09T19:46:55Z

Schendje: /* Default theme */ Added background texture image

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

It is, however, '''not meant to be a definitive up-to-date guide'''. It serves as an introduction, but experiments with the design are common and the latest design specifications will always be found in the MediaGoblin software itself.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.
[[File:Background.png]]

The basic color palette used for MediaGoblin is shown below. Many other colors based on the same hues are also used.

{| class="wikitable" width="400px"
! Color || Hex || Sample || Used for e.g.
|-
| Text grey || #C3C3C3 || [[File:Color_text_grey.png]] || Body text
|-
| Pure white || #FFFFFF || [[File:Color_pure_white.png]] || Headers, logo
|-
| Highlight green || #86D4B1 || [[File:Color_highlight_green.png]] || Links, buttons
|-
| Faint red || #D49086 || [[File:Color_faint_red.png]] || Form headers
|}

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a black-on-white design and increased contrast.

Color differences include:

{| class="wikitable" width="400px"
! Color || Hex || Sample
|-
| A light background || #FCFCFC || [[File:Color_light_background.png]]
|-
| Dark text || #3C3C3C || [[File:Color_light_text.png]]
|-
| Black headers || #000000 || [[File:Color_light_headers.png]]
|-
| Adapted link color || #499776 || [[File:Color_light_link.png]]
|}

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

File:Background.png

2012-01-09T19:45:42Z

Schendje: Standard MediaGoblin background texture

Standard MediaGoblin background texture

Design/Appearance

2012-01-09T19:43:55Z

Schendje: Added color samples

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

It is, however, '''not meant to be a definitive up-to-date guide'''. It serves as an introduction, but experiments with the design are common and the latest design specifications will always be found in the MediaGoblin software itself.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.

The basic color palette used for MediaGoblin is shown below. Many other colors based on the same hues are also used.

{| class="wikitable" width="400px"
! Color || Hex || Sample || Used for e.g.
|-
| Text grey || #C3C3C3 || [[File:Color_text_grey.png]] || Body text
|-
| Pure white || #FFFFFF || [[File:Color_pure_white.png]] || Headers, logo
|-
| Highlight green || #86D4B1 || [[File:Color_highlight_green.png]] || Links, buttons
|-
| Faint red || #D49086 || [[File:Color_faint_red.png]] || Form headers
|}

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a black-on-white design and increased contrast.

Color differences include:

{| class="wikitable" width="400px"
! Color || Hex || Sample
|-
| A light background || #FCFCFC || [[File:Color_light_background.png]]
|-
| Dark text || #3C3C3C || [[File:Color_light_text.png]]
|-
| Black headers || #000000 || [[File:Color_light_headers.png]]
|-
| Adapted link color || #499776 || [[File:Color_light_link.png]]
|}

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

File:Color text grey.png

2012-01-09T19:40:55Z

Schendje:

File:Color pure white.png

2012-01-09T19:40:45Z

Schendje:

File:Color light text.png

2012-01-09T19:40:37Z

Schendje:

File:Color light link.png

2012-01-09T19:40:28Z

Schendje:

File:Color light headers.png

2012-01-09T19:40:23Z

Schendje:

File:Color light background.png

2012-01-09T19:40:15Z

Schendje:

File:Color highlight green.png

2012-01-09T19:40:10Z

Schendje:

File:Color faint red.png

2012-01-09T19:39:53Z

Schendje:

Design/Appearance

2012-01-08T21:10:34Z

Schendje: /* Light theme */

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

It is, however, '''not meant to be a definitive up-to-date guide'''. It serves as an introduction, but experiments with the design are common and the latest design specifications will always be found in the MediaGoblin software itself.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.

The basic color palette used for MediaGoblin is shown below. Many other colors based on the same hues are also used.

{| class="wikitable" width="400px"
! Color || Hex || Sample || Used for e.g.
|-
| Text grey || #C3C3C3 || || Body text
|-
| Pure white || #FFFFFF || || Headers, logo
|-
| Highlight green || #86D4B1 || || Links, buttons
|-
| Faint red || #D49086 || || Form headers
|}

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a black-on-white design and increased contrast.

Color differences include:

{| class="wikitable" width="400px"
! Color || Hex || Sample
|-
| A light background || #FCFCFC ||
|-
| Dark text || #3C3C3C ||
|-
| Black headers || #000000 ||
|-
| Adapted link color || #499776 ||
|}

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

Design/Appearance

2012-01-08T21:08:56Z

Schendje: /* Default theme */

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

It is, however, '''not meant to be a definitive up-to-date guide'''. It serves as an introduction, but experiments with the design are common and the latest design specifications will always be found in the MediaGoblin software itself.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.

The basic color palette used for MediaGoblin is shown below. Many other colors based on the same hues are also used.

{| class="wikitable" width="400px"
! Color || Hex || Sample || Used for e.g.
|-
| Text grey || #C3C3C3 || || Body text
|-
| Pure white || #FFFFFF || || Headers, logo
|-
| Highlight green || #86D4B1 || || Links, buttons
|-
| Faint red || #D49086 || || Form headers
|}

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a black-on-white design and increased contrast.

Color differences include:
* A light background: #FCFCFC
* Dark text: #3C3C3C
* Black headers: #000000
* Adapted link color: #499776

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

Design/Appearance

2012-01-08T20:14:38Z

Schendje:

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

It is, however, '''not meant to be a definitive up-to-date guide'''. It serves as an introduction, but experiments with the design are common and the latest design specifications will always be found in the MediaGoblin software itself.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.
* Colors
** Text grey: #C3C3C3. Used for: body text.
** Pure white: #FFFFFF. Used for: headers, logo.
** Highlight green: #86D4B1. Used for: links, button backgrounds.
** Faint red: #D49086. Used for: form headers.

Many other colors based on these hues are used across the MediaGoblin and related websites.

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a black-on-white design and increased contrast.

Color differences include:
* A light background: #FCFCFC
* Dark text: #3C3C3C
* Black headers: #000000
* Adapted link color: #499776

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

Design/Appearance

2012-01-08T20:03:31Z

Schendje: /* Default theme */

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

== Default theme ==

By default, MediaGoblin the software and many of the MediaGoblin websites use a dark, relatively neutral theme. While beauty is important, we try to keep the theme simple and avoid unnecessary decoration. One of the reasons for this is that we believe MediaGoblin itself should stay in the background and put media in the spotlight. Another is that this makes it easier for others to theme their own MediaGoblin instances, which is also why we try to use as little images as possible in the design.

* Text: we use a typeface called [http://www.google.com/webfonts/specimen/Lato Lato], created by Łukasz Dziedzic. The MediaGoblin logo is a custom design, though it takes hints from Lato.
* Background: a very dark grey with a slight texture. The texture was added to make it easier to distinguish the background from media with similar colors. Fallback color is #161616.
* Colors
** Text grey: #C3C3C3. Used for: body text.
** Pure white: #FFFFFF. Used for: headers, logo.
** Highlight green: #86D4B1. Used for: links, button backgrounds.
** Faint red: #D49086. Used for: form headers.

Many other colors based on these hues are used across the MediaGoblin and related websites.

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a light background and higher contrast.

Differences include:

FIXME

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

Design/Appearance

2012-01-07T00:05:15Z

Schendje: Created page with "This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material. == Default theme == MediaGoblin's default...."

This page describes MediaGoblin's appearance and style. If you're looking to contribute to its design, this is good reading material.

== Default theme ==

MediaGoblin's default.... FIXME.

FIXME

== Light theme ==

Besides the regular theme, we've created a lighter version for use on the wiki, documentation and other places that might require reading longer pieces of text. It is meant to increase readability through the use of a light background and higher contrast.

Differences include:

FIXME

== Logo ==

Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html

Design

2012-01-06T23:53:58Z

Schendje: Created page with "Welcome to the Design Shack™, where we collect all things design in and around MediaGoblin. * DesignDecisions: general musings on the MediaGoblin name, software choice..."

Welcome to the Design Shack™, where we collect all things design in and around MediaGoblin.

* [[DesignDecisions]]: general musings on the MediaGoblin name, software choices and licensing decisions
* Graphical design
** [[Design/Appearance]]: about MediaGoblin's appearance and style; good reading material if you'd like to contribute
** Get and use the MediaGoblin logo at http://www.mediagoblin.org/pages/logo.html
* Usability
** [[User_Experience]]: a collection of user test reports
** [[Feature_Ideas]]: feature suggestions and brainstorming space (for more specific features or bugs: use the [http://bugs.foocorp.net/projects/mediagoblin/issues bug tracker])

== Join us ==
MediaGoblin's design is not a fixed thing. Rather, it's in a constant state of flux and we are always trying to improve it. If you'd like to help, [http://www.mediagoblin.org/pages/join get involved]!

Feature Ideas/Activities

2011-12-02T16:05:27Z

Schendje: Added screenshots with summary notes

Below is a big braindump, feel free to ignore it.

For a quick summary, here's a screenshot[http://schendje.fedorapeople.org/goblin/activities/screenshot.png] and here's one with notes[http://schendje.fedorapeople.org/goblin/activities/screenshot_notes.png].

--[[User:Schendje|Schendje]] 11:05, 2 December 2011 (EST)

== What is it ==

One of the things I ran into when using mediagoblin.com was that it's hard to keep track of what's happening. Somebody commented on one of your pictures? Your favorite artist uploaded a new piece? You wouldn't know about these things unless you actively looked for them.

That's why I'd like to propose an Activities page, which would keep track of changes relevant to you. It would consist of a separate page that lists all of these updates, but also take up a small part of your profile or the homepage in the form of a small list with the latest 5/10/20 updates.

As for the actual name, I'd like something a little more fun than the dry "Activities", like "Latest happenings" or "What's going on" or something, but the word Activities is a nice and appropriate code name. ;)

== About updates, favorites and fans ==

What do I think would count as an update? Needless to say, we don't want to alert users about *everything* that's going on. I think relevant updates would be:

* Comments on your uploaded media
* People "favoriting" your media (since that's basically the same as a "cool, I like this" comment)
* New media added by people you're "following"

For those last two, we don't even have the functionality yet, but they would provide a way for you to customize which and how many updates you receive. Do you like a certain user's stuff? "Follow" him and you'll receive updates whenever there's something new.

You could expand this even further:

* Someone you're "following" has added a comment on somebody else's media
* Someone you're "following" has "favorited" another user's media

...etc. But let's think about that later.

== Rationale ==

So, a lot of websites have an updates/messaging system. Two of these are:

* Email based systems. This is quite simple: for every update that is relevant to you, an email will be sent.
** But being spammed by emails every time something happens will get annoying quickly.
* Messaging/inbox systems. Typically used on forums and whatnot, you'll receive a message in your "inbox" for every update. So that's basically the same as email, except it's on the website itself. It'll often list your "unread" messages. They are "read" by opening them, or as on reddit, by simply clicking on them.
** But creating a system like this will take a lot of work. Also, you have to manually open each message or at least actively dismiss them.

Instead, let´s look at microblogging. On Twitter/identi.ca/Facebook(?), there's a long list of updates from people you're following. How is this different:

* You are not alerted by email or messages about every new update
* It's filled with the things you want to see, because you've selected the updates by choosing the people you want to follow
* This list is automatically updated, but you check it manually. This means ''you check the updates'', instead of ''the updates alerting you''. As a result, they won't bug you when you don't want to see them.
* The system doesn't keep track of what you've already read. You do this yourself, by remembering what you've already seen. By keeping all the updates in the list, you can always go back. To give a rough sense of time, we could add date headers, so you can see what happened today, yesterday, or earlier.

I think this last one would be the most appropriate for our software.

== So what would this look like ==

As said above, it'd consist of two parts:

* A main Activities page, listing all the updates in reverse chronological order.
* A slice of the latest X updates on other pages, like your profile page or even the homepage.

Additionally, we could create an Atom feed (since this is the perfect place for a feed) and/or have an update-me-by-email option.

Appearance-wise, I imagine it'd be fairly straight-forward. I quickly firebug'd something here: http://schendje.fedorapeople.org/temp/Screenshotsdcjnasdcsdh.png

Feature Ideas/Activities

2011-11-27T20:17:37Z

Schendje: first braindump

This page is basically a braindump for the Activities page...

--[[User:Schendje|Schendje]] 15:17, 27 November 2011 (EST)

== What is it ==

One of the things I ran into when using mediagoblin.com was that it's hard to keep track of what's happening. Somebody commented on one of your pictures? Your favorite artist uploaded a new piece? You wouldn't know about these things unless you actively looked for them.

That's why I'd like to propose an Activities page, which would keep track of changes relevant to you. It would consist of a separate page that lists all of these updates, but also take up a small part of your profile or the homepage in the form of a small list with the latest 5/10/20 updates.

As for the actual name, I'd like something a little more fun than the dry "Activities", like "Latest happenings" or "What's going on" or something, but the word Activities is a nice and appropriate code name. ;)

== About updates, favorites and fans ==

What do I think would count as an update? Needless to say, we don't want to alert users about *everything* that's going on. I think relevant updates would be:

* Comments on your uploaded media
* People "favoriting" your media (since that's basically the same as a "cool, I like this" comment)
* New media added by people you're "following"

For those last two, we don't even have the functionality yet, but they would provide a way for you to customize which and how many updates you receive. Do you like a certain user's stuff? "Follow" him and you'll receive updates whenever there's something new.

You could expand this even further:

* Someone you're "following" has added a comment on somebody else's media
* Someone you're "following" has "favorited" another user's media

...etc. But let's think about that later.

== Rationale ==

So, a lot of websites have an updates/messaging system. Two of these are:

* Email based systems. This is quite simple: for every update that is relevant to you, an email will be sent.
** But being spammed by emails every time something happens will get annoying quickly.
* Messaging/inbox systems. Typically used on forums and whatnot, you'll receive a message in your "inbox" for every update. So that's basically the same as email, except it's on the website itself. It'll often list your "unread" messages. They are "read" by opening them, or as on reddit, by simply clicking on them.
** But creating a system like this will take a lot of work. Also, you have to manually open each message or at least actively dismiss them.

Instead, let´s look at microblogging. On Twitter/identi.ca/Facebook(?), there's a long list of updates from people you're following. How is this different:

* You are not alerted by email or messages about every new update
* It's filled with the things you want to see, because you've selected the updates by choosing the people you want to follow
* This list is automatically updated, but you check it manually. This means ''you check the updates'', instead of ''the updates alerting you''. As a result, they won't bug you when you don't want to see them.
* The system doesn't keep track of what you've already read. You do this yourself, by remembering what you've already seen. By keeping all the updates in the list, you can always go back. To give a rough sense of time, we could add date headers, so you can see what happened today, yesterday, or earlier.

I think this last one would be the most appropriate for our software.

== So what would this look like ==

As said above, it'd consist of two parts:

* A main Activities page, listing all the updates in reverse chronological order.
* A slice of the latest X updates on other pages, like your profile page or even the homepage.

Additionally, we could create an Atom feed (since this is the perfect place for a feed) and/or have an update-me-by-email option.

Appearance-wise, I imagine it'd be fairly straight-forward. I quickly firebug'd something here: http://schendje.fedorapeople.org/temp/Screenshotsdcjnasdcsdh.png