All Pages

All pages have a parent page, children pages (optional), a title, and some other metadata.

Most page fields are translatable, meaning that you can provide different text for the field that is selected differently depending on the user's selected language.

It is possible to set visibility, published status, scheduled publishing date, and permissions by page under subsequent tabs.

For details regarding how this Wagtail-powered CMS section operate, please consult the Wagtail Editor's Guide, located here.

Root Page

Use

The Root Page is the top page of a tree hierarchy.  There should only be one page of this type, and all other pages should inherit from this one.

Fields

• Stream Field
  • This Stream Field allows for complete customization of the Root Page.
  • This has the following content blocks:
    • Heading
    • Paragraphic
    • Image

The following pages are possible subpages:

• Blog Index Page
• Blog Page
• Document Index Page
• Document Page
• FAQ Index Page
• SLT Page
• Incoming Index Page

Blog Index Page

Use

The Blog Index page is used as the root page for any Blog subsections of the CMS portion.  It will include a tag selector, as well as links (and previews) of any Blog Pages that are children of this index page.

Fields

• Intro
  • An introduction field presented at the top of the page

The following pages are possible subpages:

• Blog Page

Blog Page

Use

A Blog Page represents a blog page and forms a part of a blog, as determined by Blog Index pages.

Fields

• Author
  • The author of the blog page (character field to be rendered at the top of the page)
• Date
  • The date of the blog post
• Main Page
  • A flag which, if true, renders the blog post on the blog index page, and, if false, only renders the blog post when a relevant tag is selected.
• Tags
  • The relevant tags to the blog page
• Body
  • The body of the blog post
• Carousel images
  • Images to be rendered in a carousel on the blog index page, and at the top of the blog page when clicked on

This page can have no subpages.

Document Index Page

Use

The Document Index page is used as the root page for any Document subsections of the CMS portion.  It will include a tag selector, as well as links of any Document Pages that are children of this index page.

Fields

• Intro
  • An introduction field presented at the top of the page
• Tags Visible
  • A flag that allows the user to control the visibility of flags

The following pages are possible subpages:

• Document Page

 

Document Page

Use

A Document Page represents a document, and is findable from a Document Index page.

Fields

• Document
  • An uploaded file representing the document the document page represents.
• School Year
  • The school year a document is relevant to.
  • All documents are tagged with a school year and are invisible beyond (or before) the selected school year.
• Date
  • The date of upload

This page can have no subpages.

FAQ Index Page

Use

A FAQ Index page serves as the home for a set of FAQs.

Fields

• Intro
  • An introduction field presented at the top of the page

The following pages are possible subpages:

• FAQ Page

FAQ Page

Use

An FAQ page represents a set of questions and answers.

Fields

• Body
  • Body is a Stream Field with two subcomponents that are functionally infinite.
  • The two subcomponents are:
    • Question
    • Answer
• • One possible structure could be:
    • Question
    • Answer
    • Question
    • Answer
  • Another could be
    • Question
    • Answer 1
    • Answer 2
    • Question
    • Answer

This page can have no subpages.

SLT Page

Use

The SLT Page is the root page for any SLT Minutes page and is a useful page for the storing of SLT minutes (if you are in the NYCDOE system), or just general meeting minutes and general information (if outside the NYCODE, or have other purposes in the NYCDOE).

Fields

• Body
  • An infinite stream fields with subcomponents.
  • Stream field subcomponents:
    • Heading
    • Paragraph

This page also provides a list of the SLT Minutes which are subpages of this page.

The following pages are possible subpages:

• SLT Minutes Pages

SLT Minutes Page

Use

An SLT Minutes Page represents a minutes document.  This page is never viewed, but the attached document is linked on the parent SLT Page.

Fields

• Document
  • The attached minutes document.

This page can have no subpages.

Incoming Index Page

Use

The Incoming Index page is the opening page for the portal.  A link will not appear through the Info tab but rather through the main Talos header menu once a setting has been configured properly.

This page has both forms and documents as subpages, forms are per student and will have a checkbox which will be a red ex when not completed, and will transition to a green checkmark when completed.  Please see the Incoming Document Page and Incoming Form for more information on how those fields operate.

Fields

• Body
  • A rich text field meant for general information that belongs on the index page.

The following pages are possible subpages:

• Incoming Document Page
• Incoming Form

Incoming Document Page

Use

An Incoming Document Page represents a document for download (or simply viewing) that appears linked from the Incoming Index Page.

This page will never be independently viewed, but the document will be presented as a link from the Incoming Index Page.

Fields

• Document
  • The linked document.

This page can have no subpages.

Incoming Form

Use

An incoming form is a Google Docs Form-esque mechanism for creating a custom form (including file upload) that you can present to incoming students to be filled out.

There will be either a red ex or a green checkmark presented to the guardian / parent / student upon filling out the form (or not).

Fields

• Instructions
  • An instructions field that appears at the top of the form page and serves as a guide to users on how to fill out the form.
• Form Builder
  • The form builder itself.