Welcome
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
These are only suggestions for contributing roles. Only your imagination sets the limits.
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, bugs, issues, patches and general discussions.
- Meetings: Our meetings page has details on when they are held.
Bugs
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.
Found a bug?
Create a new ticket and we'll be notified.
Alternatively, email webmaster AT fedoraproject DOT org which is sent to the websites list.
Fixing a bug or sending patches?
Here is how to fix bugs on the Fedora Project website.
Patches can be sent to our websites list.
Tracking a bug?
Bug tracking for the Fedora websites is handled through our Fedora Websites Trac instance.
Bugs that are related to the Fedora Documentation Project or http://docs.fedoraproject.org can be reported using this template .
Open Tasks
Want to see a list of our open tasks?
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.
Projects
These are projects with specific goals being worked on. They're in rough order of the priority, but remember, you decide priority by voting with your feet and doing things to move these projects forward.
Wiki Theme Update
Update this Wiki's theme to match fedoraproject.org's 960.gs design.
Team: Sijis Aviles, Ian Weller
Status: Not started
Deadline: Spring 2012
All Fedora Websites Theme Update
Update all Fedora websites simialar to fedoraproject.org's 960.gs design. The list to tackle are the ones in the website git repository.
Team: Sijis Aviles (lead)
Status: Not started
Deadline: Summer 2012
Translations
Make sure all websites, primarily fedoraproject.org is translated for Fedora releases.
Team: Nobody yet! Please help!
Deadline: Ongoing
(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.)
Decision making process
Articulate and document the consensus-based decision making process of the websites team.
Team: Sijis Aviles (lead)
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)
Status: Stalled
Deadline: N/A
Resources
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 fedoraproject.org/wiki).
Boilerplate responses to common mailing list inquires
Completed Projects
- Fedora Spins
- fedoraproject.org Redesign
- join.fedoraproject.org (as part of fedoraproject.org redesign)