cState v3.0 Release Notes

Release Date: 2019-01-24 // over 5 years ago
  • This is a _ big _ release — once again thank you to everyone who supports the project. Before upgrading, of course, make a copy, especially if you don’t use Git, of your existing status page in case issues arise. You can just revert back on Netlify to a previous deploy if you so wish.

    🚀 Delayed for 3 months, originally planned for release in October (for Hacktoberfest 2018). But it’s finally here! There are now almost 200 stars for the project (from some really awesome developers, too)! Still unbelievable to me.

    👀 👁 Have you seen the cState quick setup guide on the Netllify Blog? It’s what got the project mildly popular in the first place!

    Migration

    The minimum Hugo version is now 0.48. A new version of Go brings variable overwrites, which may be used in parts of cState in the future.

    ⚡️ 1. Update cState like normal.

    1. Make sure your baseURL is NOT A SLASH IN A PRODUCTION. Moving forward, if the baseURL is not properly defined, RSS and other functionality may not be supported, as well as cause unexpected behavior.
    2. Add some values to your config.yml file to enable new functionality and ensure compatability:

    ➕ Add defaultContentLanguage & preserveTaxonomyNames to the very bottom of the config file as well as a taxonomies object:

    defaultContentLanguage: enpreserveTaxonomyNames: truetaxonomies: affected: affected
    

    🔄 Changelog

    cState is more powerful than ever — now with:

    image

    • Redesigned issues. Resolved issues in the history view are now much more condensed, letting you see more than 1 issue on a single page. The focus is put on the time it took to resolve the issue, calling
    • Fully implemented settings in Netlify CMS (#18). Up until this point, Netlify CMS was only used for posting incidents. Now you can even edit the configuration files with it!

    image

    • ⚡️ Updated, more consistent look & CSS. Moved some stuff around, added more comments, now using BEM in more places, removed unnecessary code. Other minor changes to sizing and colors.
    • Made RSS feeds even more discoverable, added links to the footer (#35). Community contributed idea. Thanks, @SamWhited!
    • 👍 RSS feeds now include more content, better in line with other status page feeds. An example of this is Reddit’s status page Atom feed, which was used as a somewhat starting point to improve the current RSS feeds in cState.
    • Issues now include the date when the incident had been resolved. Just hover over the “Resolved in…” text on the issue page.
    • 🔖 Versions will now be shown in console and generator tags. In previous versions, the version numbers would either be thrown around everywhere or just wrong.
    • You will now be automatically redirected to the Netlify CMS page when cState detects access_token in the URL. This was a confusing UX pattern, since you’d often be redirected to the homepage (for example, after using SSO login like Google’s) without any error message and the token waiting to be used in the URL.
    • Localization. (#12) Introducing defaultContentLanguage! English & Lithuanian translations are available right out of the box. Speaking of which — why don’t you help us translate cState?
    • Customizable date formatting. (#19) If you have Params.dateFormat in your config file, you can change how dates look in places like issue templates. If you’re upgrading from v2 and don’t care about the date formatting, the default will be kept as is.
    • 👀 See what was down (#25). Thanks to @avelino for the suggestion! This also brings about the ability to view a component’s entire incident history, like from a tag.
    • 404 the right way. Turns out 2.0 didn’t even have a 404 page. Now it has one. Here’s what it looks like.
    • Made RSS feeds discoverable (#34). Community contributed idea. Thanks, @SamWhited!