Quick Start Guide
Everyone needs a starting point to help center their journey. Here's a quick guide to help you begin.
Quick Start Implementation Outline
Task | Description | Questions to Ask/Answer |
---|---|---|
Add Administrative users | Add administrative users to your page | Who will be an Admin user? Will there be Incident Managers who cannot access the Settings and Integrations menus? |
Generate list of components | Generate list of components Generate a list of all the components needed on your status page and their hierarchy | What components will be included on the page. Will there be Parent/child relationships? Will they be organized by region, function or other dependencies? |
Implement components, establish structure/relationships | Implement components based on your list | |
Beacon Configuration and Implementation | Establish Beacons for incident creation, resolution, and 3rd party sourced components | What 3rd party providers will you be posting information about on the page? What services of theirs do you depend upon? Do you use 3rd party monitors? Under What conditions would you create an incident or information posting as a result of information this service can provide? |
Status Page Access Review (Private Page) | Review of access to the status page resource, the rss feed, and administrative portal | Who should have access to the page? What should they see? Are their varying views per user role or per audience group? |
Integration Setup | Configure integrations based upon documentation provided by StatusCast. | What integrations do you wish to establish? Will SSO be used? For what roles? Will you be adding notifications to other channels? Sending notifications through your own mail server or Twillio account? Are you using posting Office 365 data to the page? |
Custom Domain Setup (cname) (if needed) | Make DNS entries, notify StatusCast for Redirect: | Will you be using a custom cname? |
Gather and implement status page design requirements | Gather requirements for status page design (desired widgets, css changes, content, etc…) | How would you like to organize the data on your status page? Which widgets will you use? How will you design the branding? Will your marketing team require input? |
Gather and implement notification design requirements | Gather requirements for design of email notifications (content layout, branding, content, etc…) | How will you design the branding of the emails? Will your marketing team require input? |
Generate and implement incident templates | Create incident templates to make creating incidents quick and easy | What should the default text for the average incident or maintenance event be? |
Review incident creation workflow process | Review the overall incident creation process including how it relates to components | Evaluate for ease of use for Incident Managers |
Import subscribers | Add subscribers to status page with appropriate component subscription. | Who should be subscribed? |
Go Live! | Make an announcement and start sending traffic to your page. |
Need more information? A more detailed guide is linked in Next Steps
Updated 10 months ago
What’s Next