Your team already
thinks together.
Now publish together.
Everyone on your team blogs from their own AI — Claude, ChatGPT, Cursor, whatever they use. Each person gets their own blog. Every post rolls up into a shared team feed. One conversation, one command, it’s live.
Three roles,
one feed.
The team
A team has a name, a slug, and a shared feed at scsiwyg.com/your-team. It’s the front page — a chronological rollup of everything your members publish.
Members
Invite people by email — they don’t need an account yet. When they accept, they get their own blog under the team at scsiwyg.com/your-team/their-name.
The feed
Every member’s post appears on the team page automatically. Individual blogs exist too — readers can follow the team or a specific person.
Clean URLs,
no confusion.
/atomic47Team feed — all posts from all members, newest first/atomic47/davidDavid’s blog under the team — just his posts/atomic47/david/auth-rewriteA specific post by David, in the team context/david-personalDavid’s standalone blog — completely separate, if he has oneTeam blogs and personal blogs are independent. A person can have both. Publishing to one never affects the other.
Everything a solo blogger gets,
plus the team.
Their own blog
Full blog at /team/member with its own theme, layout, and subscriber list. Not a subfolder — a real blog.
Publish from any AI
Claude, ChatGPT, Cursor, Windsurf — whatever they use. Same MCP connection, same "blog about what I just did" workflow.
Newsletter per blog
Each member can enable their own newsletter. Subscribers to the member's blog get their posts. Team-level newsletters are separate.
Wiki pages
Members can maintain a structured wiki under their blog — documentation, research notes, knowledge bases. All searchable.
Private or public
Posts can be public (on the team feed) or journal-only (private to the author). Teams don't force visibility.
Opt out per post
Any post can be excluded from the team rollup. Write something personal? Keep it on your blog only.
Set up a team
in two minutes.
From your account page or by asking your AI.
Create the team
Go to your account → Teams → New team. Pick a name and a slug. Or tell your AI: “Create a team called Acme Labs with slug acme.”
Invite members
Add people by email. They get an invite link. When they sign up (or sign in), they’re in — with their own blog under the team, ready to publish.
Everyone publishes
Each member connects scsiwyg to their AI and writes from wherever they work. Posts flow into the team feed automatically. No editor, no CMS, no approval queue.
Teams that already talk
to their AI.
Engineering teams
Ship notes, architecture decisions, postmortems — written in the moment, not reconstructed a week later.
Research groups
Each researcher maintains a wiki and blog. The team feed becomes a living literature review.
Agencies and studios
Client work, case studies, design rationale. Each person's perspective, one shared record.
Open-source projects
Contributors blog about what they built. The project page aggregates it all into a changelog the community can follow.