Mozilla.org/How to Work with Site: Difference between revisions
No edit summary |
|
(No difference)
|
Revision as of 16:06, 2 September 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
Bugzilla
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 at the files in our Subversion repository at:
Our repository is open, so feel free to look around at different files to see how things are put together.
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 Subversion 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 the site (covers Subversion and Bespin)
Style Guides and References
Once you're able to make changes to the site, please take a look at the following pages that offer suggestions about writing and coding. Since the site is edited by a range of people across the community, following some guidelines will help maintain a consistent experience for users.
- mozilla.org Documentation Style Guide
- mozilla.org Markup Reference
- Design style guide (coming soon)