In honor of (almost) nearing 100 stars and #hacktoberfest, v3 is almost ready to go out from the pipeline.

Changelog

cState is more powerful than ever — now with:

• 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 & language files in Netlify CMS (Add visual settings via 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!

• 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 (Add RSS feed link to 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.

From Developer Preview 1:

• Localization. (Make every string translatable / changeable #12) Introducing defaultContentLanguage! English & Lithuanian translations are available right out of the box. Speaking of which — why don’t you help us translate cState?
• Netlify CMS experimentation. The preview window has begun receiving some changes as well as the Markdown body editor field. Give it a shot!
• Customizable date formatting. (Allow to change date format #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 (issue affected list #25). Thanks to @avelino for the suggestion! This also brings about the abillity 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 (Add links to RSS feeds #34). Community contributed idea. Thanks, @SamWhited!

Upgrading from v3 is currently not recommended, as cState is still in an unstable stage, however, the guide is being prepared for future use.

Migrating to v3 from v2

⚠ 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.
2. Change your config.yml file accordingly:

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

defaultContentLanguage: en

preserveTaxonomyNames: true

taxonomies:
  affected: affected

There’s also other bits & bobs — small changes & fixes, some thanks to the generous contributions of others.

Thanks for using cState! ❤️