This is a start page for a detailed Websites team presentation. You can edit freely.
The Plan
The idea is to detailed any side of the Websites Team. That would be used to fill The wiki page for incommers, but also to construct some slideshow.
Slideshow framework
Once started, we are going to move quickly to the framework chosen. We will code on a personnal git repo but publicly available (like gitorious).
We could use http://paulrouget.com/dzslides/ which is simple fast but efficient. (or at least appears to be).
Who we are
As the name says we are a group, spread over the world, that aims to improve Fedora's image and to create the best possible interface for users and contributors on the Internet.
The key goals of the websites group 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
To realize our mission the group members have good html, css and php skills, but are also able to use the genshi framework, based on Python.
Moreover the websites team has to coordinate his work with the Fedora Infrastructure Team , Fedora Documentation Project, the Fedora Design Team and the Fedora Localization Team.
What we do
Our goal is to develop and maintain all the websites related to the fedoraproject.org domain. Therefore we don't maintain the wiki and are not involved directly into what is maintained by the Infrastructure Team. On the Infrastructure Start Page for example you can see what is maintained by the Infra Team, but you will notice that the activity range between the mentioned teams is very close and accordingly needs a good coordination.
We keep ourself in touch with the community, like other teams, with the Websites Tickets, where you can also track a bug.
The websites arch (build, dev and trans)
Our build system
Our websites are rebuilt hourly. This is done using the syncStatic script which is puppet managed. In other words, you need to be on the infra team to change it. Put a sample script here. This is where we decide against which branch we build each websites. There is also a specific syncStatic.stg script for the staging websites. Example of stg websites are stg.fedoraproject.org and spins.stg.fedoraproject.org.
For release time, please refere to our specific documentation there.
Coding
insert graph here
Architecture
There is a specific folder for each websites under which you will find the following tree:
.
|-- boot.fedoraproject.org
| |-- build
| |-- ChangeLog
| |-- data
| |-- httpd
| |-- Makefile
| |-- po
| -- static
-- TODO
<explain every folder here>
i18n
Genshi markup <explain the syntax here>
l10n
All POs are download hourly. Any error should be reported to our tracking system. <explain all l10n related stuff here>
The Hot (comming) New Websites Arch
The idea is to have a different tree using a recursive make. The syncStatic script will have few changes. Like the following (not sure about the httpd folder)
.
|-- boot.fedoraproject.org
| |-- build
| |-- data
| |-- httpd
| |-- Makefile
| |-- po
| -- static
…
|-- build
|-- Makefile
|-- static
|-- templates
-- TODO
This is directly related to ticket #90.