Think of the Wiki as the Wikipedia for Force.com developers. It's a website for anyone to use to get access to Force.com development information, tools, and other resources. But because it is a wiki, it is also a powerful tool for sharing your own expertise with other developers in the Developer Force community. Every Developer Force member has the option to participate -- you can contribute new resources of your own, or add to almost any of the existing resources already posted.
Participation is open to anyone who is a Developer Force member. If you have a Developer Edition account that you've enabled for the Force.com Discussion Boards -- and doing that is easy, and free -- you are good to go. The rest of this help section will give you the details you need to contribute, edit, and more.
To add or edit wiki content, you'll want to have basic understanding of wiki syntax. Click the "edit" button on pages on this site, and take a look at the underlying syntax and markup. You can accomplish a lot just by mimicking what's already been done, and this has the added benefit of helping keep the site consistent and usable. Probably 90% of what you need to know can be learned by looking around this site, and copying syntax and tags from existing pages.
To go a little deeper, or if you need to look something up, Wikipedia has a nice set of documentation on how to edit wiki pages. If you want to do some wiki experimentation, we've set up a Wiki Sandbox page where you can create test pages, try out formatting, and so forth, without fear of messing up anything important.
Still unsure? Follow these steps to get your confidence up:
The primary organization of the site is topical. There are five top-level categories -- Application Framework, Integration, Apex, Visualforce, and Database Services -- and numerous topical subcategories to each of those. There are also three special categories, Tools, Packaging, and Business Resources.
Each top-level category has its own page (informally, we call these "pillar pages"), and subcategories appear as sections on that page. Links to content resources are are listed within subcategory sections. See the Integration page for a good example.
If you create a new page, be sure to add links on all of the appropriate topical pages, so others may be more likely to find it. A piece of Java sample code that addresses an integration issue, for example, should probably be categorized and linked from both Java and Integration sections.
We encourage your contributions -- the point of the Wiki is to bring together the collective expertise of the Force.com Developer community. If you have something to contribute -- say a piece of sample code or a tech note that you would like to share with the community -- you can easily create a new page. New pages are created simply by editing an existing page to add a link. Say you have a new piece of Java sample code you want to share. First you'd need to log in to the wiki. Next you'd go to the Java section of the API page, since that's the most likely place to categorize the new sample code. You'd click on the "edit" button above that section, and then you'd see the wiki "source" for the section within an editable field. Add a link to your new page using wiki syntax -- for a new page, it's as simple as enclosing the name of the new page in double brackets, then saving that change. You'll see the link to your new page in red. Click on this, and -- ta da! -- you're on your new page. Copy in your sample code, add a little wiki markup for styling headers and such, and save. That's it. (The Wiki Sandbox page is a good place to experiment without fear of messing up a page other folks depend upon.)
For more detailed information, check out Wikipedia's "how to edit wiki pages" reference; we're using the same wiki engine (MediaWiki) that they are. And one nomenclature tip: Since the way you add a new page to a wiki site is by editing a page that already exists, most wiki information about contributions is confusingly categorized under "editing".comment tags to hide links to your work until it is ready for prime time, then simply remove the comment tags to expose the link when the page is ready.
Any given piece of content should be listed within at least one section of one pillar page (which is the same as saying it should live in at least on category/subcategory pair). So, for example, the Tech Note Creating an Outbound Messaging Notification Service with Eclipse 3.2 is placed on the API page within the Java section. But a piece of content can be listed in multiple places if this makes sense -- and it should be as well, since different users may seek information via different paths. An example is the document Creating Applications with the Force.com Platform.
When placing and categorizing your content, try to make best use of the patterns and conventions already in use on the wiki. That will help the site maintain a consistent navigational scheme.
This section describes how to use templates when adding new content pages: tech notes, samples, books, documenation, or multimedia content. Simply include one of the following at the top of your content page and the appropriate header will be displayed:
Notes on content types and template usage:
The __NOTOC__ tag you see at the top of most pages is used to turn off the default table of contents, which would otherwise appear at the top of the page (as it does at the top of the help page).
If you are logged in, you can click on the "edit" button on any page or section of a page, and you'll be able make changes to the content there. Adding to and improving exisiting content is highly encouraged, but be respectful of the work already done by others, and be thoughtful about any changes that remove, obscure, or diminish already existing content that the community may value.
Embedding video into a wiki page is easy. Depending on your video format, you surround your video id with the proper tags. Below is a list of video formats and tags that this wiki supports:
<swf width="740" height="640">http://tulipit.com</swf>