Draft Content Hub

[erikwrede]

Establish a centralized content hub to support ambassadors and GraphQL content creators in discovering and sharing timely topics such as ecosystem news, conferences, blogs, and meetups.

We'd like to prototype Obsidian via GitHub and a Notion database. @jeanlucaslima will work on an Obsidian Prototype, @erikwrede will work on a notion prototype. The next agenda meeting will compare both prototypes.

• assignee(s): @jeanlucaslima , @erikwrede
• source: 01/26

---

[benjie]

Obsidian isn't well suited to multiple people editing the same file concurrently. I use and love obsidian, but for this a Google Doc might be a better alternative.

[benjie]

@jeanlucaslima If you reply (not react) to this, I can add you to assignees.

[jeanlucaslima]

Hello 👋

@benjie my suggestion is to use a Git repository with Markdown as the source of truth. It may or may not have optional scaffolding for tools like Obsidian or Logseq. Those tools would be clients, not requirements.

This isn’t intended for real-time, concurrent editing. If the content requires live co-authoring, then Git + Markdown is indeed not the right solution.

The motivation is to keep the content tool-neutral and portable. With Git, we get a clear, auditable history, an open format that’s easy to migrate, and an offline-first workflow. In contrast, Notion is proprietary, and Google Docs requires a Google account.

Happy to clarify further if helpful.

[benjie]

Sounds good; I like markdown + git as a solution - we can set up branch protections and what not to ensure that only admins can rewrite history/etc (e.g. in the case of abuse).

[jeanlucaslima]

@benjie doesn't this solves this issue? https://handbooks.graphql.cafe/

[benjie]

I wasn't at the meeting where this was proposed; but from the summary above (emphasis mine):

Establish a centralized content hub to support ambassadors and GraphQL content creators in discovering and sharing timely topics such as ecosystem news, conferences, blogs, and meetups.

I don't think so. Handbooks are for evergreen long term content; sounds like you want a hub for shorter term more frequently edited content?

[martinbonnin]

Would be great to have slack discord, graphql-weekly, typefully integrations so that people could, from slack and/or discord, submit a link for inclusion in weekly/typefully directly.

[jeanlucaslima]

I understand it better now, the Handbooks site is more suited to documentation.

Then how about it becoming something closer to a content radar for the GraphQL ecosystem: a place where ambassadors and creators can quickly discover timely topics such as ecosystem news, conferences, blog posts, and meetups.

The current idea is to prototype this as a small static site built with Astro, with GitHub + Markdown as the source of truth. The site would simply aggregate and surface content in a structured way (e.g. news, events, blog posts), while keeping contributions lightweight through issues or pull requests.

Some directions I’d like to explore in the prototype:

• Markdown content stored in the repo (portable and tool-neutral)
• Structured entries for news, conferences, meetups, etc.
• RSS ingestion to surface ecosystem updates
• Optional integrations (Slack/Discord notifications when new topics appear)
• Ability to submit links from Slack/Discord directly into the hub (for example via a bot or slash command that creates GitHub issues or pull requests)
• Potential integrations with tools like Typefully to help ambassadors share content

The idea is not to create long-form documentation, but rather a signal hub where people can quickly see "what’s happening in GraphQL this week".

I also think this could live nicely under a dedicated subdomain, something like content.graphql.cafe or radar.graphql.cafe, so it remains clearly separated from documentation-style content like the Handbooks.

I'll start with a small prototype and send it here for everyone to look at.

[martinbonnin]

radar.graphql.org ❤️ 📡 I love it!

I think the main goal is to crowdsource the information/news. We can't give everyone access to GraphQL weekly but we should make it as easy as possible to share news and aggregate community members accross different tools.

[martinbonnin]

Another use case: automate some posting. For an example, we could post GraphQL Weekly automatically on socials.

All in all, I think the 2 main goals are:

1. Reach people where they are. Make it easy to submit content from:

• Slack
• Discord
• https://www.graphqlweekly.com/
• Twitter/LinkedIn/Bluesky

2. Help us automate some of the tasks

• Automatically post GraphQL Weekly
• ...

[rnative77]

@benjie @jeanlucaslima @erikwrede Hi, I want to specialize in GraphQL. I'd also like to contribute to the project.