Website Hierarchies

  • School site administrators have additional editing and viewing privileges beyond teachers and most users.

    Site administrators may adjust the layout and design of their specific site's homepage or landing page, as well as add Users, create Group, and delineate various viewing privileges.

    Below you will see an image map that explains the mapping of a school site's homepage. Please use this guide as your reference for when editing the homepages as to what corresponds to what part of the page.

    School Site Region Map

    Here is the site hierarchy:

    • SITE: i.e. spps.org. That is our overarching site. We have just one.
    • SUBSITE: Schools are subsites, i.e. spps.org/adams. These are standalone sites, but fall under the overall spps.org domain. Departments used to be subsites, but under the new hierarchy they will not be. Only schools will be subsites, along with two departments: IT and Community Education. (More on that below).

    Site Hierarchy

     

    The above metaphor is used to describe the site hierarchy.

    • CHANNEL: Each tab across the top nav bar of the spps.org home page is a channel. Most departments will be a channel. It is the giant bucket to divide the site's main areas. Example: Human Resources is a "channel" under SPPS.org. SUBSITES can have their own channels; example: spps.org/adams can have its own "About" channel, "Classrooms" channel, etc.
    • SECTION: Sections fall under channels to further divide the channel. Using HR as an example again: the HR site can have multiple sections, such as Payroll, Benefits, Professional Development, etc. A school website can have multiple sections within "About" such as Principal, Demographics, etc.
    • PAGES: Each section can have as many pages as needed. Example: Payroll can have pages about how to pick up w2s, how to add insurance, etc. At Adams, the principal can have multiple pages such as a biography page, newsletter page, etc.
    • APPS AND LAYOUTS: These are the specific preformatted containers you can place on each page. We create these specific to each page. This function also controls the layout of a page to include a left navigation, or a right sidebar, etc.

    A couple of quick overall points:

    • We may control viewing rights and privileges down to a specific user.
    • We can only control editing rights only to a SECTION LEVEL. In other words: If you give editing rights to a section, the editor can edit ALL PAGES within that section. If you give editing rights to a CHANNEL, you can control editing rights to the SECTION. Example: Under the Teacher CHANNEL, each teacher has their own section, so teachers can have editing rights to their own section and pages, but not have editing rights to other teachers' pages.

    Now understanding the site hierarchy, here is how SPPS sites are broken down:

    • SPPS.org is the district's overall umbrella site. This site is operated by the team at the Office of Communications. It operates on its own custom-designed District Template, but has the same elemental design and function as all sites in the district.
    • SPPS has 50+ schools. Each of these operates a SUBSITE under SPPS.org, on a custom-designed School Template. It is the same layout, design and function, but has the ability to have customized images, colors, banners, etc. All schools retain a "subdomain," i.e. "spps.org/wellstone," "spps.org/adams," etc.
    • SPPS has 70+ departments. Each of these operates a CHANNEL. In Blackboard, departments now function under the SPPS.ORG domain. Example: Facilities is no longer facilities.spps.org. It is now SPPS.org/facilities. If you type in facilities.spps.org, it will redirect to spps.org/facilities.
      • There are four department exceptions that will operate subsites:
        • Community Education
        • Technology Services
        • Staff
        • Athletics
    • Within each channel, we have SECTIONS that are dedicated to the areas of each department. This was done deliberately to isolate editor permissions within departments and to avoid overlap. This way, for example in HR: Payroll won't have editing rights to the Benefits section of the site, etc.
      • REMINDER: The ability to limit editing rights ends at the SECTION level. You cannot limit the number of editors to a page. You can only limit editing rights to a section.
    • Within each SECTION, you can lay out as many PAGES as you want. For example, again: Payroll can have pages about how to pick up w2s, how to add insurance, etc.; Benefits can have pages on how to contact HealthPartners, etc. At spps.org/adams, the principal can have multiple pages such as a biography page, newsletter page, etc.