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
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 Get 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 Community Websites page.
Join the Websites Team
Please refer to the Join page on how to get the process started.
Communicating with Us
|How to contact the Websites team|
| Mailing list:
Visit this link to sign up for the email list for the Websites team.
| Chat: |
This is where real-time chat with Websites team members happens.
- Mailing List: All interested contributors should join the mailing list.
- IRC: The channel 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.
Found a bug?
Create a new ticket and we'll be notified.
Alternatively, email webmaster AT fedoraproject DOT org which is sent to thelist.
Fixing a bug or sending patches?
Patches can be sent to ourlist.
Tracking a bug?
Bug tracking for the Fedora websites is handled through our Fedora Websites Trac instance.
Want to see a list of our open tasks?
If you find something you'd like to take on, add a comment to the ticket and add yourself as owner.
These tasks can vary from html/css changes to python scripting.
If you are the owner of a new Spin that needs to be included on the websites there are just a few websites specific tasks (you will have to make others) to accomplish:
- Open a ticket in the websites track and refer to your wiki page, provide support informations, mailing list and IRC channel.
- Provide a features list, they are different if your spin is a Desktop Spin or a Functional Spin.
- Open a ticket in the design trac to request design.
- Provide an actual screenshot with a full HD resolution (1920x1080): only for Desktop Spins!
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.
Status: Not started
All Fedora Websites Update
Update all Fedora websites similar to getfedora.org's bootstrap design. All websites should be responsive and easy to navigate.
Team: Robert Mayr (lead)
Status: In progress
Deadline: Summer 2016
Make sure all websites, primarily fedoraproject.org subdomains and getfedora.org are translated for Fedora releases. All source files now are on fedora.zanata.org. This project needs to work close to the L10n teams.
Status: Migration completed, make sure all websites have I18n.
Decision making process
Articulate and document the consensus-based decision making process of the websites team.
Create a new web-interface for contributors and for gathering new contributors, where people can have an easy overview of what's going on in the single team. Will need a framework and working close together with Design and Infrastructure is a must!
Status: Brainstorming started
Deadline: F23 or F24
Fedora Developer Portal
developer.fedoraproject.org - a new go-to place for app developers running Fedora
Wiki page: Websites/Developer
Status: Project definition
Deadline: End of the summer 2015
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
All websites based on bootstrap use the same basic CSS file. Any specific stylesheet needs to be written in the website's app.css file. Don't modify the main bootstrap CSS.
Fedora CSS in your application
And then load your custom css file and override elements as needed.