How to use the website

From LU
Revision as of 03:46, 26 September 2015 by Jmoldow (Talk | contribs)

Jump to: navigation, search

Some newer documentation is available at <>.

The latest release notes are at <>.

To contact the web team with questions, problems, feature requests, etc. email <>.

Submit feature requests and non-urgent bug reports to <>.

The Website: A Quick Overview

What we call the "website" actually consists of two separate (but interacting) parts:

  1. The graphical front-end. This is controlled with normal HTML, CSS, etc. The tools that any web designer knows, and so if you find someone who knows any web design, they'll be able to do this.
  2. The database back-end. This is the part that stores user information, classes, and much more.

You have nearly complete control over the front-end, while back-end code is maintained by our Web team. The graphics and content of your site can be edited in several ways:

  • The easiest is editing "Quasi-static data," or "QSD," which just refers to text on the website. If you're logged in as an administrator, just click the Edit link or in the box with a dotted outline, and you'll be editing the content on the page. (More info.)
  • The media files for the website (images, CSS stylesheets) can be added or modified by using the file browser at https://[yoursite]
  • The HTML templates that are used to generate pages can be overridden at https://[yoursite] You can set the appearance of every page on your site by editing a single template override (main.html).

Feature Requests

If you want to request a new feature or bug fix for the website, you have three choices:

  1. For anything that warrants discussion, e-mail your mentors or Web support e-mail list with a description of the issue.
  2. If you have a good idea of what you need, fill out our Google form here (responses are visible here)
  3. If you have detailed technical knowledge of the issue, file a ticket directly on Github:
    • Go to
    • Click "New Issue"
    • Provide a short descriptive title of the issue, and a detailed description (e.g. exactly how to reproduce a problem, or exactly what you want a new feature to look like). Click "Submit New Issue."
    • Associate any relevant labels with the ticket (e.g. Error, UserInterface, Enhancement, Performance).

Starting Out

Managing a Program


How to...

In general, "test everything you want to use." In particular, important tests are:

Website Output

How to...

Website Content

How to...

Managing Users

How to...


How to...

Continue Reading on How to design a chapter website