Websites

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

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

OS Developer

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 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 and read how to fix bugs on the Fedora Project website.

Bugs

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 https://fedorahosted.org/fedora-websites/

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 .

A list of active page building requests from other projects within Fedora are located here .

Open Tasks

If you are interested in working on some of our open tasks. Take a look at our tickets

• Website tickets (newer tickets)
• Infrastructure tickets (older tickets)

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

Projects

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.

get.fedoraproject.org

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.

Mockups - Website_redesign_2009/Mockups/Get.fpo

Team: Sijis Aviles (lead)

Next steps:

1. in #desktop tab, align button so that its closer to text
2. create new images (#download tab desktop icon and screenshots)
3. verify pages work with different browsers/OSes and resolutions
4. complete "Download Finish Splash" page - Next Phase
5. the left side link "Get Fedora (Redesign)", should really be linked from the stg.fp.o/get-fedora page in the "View full list of options for getting Fedora ..." link. I put the link there for ease.
6. text needs to be updated to reflect F13
7. links need to be updated to correct locations (i've put in #! as link location fillers)

Note that we are purposely leaving out the header and footer as in the mockup. Those pieces are related more to the complete fp.o site redesign.

Decision making 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

fedoraproject.org

Open.

join.fedoraproject.org

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

Translations

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)

blogs.fedoraproject.org

Please refer to the Fedoraproject Blogs page to get started on your blog.

Team

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 https://blogs.fedoraproject.org/wp/ instead of https://blogs.fedoraproject.org/wp/name-of-your-blog). 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 https://blogs.fedoraproject.org except manually typing in the url (https://blogs.fedoraproject.org/wp/name-of-your-blog/wp-admin/)

Heuristics

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. Nobody is working on this.

Fedora Insight

Assisting with the launch of Fedora Insight, in particular the CSS-related work that needs to be done before initial launch; after launch, the back-end infrastructure maintenance will transition to the Websites team, with content and workflow remaining the responsibility of Marketing and FWN. Hiemanshu and Tatica are working on the initial release CSS and are good contact points.

Brainstorms

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.

Communicating

Mailing List

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

IRC

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

Meetings

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

Resources

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 fedoraproject.org domains ( things on this list ):

Websites/DomainsList

Fedora CSS in your application

Load the main Fedora CSS file

fedora.css

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

main

Fedora Images in your application

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

<a href="http://fedoraproject.org/static/images/banners/paulfrieldstv2.png">

results in a webpage:

Boilerplate responses to common mailing list inquires

Boilerplate Responses

Completed Projects

• Fedora Spins

Agenda

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