cState v4.0-rc1 Release Notes
Release Date: 2019-12-15 // over 4 years ago-
cState v4.0 brings many important changes to help you get more from your status page.
π The final stable release will be out before 2020.
Thank you to the people who keep using cState and have starred it. It feels good to know that I have made something that helps people.
Development began on: May 1, 2019
π Release date: December 15th, 2019
π Stars at time of release: 418β¬οΈ > β ATTENTION REQUIRED. This version brings many major changes that require changes to your configuration file and more. Please read the migration guide and changelog before upgrading.
π Changelog
β Added categories (#8)
Fun fact: the original issue created Jul 7, 2018.
Every system/component needs a category:
systems: - name: Gatewaycategory: North Coast - name: Backup Gatewaycategory: Uncategorized
You can set categories to be collapsed (closed) when the user visits the status page. You can also create a catchall category for components that should not be nested under a category.
categories: - name: North Coastdescription: The worst one. Or the best one.closed: true - name: East Coast - name: Uncategorizeduntitled: true
You need to have at least one category. Take a look at the example β you can add an Uncategorized category and hide that.
Simply copy paste:
params: categories: - name: Uncategorizeduntitled: true
and add
category: Uncategorized
to every system/component.π§ You can now use any color, not just HEX colors, in the configuration file (#83)
Netlify CMS does not correctly interpret certain color values (most shockingly the defaults). To fix this bug, HEX codes now need the
#
in front in theconfig.yml
file. You can also use other color types, like rgb(), but if you care about airtight browser support, keep using HEX codes or web safe colors.β Added read-only API (#27)
This feature is enabled out of the box for new websites with the new
config.yml
file. If you want to enable this feature, look at the migration guide.β‘οΈ The API will get better with further updates.
π Documentation:
https://github.com/cstate/cstate/wiki/APIInformational posts
You could always make pages with cState, pages that would not show up in the incident history.
v4 allows you to make pages that can show up in the incident history but are similar to basic pages.
Informational pages need a title, date, and a boolean of
informational: true
.Design: Auto dark mode (#87)
Thank you to @microsockss for the help with this.
β If your OS and browser support dark / night mode, specifically
prefers-color-scheme
, cState will automatically enable a dark UI. This has been tested on:- π Windows 10 β Chrome
- iOS 13 β Safari
- Android 9 (Samsung Galaxy S10) β Android (with certain flags)
0οΈβ£ By default the
.Params.disableDarkMode
boolean is set it tofalse
.Dark mode uses built-in hard coded colors to ensure contrast and legibility.
β‘οΈ If you use custom CSS, please test this behavior before pushing to production. This feature is enabled automatically when you update.
Design: Show years in incident history (#43)
You can opt-in to this new layout with the
.Site.Params.enableYearlyIncidentHistory
boolean inconfig.yml
. There is no pagination with this system but you can link to years like this: https://cstate.mnts.lt/#2019β‘οΈ This is a good option for status pages that do not get updated often.
Other little changes
- If you have βInterβ, it will now be the primary font for cross-platform use
- π Auto refresh was removed
- β Added donation info to README
- π Clarified docs
- General improvements
- Shape next to "Unresolved!" shows what severity an issue is
- β² = disrupted
- β = down
- β = notice