You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
at the moment: cstate/hugo only creates pages for systems, which are currently affected by an incident.
clicking on a system's name (without incidents) on the index page forwards to the 404.html-page, with is showing a vague message like "doc not found OR no incident recorded OR url maybe wrong" (it's not the fault of the 404-page: he/she/it can't know for sure)
It would be more user-friendly, if more precise information could be displayed.
Describe the solution you'd like
rendering/creating page for all systems would be a solution for this problem. _default/lists.html seems to be already prepared for this usecase: Lines 59ff formulate an if-clause to include the calmBeforeTheStorm-message. (however, as the pages for systems currently will only be rendered, if there are incidents, the calmBeforeTheStorm is never displayed) :(
Describe alternatives you've considered
i tried to create inndividual pages per system in a folder content/affected/. this kind of works. however, this would be some form of duplicate data storage, as the systems names are already defined in config.yml. (Furthermore, I wasn't able to display die incidents/issues belonging to the system on it's content/affected/-Page. -- if fixable, this might be an alternativ, though)
The text was updated successfully, but these errors were encountered:
this issue goes away when you create the first issue. So, in other words, this issue is not persistent. What's your use case that you have many empty categories/systems?
I want to show the user the extended system's description mentioned in #270 . however, if the site is not rendert, the extended description is not shown.
in the description we placed additional link to tickettools, selfservice and a small component intro.
we plan to delete older incidents after a couple of weeks.
I want to have the same "look and feel" for all systems the user clicks (regardless if theres currently an incident or not)
a possible - but a little bit tedious (if not done by python ;)) - solution without changing cstate looks like this:
maybe you could add this to the Wiki, @mistermantas
create for each system a folder: content/affected/SYSTEMSNAME and place a _index.md file in there (note the _) with the content
---
title: Title of the system
---
the SYSTEMSNAME needs to exaclty match the URL, which is shown in the components list on the main page. just copy it from there.
(if you want to create it yourself: it is generated from systems-array in config.yml like this: $system.title | urlize, so the url-safe version of the name. i.e. Spaces and most other special chars get replaced by '-'. However, '+' and '_' won't be replaced)
Example: config.yml:
- name: Media Proxy
description: This is the service responsible for serving images, audio, and video. It is reliant on our CDN.
category: Uncategorized
Is your feature request related to a problem? Please describe.
at the moment: cstate/hugo only creates pages for systems, which are currently affected by an incident.
clicking on a system's name (without incidents) on the index page forwards to the 404.html-page, with is showing a vague message like "doc not found OR no incident recorded OR url maybe wrong" (it's not the fault of the 404-page: he/she/it can't know for sure)
It would be more user-friendly, if more precise information could be displayed.
Describe the solution you'd like
rendering/creating page for all systems would be a solution for this problem.
_default/lists.html
seems to be already prepared for this usecase: Lines 59ff formulate an if-clause to include thecalmBeforeTheStorm
-message. (however, as the pages for systems currently will only be rendered, if there are incidents, thecalmBeforeTheStorm
is never displayed) :(Describe alternatives you've considered
i tried to create inndividual pages per system in a folder
content/affected/
. this kind of works. however, this would be some form of duplicate data storage, as the systems names are already defined inconfig.yml
. (Furthermore, I wasn't able to display die incidents/issues belonging to the system on it'scontent/affected/
-Page. -- if fixable, this might be an alternativ, though)The text was updated successfully, but these errors were encountered: