Mozilla.org/How to Work with Site: Difference between revisions
| Line 51: | Line 51: | ||
''Note: You '''do not''' need to deal with CVS if you don't want to. This information is provided for anyone who does want to work directly with our repository.'' | ''Note: You '''do not''' need to deal with CVS if you don't want to. This information is provided for anyone who does want to work directly with our repository.'' | ||
If you'd like to edit the site directly, you will need to | If you'd like to edit the site directly, you will need to get commit access and either edit pages using a version control tool or our online editor. Documentation for each of those steps is below: | ||
* [http://www.mozilla.org/hacking/committer/ Becoming A Mozilla Committer] | * [http://www.mozilla.org/hacking/committer/ Becoming A Mozilla Committer] | ||
* [http://www.mozilla.org/contribute/writing/cvs | * [http://www.mozilla.org/contribute/writing/cvs Documentation for editing current version of site] (covers CVS and Doctor) | ||
* [[Mozilla.org/Editing Site with SVN|Documentation for editing the staging site]] (covers SVN and Bespin) | |||
Revision as of 18:51, 2 July 2009
Docs for people getting involved with site.
Asking Questions
The best way to learn about how to work with the www.mozilla.org site is to ask questions. Community members are happy to help, but it can be difficult to know who to talk to. Here are a few good places to go with questions:
Email: dev-mozilla-org
Chat: #siteplanning on irc.mozilla.org
Phone: Monthly planning meetings
What To Work On
We use Bugzilla to track bugs as well as enhancements to the site, so we recommend that you look through open bugs to determine what you'd like to work on. Of course you are welcome to suggest new ideas as well.
You can look through bugs without a Bugzilla account, but you will need one to update an existing bug or open a new one. Everyone is welcome to look through open bugs, comment in a bug, submit a patch or open a new one.
Viewing The Source
The site uses a templating system to add the header, side navigation and footer to all of the pages. If you view the source of a page through your browser you are seeing the results of merging a page with a template. To see what the HTML files look like before they are merged, you can look in the footer of any page (except the home page) and click on the Edit this Page link. For instance:
Our repository is open, so feel free to check out different pages to see how things are put together.
Staging Site
The current version of the site does not have a staging server—instead you are able to run a version of the site on your computer to test most changes (details of how to do that are below). We are setting up a staging site at http://www-stage.mozilla.org but it is not in use yet.
Making Site Changes
There are two ways to update the site—have someone with access make the change or make the change yourself.
Submitting Changes
The easiest way to make a change is to work with someone who already has access. You can send them the change in a variety of formats. Attaching a patch to a bug is the most common way to do that, but it is also possible to simply email a change to someone. How changes are submitted will vary on your technical experience and on who you are working with.
Checking In Changes
Note: You do not need to deal with CVS if you don't want to. This information is provided for anyone who does want to work directly with our repository.
If you'd like to edit the site directly, you will need to get commit access and either edit pages using a version control tool or our online editor. Documentation for each of those steps is below:
- Documentation for editing current version of site (covers CVS and Doctor)
- Documentation for editing the staging site (covers SVN and Bespin)