Currently some chapters have dedicated event streams, while others rely on the TWC Meetup.com

I would love to have an aggregated stream of events, both as an API, and where we visually display them, e.g. on techworkerscoalition.org/events

• Berlin events available here in ICS (iCalendar) and JSON format
• Boston iCalendar and google calendar
• London google calendar
• NYC Google Calendar
• San Diego Meetup and
• TWC Meetup Calendar
• Your local chapter calendar? Please comment with ideas/other calendar sources!

Audit the following files

• .travis.yml
• .s3_website.ymll
• .java-version
• scripts

• Dynamically load blog posts from techworkersberlin.com/news
• Standardize blog url and manually redirect with netlify.toml (backward compatibility)
• Add DecapCMS for shared editing capabilities without using GitHub directly
• Integrate https://news.techworkerscoalition.org/ somehow?

Visual flow

• The /blog interface could look like Berlin site; where it shows unique authors (or organizational) https://techworkersberlin.com/news
• And each individual blog post could also show author/image/date/title and a backlink to all blog posts on top, like here This PR (in Berlin specific repository) shows what that code might look like techworkersco/twc-site-berlin#267

we should consider adopting the tailwind/postcss/jekyll build system im using over in https://github.com/emergentworks/project-not-911/tree/master/docs which is also a jekyll site, but uses a more modern (and performant) css approach

Expose navigation items for screen sizes that are larger than mobile. Attaching a mock for a potential direction. If we are aligned, I will update it to show more accurate specs, hover states, and selected states.

Hey @kidmillions there are several reasons why I would recommend moving to Netlify:

1. Continuous deployments
2. Handy build plugins, such as image compression, url checkers etc.. see here: https://github.com/netlify/plugins
3. Preview links e.g for this PR: techworkersco/twc-site-berlin#74 we had this preview link: https://deploy-preview-74--techworkersberlin.netlify.app/
4. A CMS to edit website without knowing git would make it super accessible. We can still have a traditional PR approval workflow even with a CMS.

The Berlin fork of the website works quite nicely with Netlify, and we get all of these features for free. https://techworkersberlin.com/

(I want to move https://techworkersberlin.com/ to berlin.techworkerscoalition.org, but that's another issue)

Should have something similar to techworkersberlin.com, with code available here. Nice visual/easy to find icons https://github.com/techworkersco/twc-site-berlin/blob/develop/_includes/links.html

Here is a global list of chapters, please edit/add any missing chapters See #120 for inspiration.

• Austin #142
• Bangalore
• Berlin #116
• Boston
• Chicago #195
• DC (Washington)
• LA #131
• London
• Montreal
• NYC
• Ottawa
• Philadelphia
• PDX (Portland) #120
• San Diego #131
• Seattle
• SF Bay Area #128
• South Bay / San Jose
• South Florida #131 (Edit: Now Removed)

Oops, see #127

Greetings from Berlin! 👋 The Berlin TWC chapter wants to support multiple languages. Namely English and German for now, but also others. Seeing this website is probably the most popular one, it makes sense to add I18n here as well.

I have heard good things about the following plugin: jekyll-multiple-languages-plugin and with English being the default language, no url routes would change unless absolutely wanted. e.g. /about still maps to /aboutwhile we can either have de/about direct to german version, or even a custom permalink name like de/impressum route there

Any thoughts? Shall I start working on a PR for further discussion?

Either on the homepage, or as a separate "Resources" page, but it could be useful to have a list of articles written about/by TWC to give visitors more information

(not sure what the process for adding/removing articles should be, just thought I'd throw this idea out there in case anyone had ideas)

Currently you can find the locals on the home page, but we should also have a dedicated page to each local. And even right there in the view, information about each local, such as contact information, websites etc...

and maybe linking them to a map.

/locals

Currently we get a very ugly 404 description with something like:

404 Not Found

Code: NoSuchKey
Message: The specified key does not exist.
Key: bla
RequestId: 8C20DDCBE295A4ED
HostId: 14uJGHIBAH3qUelJbkmLTaC6dM8QxpoihXXGfrXMYESEqCXSNGIosM1v/4NuTIF6QfUnexMSk9Q=

An Error Occurred While Attempting to Retrieve a Custom Error Document

Code: NoSuchKey
Message: The specified key does not exist.
Key: error.html

Get more precise analytics and figure out what pages' SEO we can improve on.

https://github.com/techworkersco/twc-site/blob/develop/slack-thanks.md

This appears when you try to sign up for newsletter or slack, and links to old Bay Area Meetup page. Needs to be updated to not include a link at all, link back to home, or include a list of locals.

1. Netlify is free.
2. We currently already use netlify for build previews of every PR
3. TravisCI ecosystem adds complexity
4. Main steps we'd need to take, is to update A records in domain registrar of techworkerscoalition.org

Support dark mode

Pages to test it on

• home page (including the BlackLivesMatter banner)
• Subscribe page https://techworkerscoalition.org/subscribe/
• https://techworkerscoalition.org/community-guide/

When visiting https://techworkerscoalition.org/subscribe it should be easier to join local specific newsletters, chat groups etc..

We currently have a newsletter mailchimp portal here, which could be linked on same page as techworkerscoalition.org/subscribe and https://news.techworkerscoalition.org/subscribe/

For example I will list need of Berlin Chapter

• Join Berlin backed Sympa Newsletter (currently you must email [email protected])
• Join Berlin Only Slack Group

After a user signs up, they're automatically added to ActionNetwork, and conditionally invited to slack. We should make that clearer from this message and also encourage them to follow our social media. In short, let's make this page snazzier https://github.com/techworkersco/twc-site/blob/master/slack-thanks.md

Proposing the following edits to improve readability:

Dark Mode

Make background color darker to increase contrast between text and bg
.primaryBg { background: #191919; }

Change nav bar color
.secondaryBg { background: #2E2E2E; }

Similar to this commit, inline the CSS, so that it is not a blocking resource, or a separate HTTP call. Our CSS is extremely light weight as is.

https://github.com/shushugah/shushugah.github.io/commit/416b8d386993e8ed2f5f73fa575581c31ccf43e9

should be pretty easy since it's a statically generated site

Techworkerscoalition.org/events exists now with #360

What further improvements can be made?

• Make it easier to distinguish who/where an event it, perhaps with label tags
• add filtered events in different sub-pages, e.g https://techworkerscoalition.org/nyc/ could link to NYC and or Global events
• Improve image CSS formatting of events for both desktop and mobile
• Include TWC Community Guidelines/CoC under each event?

I'd like to see a code of conduct for Slack that addresses some things that have come up in the past week including

• who the moderators are and how to get in contact with them
• prioritization of the safety of marginalized groups over comfort of privileged
• consequences for CoC violations

some good examples:
https://wealljs.org/code-of-conduct
https://lgbtq.technology/coc.html
https://docs.google.com/document/d/1OBYKDw4mDVX3A25Eo2g397XwF1NvteZgY_pVDnxoBu8/edit
https://docs.google.com/document/d/1UqK1_M6_I-sm9XLmSJt_SgYfo5tHg9z-ar5SHy62ENI/edit#heading=h.3u02axafjdg5