TinaCMS + Fumadocs: Bring Visual Editing to Your Docs

📦 The package (TinaCMS + Fumadocs) https://github.com/0xharkirat/tinacms-fumadocs-pkg

🔗 Tools

Fumadocs: https://www.fumadocs.dev/

TinaCMS: https://tina.io/

Roadmap: https://tina.io/roadmap

💬 Discussions

TinaCMS + Fumadocs : https://github.com/tinacms/tinacms/discussions/6973

📞 Contact us: https://bit.ly/4fAFrVx

Editing docs directly in Markdown is great for developers, but not so great for non-technical team members who just want to update content without living in VS Code.

In this video, Hark Singh shows how he added TinaCMS-powered visual editing to a Fumadocs site, making it easier to edit Markdown, add images, create new pages, insert UI components, reorder navigation, and even make live changes through Tina Cloud.

He walks through the old manual workflow, then shows the visual editing experience in action, including saving changes back to the file system, committing updates to GitHub, and triggering Vercel deployments from the CMS.

The package is currently a preview, but it points to an exciting future for developer-friendly docs that are also friendly for the rest of the team.

00:00 | Introduction

00:27 | What Fumadocs is used for

00:53 | The manual Markdown editing workflow

01:24 | Creating and ordering pages manually

02:19 | Visual editing with TinaCMS

02:41 | Editing Markdown and adding images

03:31 | Creating a new page visually

04:00 | Adding Fumadocs UI components

04:25 | Reordering navigation with drag and drop

05:15 | Live editing with Tina Cloud, GitHub, and Vercel

🌐 About SSW: https://linktr.ee/SSWTV

🔗 Links:

LinkedIn: https://linkedin.com/company/ssw

Twitter: https://twitter.com/ssw_tv

Facebook: https://facebook.com/SSW.page

Instagram: https://instagram.com/ssw_tv

Tiktok: https://www.tiktok.com/@ssw_tv

👋 Get in touch:

Hark Singh – SSW Software Engineer I

About: https://www.ssw.com.au/people/hark-singh

LinkedIn: https://www.linkedin.com/in/talesofhark

#TinaCMS #Fumadocs #CMS #VisualEditing #Markdown #Documentation #MDX #Vercel #GitHub #WebDevelopment #DeveloperTools #SSWTV

V4 – Pam

About the speakers

Hark Singh

Hark is a passionate Full-Stack Developer, who builds clean, reliable software with a focus on user experience and delivery discipline.

He joined SSW Newcastle through FireBootCamp, SSW’s intensive, real-world training program for elite graduates – where he worked in a high-pressure, consultancy-style environment, building production-grade solutions using Angular, .NET, Clean Architecture, and Azure DevOps. After impressing the mentors and senior architects, he was invited to join SSW full-time.

Microsoft Teams Etiquette: Simple Habits That Make Meetings Better | Adam Cogan

Whether you’re working remotely or in the office, small habits can make a huge difference in Microsoft Teams meetings. In this video, Adam Cogan shares practical etiquette tips to help meetings run more smoothly—from introducing people who join the room, to announcing yourself when joining a call, using screen sharing respectfully, and ending meetings with a recorded summary that can automatically create a Product Backlog Item (PBI).

These simple communication habits improve collaboration, reduce confusion, and make hybrid meetings more inclusive and productive.

Treat Your Code Like Uranium | Adam Cogan

Adam Cogan shares a striking story comparing two World War II factories—one ordinary, one handling uranium—and the surprising lesson that the uranium workers lived longer because they followed disciplined, risk-aware practices. He connects that idea to software teams: the best outcomes come from careful habits like automated tests, telemetry, pull requests, retrospectives, shared rules, and good tools. The message is simple: treat software delivery with the same respect as dangerous work, and you’ll reduce stress, avoid chaos, and get better results.

3 Tips for Better Video Recordings | Adam Cogan

Great coaching can dramatically improve how you present, communicate, and learn. In this video, Adam Cogan shares 3 practical coaching tips that SSW uses every day—from onboarding and role plays to improving video delivery. He explains why having a coach matters, why immediate interruption beats delayed feedback, and how repeating corrections helps lock in better habits.

TinaCMS + Fumadocs: Bring Visual Editing to Your Docs | Hark Singh

Discover how to connect Playwright with AI agents and unlock powerful workflows.

Stop Using 👍 Wrong in Teams | Adam Cogan

A quick communication tip from Adam Cogan: don’t use 👍 as a catch-all response when someone assigns you a task in Teams, Slack, or Google Chat. In the example Adam gives, if a task will take about five minutes, a thumbs up is too ambiguous because it does not clearly say whether you’ve read it, agree with it, are doing it now, or will do it later. Instead, use 👍 for agreement, 👀 to show you’ve seen the task and are actively working on it, and then replace 👀 with ✅ once the task is done. It is a small change, but it removes ambiguity and cuts down unnecessary follow-up messages.

How to record a done video in SSW | Sylvia Huang | SSW Rules

Sylvia Huang from SSW shares her SSW Cultural Exchange experience from Hangzhou, China to Australia

4 Essential Sales Tips for Engineers | Adam Cogan

Not a salesman? No problem. Adam Cogan shares 4 practical tips to help engineers navigate sales meetings with confidence. Learn how to stop “selling” and start solving, how to talk numbers without the awkwardness, and why being transparent about your process wins more clients.

Do you explain why you’ve deleted or updated an appointment? | Adam Cogan | SSW Rules

Ever wonder why a meeting was moved or cancelled? Adam Cogan explains the “Secret Ingredient” to professional scheduling: always include a version history and reason for change at the top of your appointments. Improve clarity, keep a record of changes, and hold participants accountable with this simple SSW Rule.

Chat first before changing others’ code | Adam Cogan

Changing someone else’s code? Don’t just dive in! Adam explains why it’s important to check the source history and talk to the original developer before making changes. A quick chat can save headaches and keep everyone on the same page. Perfect advice for devs working in teams!