Portals are a framework that is built into Slate that allows for custom development of mini-websites that can access Slate data and use Slate authentication. Portals represent fully-customized software development that requires specialized resources. Slate provides several out-of-the-box portals that can be customized by our partners.
Prior to beginning any portal project, it is important to identify the available resources on staff to maintain each portal. While Technolutions can offer guidance and instruction on Portals, the custom nature of a portal requires that each partner take full ownership over the portal.
Portals can be added to Slate via Briefcase using the Briefcase IDs listed below.
The applicant status portal replaces the /apply/status.xslt file institutions may have previously used to customize the applicant's experience post-submission.
The application status portal allows for many customizations, including custom checklist sections, filtering on static content, social media, and other merge fields.
The Standard Application Status Portal replicates the /apply/status.xslt file by using drag-and-drop widgets. For institutions seeking to mirror the existing /apply/status.xslt functionality, we recommend importing this portal to then build upon.
If you have made any edits to the /apply/status.xslt file, these edits will not be reflected in the portal. We recommend reviewing the Migrating Portals from XSLT to Views documentation for advice about translating teasers and other application status page edits to the Application Status Portal.
The Customized Application Status Portal includes the Checklist by Section widget, more merge fields, filters on widgets, staff assigned information, and test scores table. This portal will require you to review the filter criteria, checklist sections, and other information prior to going live with the portal.
While many partners continue to evolve the application status portal beyond the point of an admission decision, some institutions may wish to give enrolling students their own portal with a different look and feel. The enrolling student portal is intended only for enrolling students where they can see enrollment checklist items and find additional information about the institution and enrollment process. In addition, the portal includes optional features, such as the ability for records to update their profile and search using a directory of fellow enrolling students.
Using a custom dataset to store alumni volunteer information, this portal will display a curated list of applicants to the volunteer, typically for the purpose of scheduling an interview. Alumni volunteers are able to select which applicants they wish to interview and provide feedback through a custom form.
Similar to the alumni interviewing portal, this portal stores alumni volunteer information in a custom dataset. Certain alumni volunteers are designated as captains, which enables them to see not only a curated list of applicants but also of matching alumni volunteers. The captains are empowered to assign applicants to volunteers. Volunteers can see their assignments and, upon completion of the interview, provide feedback through a custom form.
This portal is configured to leverage the Slate standard Sport table, and coaches are set up as users with specific roles in Slate. Coaches are added to Slate as administrative users and given a custom role which matches the names of sports. Person records with the corresponding sport on their profiles are then shown to the appropriate coaches. The specific details of the information shown to the coach can be customized and, using a custom form, additional information can be added to the records by coaches.
A portal can be a helpful tool to display information about a Giving Campaign or Giving Day. This portal allows advancement offices to display information about a specific campaign, a list of recent donors, metrics regarding the goal of the giving day or campaign, and links to giving forms.
Tour guides can sign up to assist with campus tours (or any other type of event) via a portal. Tour guides in this example are dataset records who will be able to log into the portal and manage their tour assignments.
Portals can be embedded inside of the Reader, allowing more dynamic pages to be accessible to readers (for example, dashboard pages). Conditional logic, tables, Liquid markup, and more can be leveraged to create an enhanced reader experience.
Portals can have multiple tabs within a single framework. This basic example demonstrates a default page with standard sections that display all the time, with a home tab, second tab, and third tab.