From Fedora Project Wiki

(Updated text in Communication section and moved it up on the page)
(removed Agenda section)
Line 118: Line 118:
* Redesign
* Redesign
* (as part of redesign)
* (as part of redesign)
== Agenda ==
The current agenda for the Fedora Websites initiative is tracked on the [[Websites/Tasks|  Tasks]]  page.
<!--Also, see [[Websites/PageRequests|  Current Page Requests]]  and ##[ ##Fedora Websites tickets] .
[[Category:Fedora sub-projects]]
[[Category:Fedora sub-projects]]

Revision as of 06:05, 29 January 2012

Artwork DesignService fedorawebsitesbanner 3.png


The Fedora Websites initiative aims to improve Fedora's image and to create the best possible interface for users and contributors on the Internet.

Contributing roles in the Websites Project

Contributing roles
These are only suggestions for contributing roles. Only your imagination sets the limits.

Join OSDeveloper.png
OS Developer

Join WebDeveloper.png
Web Developer or Administrator

About Fedora Websites

The key goals of this effort include:

  • Consolidating all key Fedora websites onto one uniform scheme
  • Maintaining content that doesn't fall under any particular sub-project
  • Generally, making the sites as fun and exciting as the project they represent

In order to better achieve these goals, as well as to benefit the community, the work of this project will involve third-party site maintainers where possible. The direct work of this project is limited to the formal Fedora site.

Work on specific sections of the sites will be coordinated by the appropriate projects. A great deal of coordination will be necessary with the Fedora Infrastructure Team , Fedora Documentation Project and the Fedora Marketing Project .

For a list of community websites, see the CommunityWebsites page.

Join the Websites Team

Please refer to the Join page on how to get the process started.

Communicating with Us

  • Mailing List: All interested contributors should join the websites mailing list.
  • IRC: The #fedora-websites channel on freenode is the best place to go for chat
  • Meetings: Our meetings page has details on when they are held.


You can help!
If you find a bug on the website you think you can help fix, try it! Here's a page on the wiki that tells you how to fix bugs on the Fedora Project website.

Bug tracking for the Fedora websites is handled through the Fedora Websites Trac instance at

Alternatively, email webmaster AT fedoraproject DOT org which is handled by websites list .

Bugs that are related to the Fedora Documentation Project can be reported using this template .

Open Tasks

Want to see a list of our open tasks? Take a look at our tickets

If you find something you'd like to take on, add a comment the ticket and add yourself as owner.

These tasks can vary from html/css changes to python scripting.


These are projects with specific goals actively being worked on for the F12 release cycle. They're in rough order of the priority discussed at the 2009-06-19 meeting, But remember, you decide priority by voting with your feet and doing things to move these projects forward.

Decision making process

Articulate and document the consensus-based decision making process of the websites team.

Team: Sijis Aviles (lead)

Next steps:

  1. Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list


Make sure all webpages are translated for the F13 release.

Team: Nobody yet! Please help!

(We aren't actually worrying about this until the end of July, but if you are interested in picking this up and keeping us from panicking then, that would be awesome. Please email the list if you are keen on this, and someone will respond to you.)

User gallery

Create a gallery for mini-interview-style user profiles and stories. This may end up being in conjunction with existing projects/frameworks/pages such as Community.

Team: Hiemanshu Sharma (lead)


CSS and Images

All CSS files and images used in Fedora sites can be found in our fedora-web.git repository. The community may use the css directly from our urls in a cascading implementation.

We encourage using the stylesheets in a cascading method when working on official Fedora Project domains (sites on this list): Websites/DomainsList

Fedora CSS in your application

Load the Fedora CSS file fedora.css

And then load your custom css file and override elements as needed. As an example, something like main.css (as used for

Boilerplate responses to common mailing list inquires

Boilerplate Responses

Completed Projects

  • Fedora Spins
  • Redesign
  • (as part of redesign)