Create Themes

[shushugah]

As we grow/expand, we should have more concrete themes, that can capture interest/relevance of different tech workers. For example /auto sector can include all news related to BMW, Daimler, Volkswagon, but also existing articles we have, for example Bosch.IO tech interview about forming works council https://www.igmetall-berlin.de/aktuelles/meldung/boschio-und-ploetzlich-droht-softwareingenieuren-kurzarbeit or related events

In short, we should pool underneath each theme, relevantly tagged events, news posts, and static information. For example IG Metall Berlin is reasonable union to link under /auto section

While news about N26, Wirecard, and contact info of Ver.di for/fintech would be reasonable.

Similarly, on a page dedicated to Amazon, we'd link to our BerlinVsAmazon campaign, AWS/Fulfillment Centre resources etc..

I don't have a strong opinion on url

/theme/amazon
theme/gig-economy
which implies /theme would exist, and could offer placeholders for non existing themes, but link to a github issue/pull request then.
or plain
/works-council
/auto etc..

[mleimeister]

Very much in favour of themes. I wonder if we should distinguish between permanent info, e.g. the works council articles, campaigns like BerlinVsAmazon, position papers on e.g. platform economy, etc. which should each have their own theme site, and news articles, which rather represent temporary information? Alternatively, if we want to capture news under themes, we could come up with some basic introduction and info/position for each sector (auto, fintech, etc.) that can be the top site of the theme, and then list news below as an ongoing list.

[shushugah]

Exactly, so a theme could be:

Simple

Simple Amazon Content

---

Medium Complexity

Medium Amazon Content

• Cool History
• Berlin Vs Amazon Campaign
• Some links

---

Advanced Theme

Advanced content etc..

Fancy dynamic content

• Related events
• All events tagged with Amazon
• Embedded tweets
• Germany/Amazon related news from collectiveactions.tech

---

[ovlb]

Late to the party because work, the evil of the organising classes.

But I think it's a superb idea to create more topical discussions.

Two things that came to mind:

a) The current codebase feels kind of convoluted and I'm not sure how well it would fit more complex, structured content like this. It might make sense to explore a Backend + SSG setup. I've been giving Kirby a try recently and really liked it.

b) Not MVP but we should ensure to make the content searchable, as the list grows to keep the archives accessible.