There's a repo with a Gatsby website as starting point: https://github.com/cdk-dev/website/

For simplicity reasons, it'll be deployed via Netlify for now.

I have no karam to it. Not even request review or label.

There's the idea to setup a discord for cdk.dev - This would be an addition to Slack and other potential communication channels. It has a few aspects which makes it more suitable to larger communities (e.g. a block functionality).

/cc @mbonig

Let's provide a page with aggregated content from the community:

• blog posts
• tweets?
• Repositories

Something in this direction perhaps https://amplify.aws/community/posts?%7B%7D

We should get some kind of logo, the current one doesn't work very well in my opinion.

I like the idea of integrating data from slack into some more archival solution. I figured maybe a slackbot that would allow someone to tag a thread and that thread gets copied out to an external system.

Let's continue discussion on this thread. We can then identify a solution and find members in the community to help implement.

it would be good if the UI catered for long construct titles - it's very difficult to navigate the catalog currently since many (most) names are cropped by the GUI.

Alongside the recently introduced CDK forum, I believe there's place for a dedicated Slack chat.

Thoughts?

Hi all,

I see some people are really active in the CDK.dev Slack channel and help out daily.
To honour their contribution to the community I think it would be cool to mention them on CDK.dev.

It could be a monthly or quarterly rotation and be determined via a poll in the Slack channel.

What do you think? Is that something people would like?

Example for the page:

A dedicated section for courses, workshops and similar things.