cState 2.0

The first commit for cState was on May 1st, 2017. Today the project has grown into a full fledged status page, for the “little guy.” Without further ado…

Are you starting fresh?

Great — documentation is now ready on the wiki!

Or upgrading from cState v1.0?

It is recommended that you set up an archive site and start fresh; cState 2.0 is (almost) a complete rewrite from top to bottom, with a design that builds on top of the simple Hugo foundation.

Have a question or want to contribute?

Please do! Linky

cState v2.0 (Release Candidate 4)

This version includes breaking changes for users of Netlify CMS.

cState has used uppercase syntax for its frontmatter since the beginning like this:

Title: GGRadio Docker Upgrades

However, because of Netlify CMS’s behavior with slug URLs, all issues now must have lowercase frontmatter. This change is now reflected in docs and the README.

The language for auto refresh has also been changed as it seems to sometimes be rather unreliable.

cState v2.0 (Release Candidate 3)

• Updated Netlify CMS / admin panel stuff (see #16)
• #15 & #17 should be fixed
• Emergency doc fixes (update command in readme was wrong)

cState v2.0 (Release Candidate 2)

Bug fixes (see: #14).

cState 2.0 (Release Candidate 1)

Oh, oh, we’re almost there!

cState will soon reach a stable release. You may use this version in production, as no more major changes will take place.

This release contains quite a few changes: bug fixes, internal changes to the overall quality of the code, and many major updates.

This version’s changelog is as follows:

• Custom HTML actually being fully implemented; only some of the partials were actually working in v2-dev2
• Added pagination to incidents list; you can change how many incidents are shown per page in the config file
• Removed uptime statistics, API scaffolding as it wasn’t properly implemented for a stable release
• Added auto refresh — you can disable it in the config, it’s set to refresh roughly every 5 minutes
• The “Last updated” ticker next to the status also now updates every 5 seconds instead of every one
• Release versions are now shown in the footer
• Repository moved to cstate/cstate from mistermantas/cstate

You can also now find an example of how cState looks like in production at cstate/example.

There have also been some improvements made to the documentation on the wiki and README. The live demo link works again. Hooray!

P.S.: If you’re interested in cState and want to contribute, spread the word, or whatnot, don’t hesitate to reach out!

cState v2.0 (Developer Preview 2)

cState is well on its way to a stable 2.0 release. There are some major breaking changes in this developer preview.

• Google Analytics can now be setup with a tracking code from config.yml (fix #10)
• Custom HTML support is here and it replaces customCSS & customJS (fix #7)
• Breaking change: Components/systems can now have explainer text & custom HTML (partial) code below them (fix #9)
• Improved uptime statistics — now shows in percentages (WIP)
• Significantly improved docs on wiki
• Incidents now truncated on homepage
• WIP: Removed unstable “Last updated” code; see #2, #11
• Numerous little bug fixes & changes
• Removed border and faded color choices — you may remove that from your config

cState v2.0 (Developer Preview 1)

cState is maturing! v1.0 was just an announcements page, but v2.0 not only allows much more customization, but also significantly improves the Hugo-powered back-end, and gives more insight into service downtime (like how long it took for an issue to be fixed).

• Simplified setup (see README)
• Improved documentation and comments
• Individual components now can change status (fix #6)
• Started wiki & there’s also now a cState Gitter
• Added option to set brand color independent from confirmation color
• Now you can see how long it took for an issue to be resolved
• Incidents now have a completely new design
• Added “Back to top” button in footer

• Bug fixes and performance improvements

There are some known issues, however:

• Development locally requires themesDir to be defined
• Uptime stats do not show up when there’s an active incident (scratch mod throws error)
• Netlify CMS intergration still needs some work