From Fedora Project Wiki


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
This is only suggestions for contributing roles. Only your imagination sets the limts.

Join OSDeveloper.png
OS Developer

Join WebDeveloper.png
Web Developer or Administrator

About Fedora Websites

The key goals of this effort include:

  • Trying to consolidate all the key Fedora websites onto one uniform scheme
  • Maintaining the content that doesn't fall under any particular sub-project
  • Generally, making the sites be 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 with 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 Fedora Websites Project

To learn how to join Fedora Websites Project, please refer to the Join page. If you just have a quick fix or suggestion, give Show Us a look.


Bug tracking for the Fedora websites is handled through the Fedora Infrastructure Trac instance at (file a ticket under the Webmaster component )

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

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

A list of active page building requests from other projects within Fedora are located here Current Page Requests


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 stuff to move these projects forward.

See Website redesign 2009.

Get people who want the non-default dl option - whether they know it or not - to find and download the right thing with minimal cognitive effort and mouse-clicks.

Decisionmaking process

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

Team: Ricky Zhou (lead)

Next steps:

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


Needs a description!

Team: Ricky Zhou (lead)

Action items:

  1. Ricky will bring his critiques to the docs team and report back via email to the list.

Increase the number of first-time Fedora contributors working on F12 by putting a support system behind this page and tweaking it to reflect that.

Team: Mel Chua (lead)

Currently stalled.

Next steps (for the week of June 28, 2009):

  1. Create a project (wiki) page for this.
  2. Make a map of "entry routes" to Fedora participation, using websites as a framework - join.fp.o goes to what other pages, which go to what other pages, and so on... and what actions do people take at each page? What sequence of webpages is a new contributor likely to see? Post this to the wiki, send to list for comment.
  3. List the communication channels used by Fedora contributors (IRC, wiki, lists, etc) and resources that already exist to explain their usage. Post to wiki, send to list.
  4. List the location, for each team, where newcomers can go and pick up their first encapsulated task (clear objectives, clear deliverable, clear person-to-deliver-it-to).
  5. interviewing people to find how they got involved with Fedora, and writing up those stories
    1. Ricky: experiences with packaging/infrastructure/web
    2. Hiemanshu: web/sysadmin/sysadmin-test
    3. nb: sysadmin/sysadmin-devel/sysadmin-test/web
    4. Mel: web, packaging
    5. Mel: find at least one feedback-writer from each Fedora team

Further down, here are some things we are considering:

  1. creating "how good is this join process?" heuristics - probably with a lot of help and advice from the design team


Make sure all webpages are translated for the F12 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)

Needs a description of the goal.

If you are a Fedora project contributor you now have the chance to start your own fedora project blog. It is hoped that these blogs will allow a variety of contributors a voice brought together under a single look and feel site.

To get a blog simply follow the sign-up process.

Blogs are available to those that meet the following criteria:-

  • You need an FAS account.
  • Logged in with your new FAS account you need to complete the Contributors License Agreement: How-to complete the CLA
  • You also need to be a member of a group that is not directly related to the CLA process - take a look at the sub-projects on the wiki to see which suits you and your own expectations. Alternatively follow the process which starts at Join Fedora and see which groups you may be interested in joining.

And that's really all there is to it, so get blogging!


Team: Nick Bebout (lead), hiemanshu, onekopaka

Next steps (suggestions by mchua)

  1. From the signup screen, when you click the “create blog” button, it takes you to a screen that shows you incorrect urls for your blog (it shows instead of Fix has been included in puppet (sijis).
  2. left sidebar: “create a blog” may be better link text than ’sign up’
  3. once I create a blog there’s no obvious way to get to the dashboard. If I log out and log back in,I’m taken to the dashboard; it’s just that there’s no way to get there from logged-in state on except manually typing in the url (


Coming up with a list of suggested guidelines and tests against which new and modified websites can be evaluated - things like checking that it works on various browsers, screen resolutions, etc. See /Heuristics. Mel Chua is working on this.


For things we're thinking about, images we're kicking around, and posting thoughts that might not yet be well formed, see /Brainstorms - a lot of this discussion also happens on the mailing list.


Mailing List

The mailing list behind this effort is the fedora-websites-list mailing list. All contributors to this effort and interested third-party site maintainers should join this list.


The #fedora-websites channel on freenode is the best place to go for chat.


Details about the regular meetings for the Fedora Websites team can be found on the Meetings page.


CSS and Images

One can find all CSS files and images used in the Fedora sites on the web. And we encourage the community to use them directly from our urls in a cascading implementation.

This is especially true when working on official domains ( things on this list ):


Fedora CSS in your application

Load the main Fedora CSS file


And then load your custom css file and override elements as needed. Something like:

main or fedora_planet.css

Fedora Images in your application

Images simply need to be loaded via their 'href' attributes' url:

<a href="">

results in a een webpage:


Boilerplate responses to common mailing list inquires

Boilerplate Responses



The current agenda for the Fedora Websites initiative is tracked on the Tasks page.