homepage: chronological feed of incident stories, and a quick summary next to each incident, served as single feed on homepage after intro, and other stuff (maybe broken into pages by year and only show incident from last few months on homepage, and old Incidents are moved to archive page.
Get rid of most pages of current page structure, and only have following pages:
/about page, talks about the initiative and when we meet, and how to contribute new incidents, etc.
/meetup page for into about current and past meetups that we did
learn page for other literature like talks, research and blog posts, page /learn where we link to educational content about failure modes in systems.
archive, old incidents that used to be on homepage.
each incident will be shown as a short card on the homepage, with details like Company, when it happened, how long it lasted, and sources, and other links to the chatter about the incident.
goal of redesign is to make website useful and users can just open it and see recent incidents, and learn from them.
I am also planning to make substack active again, and send an email each time we add new incidents on website. content can be short form or copy of what we add to website.
right now website is very plane and boring.
homepage: chronological feed of incident stories, and a quick summary next to each incident, served as single feed on homepage after intro, and other stuff (maybe broken into pages by year and only show incident from last few months on homepage, and old Incidents are moved to archive page.
Get rid of most pages of current page structure, and only have following pages:
/about
page, talks about the initiative and when we meet, and how to contribute new incidents, etc./meetup
page for into about current and past meetups that we did/learn
where we link to educational content about failure modes in systems.each incident will be shown as a short card on the homepage, with details like Company, when it happened, how long it lasted, and sources, and other links to the chatter about the incident.
goal of redesign is to make website useful and users can just open it and see recent incidents, and learn from them.
I am also planning to make substack active again, and send an email each time we add new incidents on website. content can be short form or copy of what we add to website.