From Fedora Project Wiki
(Added retirement notice along with a link to the new docs page.)
 
(78 intermediate revisions by 19 users not shown)
Line 1: Line 1:
{{admon/warning|Page Retired|This page has now been retired as part of the larger community websites revamp effort. For the latest updates about Fedora Websites please refer to the docs page at https://docs.fedoraproject.org/en-US/websites}}
{{autolang|base=yes}}
{{header|websites}}
{{header|websites}}


= Welcome =
== 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.
The Fedora Websites initiative aims to improve Fedora's image and to create the best possible interface for users and contributors on the Internet.
Line 24: Line 27:
* Consolidating all key Fedora websites onto one uniform scheme
* Consolidating all key Fedora websites onto one uniform scheme
* Maintaining content that doesn't fall under any particular sub-project
* Maintaining content that doesn't fall under any particular sub-project
* Generally, making the sites as fun and exciting as the project they represent
* Generally, making the sites as fun and exciting as the projects 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 [http://fedoraproject.org/ Fedora site].
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 [https://getfedora.org/ 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 [[Infrastructure|  Fedora Infrastructure Team]] , [[DocsProject|  Fedora Documentation Project]]  and the [[Marketing|  Fedora Marketing Project]] .
Work on specific sections of the sites will be coordinated by the appropriate projects.  A great deal of coordination will be necessary with the [[Infrastructure|  Fedora Infrastructure Team]] , [[DocsProject|  Fedora Documentation Project]]  and the [[Marketing|  Fedora Marketing Project]] .


For a list of community websites, see the [[CommunityWebsites]] page.
For a list of community websites, see the [http://fedoracommunity.org Community Websites] page.


== Join the Fedora Websites Project ==
== Join the Websites Team ==


To learn how to join Fedora Websites Project, please refer to the [[Websites/Join| Join]] page.  If you just have a quick fix or suggestion, give [[Websites/ShowUs| Show Us]] a look.
Please refer to the [[Websites/Join| Join]] page on how to get the process started.
<!--== Artwork ==-->
<!--Artwork for use on Fedora websites and with other Fedora resources can be obtained from the [[Artwork|  Fedora Artwork Project]] .-->


== Communicating with Us==
{{Team contact|Websites|websites|#fedora-websites}}
* '''Mailing List''': All interested contributors should join the {{fplist|websites}} mailing list.
* '''IRC''': The {{fpchat|#fedora-websites}} channel is the best place to go for chat, bugs, issues, patches and general discussions.
* '''Meetings''': Our [[Websites/Meetings| meetings]] page has details of old meetings (actually no meetings are scheduled).
<div style="float: right;">[[Image:WikiElements_meetingL.png]]</div>
{{Anchor|bugs}}
{{Anchor|bugs}}
== Bugs ==
== Bugs ==


{{admon/note | 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]].}}
{{admon/note | 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/
'''Found a bug?'''
 
Alternatively, email '''webmaster AT fedoraproject DOT org''' which is handled by [https://admin.fedoraproject.org/mailman/listinfo/websites websites list] .


Bugs that are related to the [[DocsProject|  Fedora Documentation Project]]  can be reported using [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Documentation&op_sys=Linux&target_milestone=---&bug_status=NEW&version=devel&component=fedora-websites&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=web-members%40fedoraproject.org&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=Description%20of%20problem%3A%0D%0A%0D%0A%0D%0AVersion-Release%20number%20of%20selected%20component%20%28if%20applicable%29%3A%0D%0A%0D%0A%0D%0AHow%20reproducible%3A%0D%0A%0D%0A%0D%0ASteps%20to%20Reproduce%3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%20%20%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A&commentprivacy=0&status_whiteboard=&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug this template] .
Create a [https://pagure.io/fedora-websites/new_issue new ticket] and we'll be notified.


A list of active page building requests from other projects within Fedora are located [[Websites/PageRequests| here]] .
Alternatively, email '''webmaster AT fedoraproject DOT org''' which is sent to the {{fplist|websites}} list.


{{Anchor|communicate}}


== Projects ==
'''Fixing a bug or sending patches?'''


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 [[/Meetings/2009-06-19|2009-06-19 meeting]], But remember, ''you'' decide priority by ''voting with your feet'' and ''doing things'' to move these projects forward.
Here is [[how to fix bugs on the Fedora Project website]].  


=== get.fedoraproject.org ===
Patches can be sent to our {{fplist|websites}} list.


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.
'''Tracking a bug?'''


Mockups - [[Website_redesign_2009/Mockups/Get.fpo]]
Bug tracking for the Fedora websites is handled through our [https://pagure.io/fedora-websites/issues Fedora Websites Trac instance].


Team: [[User:Sijis|Sijis Aviles]] (lead)
Bugs that are related to the [[DocsProject| Fedora Documentation Project]] or https://docs.fedoraproject.org can be reported using [https://bugzilla.redhat.com/bugzilla/enter_bug.cgi?product=Fedora%20Documentation&op_sys=Linux&target_milestone=---&bug_status=NEW&version=devel&component=fedora-websites&rep_platform=All&priority=normal&bug_severity=normal&assigned_to=web-members%40fedoraproject.org&cc=&bug_file_loc=http%3A%2F%2F&short_desc=&comment=Description%20of%20problem%3A%0D%0A%0D%0A%0D%0AVersion-Release%20number%20of%20selected%20component%20%28if%20applicable%29%3A%0D%0A%0D%0A%0D%0AHow%20reproducible%3A%0D%0A%0D%0A%0D%0ASteps%20to%20Reproduce%3A%0D%0A1.%0D%0A2.%0D%0A3.%0D%0A%20%20%0D%0AActual%20results%3A%0D%0A%0D%0A%0D%0AExpected%20results%3A%0D%0A%0D%0A%0D%0AAdditional%20info%3A&commentprivacy=0&status_whiteboard=&ext_bz_id=0&ext_bz_bug_id=&data=&description=&contenttypemethod=list&contenttypeselection=text%2Fplain&contenttypeentry=&maketemplate=Remember%20values%20as%20bookmarkable%20template&form_name=enter_bug this template] .


Next steps:
{{Anchor|Open Tasks}}
# in #desktop tab, align button so that its closer to text
# create new images (#download tab desktop icon and screenshots)
# verify pages work with different browsers/OSes and resolutions
# complete "Download Finish Splash" page
# 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.
# text needs to be updated to reflect F13
# 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.
== Open Tasks ==
Want to see a list of our open tasks?
* [https://pagure.io/fedora-websites/issues Website tickets]
* [https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&owner=~web&order=priority Infrastructure tickets]


=== Decisionmaking process ===
If you find something you'd like to take on, add a comment to the ticket and add yourself as owner.


Articulate and document the consensus-based decision making process of the websites team.
These tasks can vary from html/css changes to python scripting.


Team: [[User:Ricky|Ricky Zhou]] (lead)
{{Anchor|spins}}


Next steps:
== Spins ==
#  Ricky to send a draft here's-how-to-present-your-patch-to-the-list checklist to the mailing list


=== fedoraproject.org ===
If you are the owner of a new and approved 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 [https://spins.fedoraproject.org Desktop Spin] or a [https://labs.fedoraproject.org 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!


Open.
{{Anchor|communicate}}


=== docs.fedoraproject.org ===
== Projects ==
 
Needs a description!


Team: [[User:Ricky|Ricky Zhou]] (lead)
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.


Action items:
=== Wiki Theme Update ===
# Ricky will bring his critiques to the docs team and report back via email to the list.


=== join.fedoraproject.org ===
Update this [http://fedoraproject.org/wiki Wiki's] theme.


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: [[User:Sijis|Sijis Aviles]], [[User:Ilianaw|Iliana Weller]] (leads)


Team: [[User:Mchua|Mel Chua]] (lead)
Status: Not started


Currently stalled.
=== All Fedora Websites Update ===


Next steps (for the week of June 28, 2009):
Update all Fedora websites similar to getfedora.org's bootstrap design. All websites should be responsive and easy to navigate.


# Create a project (wiki) page for this.
Team: [[User:Robyduck|Robert Mayr]] (lead)
# 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.
# 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.
# 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).
# interviewing people to find how they got involved with Fedora, and writing up those stories
## Ricky: experiences with packaging/infrastructure/web
## Hiemanshu: web/sysadmin/sysadmin-test
## nb: sysadmin/sysadmin-devel/sysadmin-test/web
## Mel: web, packaging
## Mel: find at least one feedback-writer from each Fedora team


Further down, here are some things we are considering:
Status: In progress


# creating "how good is this join process?" heuristics - probably with a lot of help and advice from the design team
Deadline: Summer 2016


=== Translations ===
=== Translations ===


Make sure all webpages are translated for the F12 release.
Make sure all websites, primarily fedoraproject.org subdomains and getfedora.org are translated for Fedora releases. All source files now are on [https://translate.fedoraproject.org/projects/fedora-websites/ Fedora Weblate]. This project needs to work close to the L10N teams.


Team: '''Nobody yet! Please help!'''
Team: [[User:Robyduck|Robert Mayr]], [[User:Shaiton|Kévin Raymond]] (leads)


(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.)
Status: Migration completed, make sure all websites have i18n.


=== User gallery ===
=== Decision making process ===


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.
Articulate and document the consensus-based decision making process of the websites team.
 
Team: [[User:hiemanshu|Hiemanshu Sharma]] (lead)
 
=== blogs.fedoraproject.org ===
 
''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 [http://blogs.fedoraproject.org/wp/wp-signup.php sign-up] process.
 
Blogs are available to those that meet the following criteria:-
 
:* You need an [[Account_System|FAS]] account.
:* Logged in with your new FAS account you need to complete the Contributors License Agreement: [[/Infrastructure/AccountSystem/CompleteCLA|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 [http://fedoraproject.org/join-fedora Join Fedora] and see which groups you may be interested in joining.
 
And that's really all there is to it, so get blogging!
<br/>
<br/>
==== Team ====
Team: [[User:nb|Nick Bebout]] (lead), hiemanshu, onekopaka
 
Next steps (suggestions by mchua)
# <strike>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).</strike> Fix has been included in puppet (sijis).
# left sidebar: “create a blog” may be better link text than ’sign up’
# 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 ===
Team: [[User:Sijis|Sijis Aviles]], [[User:Robyduck|Robert Mayr]] (leads)


Assisting with the launch of [[Fedora Insight]], in particular the [[Fedora Insight#Design|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]]. [[User:Hiemanshu|Hiemanshu]] and [[User:Tatica|Tatica]] are working on the initial release CSS and are good contact points.
=== Hubs ===


== Brainstorms ==
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!


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.
Team: [[User:Robyduck|Robert Mayr]], [[User:Duffy|Máirín Duffy]] (leads)


== Communicating ==
Status: Prototype created, QA in progress


=== Mailing List ===
Deadline: F24


The mailing list behind this effort is the [https://admin.fedoraproject.org/mailman/listinfo/websites websites] mailing list.  All contributors to this effort and interested third-party site maintainers should join this list.
=== Fedora Developer Portal ===
developer.fedoraproject.org - a new go-to place for app developers running Fedora


=== IRC ===
Wiki page: [[Websites/Developer|Websites/Developer]]


The #fedora-websites channel on [http://freenode.net/ freenode] is the best place to go for chat.
Team: [[User:Phracek|Petr Hracek]], [[User:Jstribny|Josef Stribny]], [[User:Asamalik|Adam Samalik]] (leader)


=== Meetings ===
Status: '''Completed''', [https://developer.fedoraproject.org/ now live]


Details about the regular meetings for the Fedora Websites team can be found on the [[/Meetings|  Meetings]]  page.
Deadline: End of the summer 2015


== Resources ==
== Resources ==


===CSS and Images===
===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.
All CSS files and images used in Fedora sites can be found in our [https://pagure.io/fedora-websites/tree/master fedora-websites.git repository]. The community may use the css directly from our urls in a cascading implementation.


This is especially true when working on official fedoraproject.org domains ( things on this list ):
We encourage using the stylesheets in a cascading method when working on official Fedora Project domains (sites on this list):
[[Websites/DomainsList]]


[[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=====
=====Fedora CSS in your application=====


Load the main Fedora CSS file
Load the Fedora CSS file
 
[http://getfedora.org/static/css/bootstrap.css bootstrap.css]
[http://fedoraproject.org/static/css/fedora.css fedora.css]
Load a Specific app CSS file
 
[http://getfedora.org/static/css/app.css app.css]
And then load your custom css file and override elements as needed. Something like:
 
[http://fedoraproject.org/w/skins/fedora/main.css main]
or
[http://fedoraproject.org/css/fedora_planet.css fedora_planet.css]
 
=====Fedora Images in your application=====
 
Images simply need to be loaded via their 'href' attributes' url:
 
<code><nowiki><a href="http://fedoraproject.org/static/images/banners/paulfrieldstv2.png"></nowiki></code>
 
results in a een webpage:


http://fedoraproject.org/static/images/banners/paulfrieldstv2.png
And then load your custom css file and override elements as needed.


===Boilerplate responses to common mailing list inquires===
===Boilerplate responses to common mailing list inquires===
Line 226: Line 175:
== Completed Projects ==
== Completed Projects ==


* [[Websites/Spins| Fedora Spins]]
* [https://getfedora.org Get Fedora]
 
* [https://start.fedoraproject.org Start Fedora]
== Agenda ==
* [https://spins.fedoraproject.org Fedora Spins]
The current agenda for the Fedora Websites initiative is tracked on the [[Websites/Tasks|  Tasks]]  page.
* [https://labs.fedoraproject.org Fedora Labs]
 
<!--Also, see [[Websites/PageRequests|  Current Page Requests]]  and ##[https://fedorahosted.org/fedora-infrastructure/query?status=new&status=assigned&status=reopened&group=milestone&component=Webmaster&order=priority ##Fedora Websites tickets] .
-->




[[Category:Websites]]
[[Category:Websites]]
[[Category:Fedora sub-projects]]

Latest revision as of 14:09, 21 April 2021

Page Retired
This page has now been retired as part of the larger community websites revamp effort. For the latest updates about Fedora Websites please refer to the docs page at https://docs.fedoraproject.org/en-US/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 projects 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: websites
Visit this link to sign up for the email list for the Websites team.		 Chat: #fedora-websites[?]
This is where real-time chat with Websites team members happens.
  • Mailing List: All interested contributors should join the websites mailing list.
  • IRC: The #fedora-websites[?] channel is the best place to go for chat, bugs, issues, patches and general discussions.
  • Meetings: Our meetings page has details of old meetings (actually no meetings are scheduled).

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.

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 https://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 to the ticket and add yourself as owner.

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

Spins

If you are the owner of a new and approved 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!

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.

Team: Sijis Aviles, Iliana Weller (leads)

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

Translations

Make sure all websites, primarily fedoraproject.org subdomains and getfedora.org are translated for Fedora releases. All source files now are on Fedora Weblate. This project needs to work close to the L10N teams.

Team: Robert Mayr, Kévin Raymond (leads)

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.

Team: Sijis Aviles, Robert Mayr (leads)

Hubs

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!

Team: Robert Mayr, Máirín Duffy (leads)

Status: Prototype created, QA in progress

Deadline: F24

Fedora Developer Portal

developer.fedoraproject.org - a new go-to place for app developers running Fedora

Wiki page: Websites/Developer

Team: Petr Hracek, Josef Stribny, Adam Samalik (leader)

Status: Completed, now live

Deadline: End of the summer 2015

Resources

CSS and Images

All CSS files and images used in Fedora sites can be found in our fedora-websites.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

Load the Fedora CSS file bootstrap.css Load a Specific app CSS file app.css

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

Boilerplate responses to common mailing list inquires

Boilerplate Responses

Completed Projects

Retrieved from "https://fedoraproject.org/w/index.php?title=Websites&oldid=612631"