So, we've been a bit quiet here 😅 but actually we've been working our butts off on the editor experience (and the user experience in general). Here's a quick peek 👀at the content editing UI...
The work by
@JossMackison
on the SplitView component for Keystatic's Admin UI is outstanding 🎉
♿️ ARIA window splitter pattern
🌍 RTL support
📏 min/max support
↔️ drag "snap" region
⏎ return to default size on double click
🎹 keyboard navigation
✨ CSS variables and clamp()
Keystatic Cloud's admin UI...
Wed (left) vs Fri (right) 👇
If you ever needed a micro case study in the value of a fit-for-purpose design system... here you go
Courtesy of
@JossMackison
Static MDX blog with dynamic Astro DB likes count 🤗
@thekeystatic
+
@astrodotbuild
DB is *nice* 👨🍳
Light mode FLASHBANG + outdoors with birds — deal with it 😎
Keystatic is almost ideal
I wish merging pull requests would be built into
@thekeystatic
dashboard
I don't want to rebuild on each change, so it would be nice to push into not main branch
And then have "publish" button to merge into main branch and run rebuild
You know you're on to a good thing when it feels good and fast and nice to build and ship real things with your thing, before you have this sentence worked out... 😆
But also... TODO 📝
Added a new Resources page on the Keystatic docs — will bring some more stuff in the near future.
A good place to collate all the different bits of Keystatic content out in the wild 🤗
Published a guide on using
@astrodotbuild
's <Image /> component with Keystatic, since it's is sorta tricky.
It covers uses cases for both "standalone" images (stored in frontmatter) and images inside content components.
🧃 Little quality of life addition: when copying, the editor will put the markdoc for your selection on the clipboard so you can copy/paste content between the Keystatic editor and a text editor without losing formatting, blocks, etc
Pretty excited about the smooth
@thekeystatic
🤝
@astrodotbuild
integration happening soon.
You can already use Keystatic with Astro, but it's about to get **much simpler** 👀
Just updated the
@astrodotbuild
guide on the
@thekeystatic
docs website!
Added the new "hybrid" output mode, and a walk-through of using Astro's content collections to render Keystatic content 🎉
⚡️ It's been a busy few weeks behind the scenes at Keystatic, lots of *new* features including:
🔲 Support for tables
⚙️ UI Popovers
🖼 Image field
Check out the demo videos and stay up to date here
@simonswiss
@astrodotbuild
You can experiment with this today:
```import { __experimental_mdx_field } from '@keystatic/core/form/fields/markdoc'
```
Then, in your collection/singleton schema:
```
schema: {
content: __experimental_mdx_field({
label: "MDX content",
// ...
})
}
```
Here’s where Keystatic can shine 💡
By putting an intuitive interface in front of the data, Keystatic has made it easy for content people to manage the strings without losing all the benefits of git-based version control that devs really need.
Think:
🔸 personal blogs
🔸 landing pages
🔸 company websites
🔸 design system docs
When housing content in a distributed-source-of-truth (git) makes the most sense.
Keen for the IRL low-down on Keystatic? We're giving a little intro talk at the upcoming React Sydney meet-up.
Stay tuned for the event registration page.
And... we're back, everyone! 👋🥳Join us on the 29th March at 6pm for our first ReactSyd event in a while. Same awesome venue at Dovetail in Surry Hills.
More details to come but, for now, any speakers interested to join the line-up?
Worth noting, this example uses Google Translate to convert the strings... so they may not be perfect.
However, with Keystatic anyone with a GitHub account can fix or improve these entries without having to worry about npm and syntax errors.
You can use it right now (understanding it's __experimental) 💫
API is very similar to the document field, but with new (more capable) "content components" 🎉
Spent the entire Sunday assembling a site with Next.js 13 App dir, Tailwind UI components and Keystatic.
Got two non-developer admins losing their shit on how awesome everything is.
We discuss a content model, minutes later they can yolo content to prod while I create layouts.
It’s designed to be an incremental improvement on how you’d build your website *without* a CMS.
Helping you interact with content & data that’s *part of your source code*.
New theme release - Dawnlight
A beautiful affiliate and blog template. Super easy to use with swappable components / sections, and Keystatic CMS for easy editing
Plus:
- Categories and tags
- Animations
- SEO
- and a bunch more
Check it out below 👇
Last night, I talked about 7 (ish) things I love about
@thekeystatic
after 5 months of using it nearly full-time.
Here's a Twitter version of that talk.
Not posting it as a thread — will just progressively add responses to this initial Tweet.
Let's go!
Keystatic opens up code-based content to people who aren’t technical, or who would just prefer to write & manage content in a UI that looks more like a CMS than IDE.
Think:
🔸 personal blogs
🔸 landing pages
🔸 company websites
🔸 design system docs
When housing content in a distributed-source-of-truth (git) makes the most sense.
Keystatic opens up code-based content to people who aren’t technical, or who would just prefer to write & manage content in a UI that looks more like a CMS than IDE.
Today ten years ago, on the 2nd of July 2013 at 3:01pm AEST,
@JedWatson
made the first commit to the
@KeystoneJS
project, aptly labelled 'Initial commit'. Happy first decade
@KeystoneJS
🎂and thanks to the devs, and our peers, who've gone the journey with us!
Anyone with an existing
@astrodotbuild
website using MDX/Markdoc with content collections interested in me doing a PR adding
@thekeystatic
to the project?
Project repo must be public, for others to learn.
Bonus points if you're using custom components (blocks) in the content.
@logan_liffick
@mattsichterman
Simon (
@simonswiss
) here — my wife and her business partner are not technical at all, but don't need to be.
They enjoy using Keystatic on the Star Athletics website!
Yes, okay, they can tap my shoulder to get dev help, but... they never really need to!