Editing GO Site (Retired)

From GO Wiki
Revision as of 16:52, 22 October 2013 by Sjcarbon (talk | contribs)

Jump to: navigation, search

Warning: Please make sure that you have read the most recent version of this document completely before contacting Seth or Moni.

General notes

  • The URL for the text versions of the pages scraped from the old website is at: http://nakama.berkeleybop.org/go
  • The spreadsheet listing pages and assignments for content migration is located at http://goo.gl/Bcr1VC
  • The user login page is at: http://beta.geneontology.org/user/login ; this may change in the future--if this link does not work, check back here
  • All internal links should be relative. Examples:
    • To link to the book containing the GO evidence code guide, you may type the following:
      Refer to the <a href="/book/guide-go-evidence-codes">GO evidence code guide</a> for the list of valid evidence codes.
    • On the other hand, to link to a basic page such as the 'Tools' tab, type:
      More information is available on the <a href="/page/tools">Tools Page</a>.
  • Editors cannot currently change menus, if you need a menu change please contact a Manager (currently Chris or Seth)
  • To view a book as a single page, click on the "Printer-friendly version" link

How to add content

After login there will be a menu visible in the left column. It contains links to add new content, currently: article, page, book, highlighted term, and external project. There is also a link to list all available current content at find content.

Adding new content

  1. Click to add a new item
  2. Enter a Title for the page. It will be displayed at the top. Please 'Capitalize Each Word' for the tile sentence.
  3. Carefully choose the intended audience from the User Story menu.
  4. Choose the appropriate Tags to categorize this content. Is this page a guide document? Or is it describing the structure of the ontology? Both Tags and User Story may be modified later, if necessary.
  5. From the content window, choose to either work using 'Source' code, using the button on the upper left corner of the box, or choose to 'Switch to plain text editor' from the options underneath the box. The difference will be obvious, and you will choose the one that is more familiar/comfortable to you. The editing box can be resized from the bottom right corner.
  6. Begin typing text using HTML tags as allowed in the list of 'Almost HTML', located under the editing box. You may use your editor of choice to prepare the HMTL elsewhere and paste it on the box. Alternatively, directly copy and paste the text from the raw HTML found in the corresponding file from the list of old site documents. If you choose to follow the latter method, please be aware that you need to further edit the text to remove unnecessary titles, and in many cases to introduce breaks. Please compare with the 'old' site for accuracy of content and sequencing.
  7. Preview your work using the button at the bottom of the page.
  8. Save your work. Remember to always Save Your Work.

Content types

All content on a Drupal website is stored and treated as "nodes". A node is any posting, such as a page, book, or an article. Treating all content as nodes allows the flexibility of creating new types of content, and allows Seth to painlessly apply new features or changes to all content.


The article module allows for nodes (pages) of any type to be organized and displayed in a centralized location. This allows us to organize organize pages of several different types in one place, and allow users to navigate the pages by searching and selecting different categories.


A book is a set of pages tied together in a hierarchical sequence, perhaps with chapters, sections, subsections, and so on. We can use books for manuals, site resource guides, Frequently Asked Questions (FAQs), etc.

How to edit content

This is rather easier than content generation.

  1. Log in
  2. Navigate to the page that you want to edit, either directly or through Find content.
  3.  ???
  4. Profit.

Versions and reversions


Style guide


Logos in projects will be cropped over 220x165. If you're having trouble getting getting your logo into an appropriate format, contact Seth or Moni for some help.

There's something I want! / It's not working!

We're still testing the new site and its workflows (thank you!), so not all of the pieces will fit perfectly yet. If there is something that you'd like (a new tag, a larger icon), please contact Seth or Moni to see if they can help you out.

If something seems to be broken, it might not just be you. Please contact Seth or Moni before frustration sets in so we can try and work out what it going on (or manage your expectations).

Also, keep in mind that these instructions and the current state of the site might fall out of sync. If that's the case, contact Seth or Moni to see if they can fox or update things.