-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AstroJS] Keystatic doesn't show files from Content Collection #519
Comments
It doesn't support slugs with several variables yet, see #340 |
Thanks for the info. |
Confirming what @florian-lefebvre said, and also noting that you're specifically using Astro's convention for different languages (ref https://docs.astro.build/en/recipes/i18n/) I've been thinking about adding a feature specific to content translation that would show you a language dropdown for each entry in the UI, rather than showing you all the entries in one list and treating We'll have a look at it this week and get back to you with when we can add support for this. |
ADMIN UI still doesn't see the posts, even with path: 'src/content/blog/**' in path |
@JedWatson Do you already have an estimated time when this feature will be available in production? Can't wait to try your admin on real projects. :) |
Collating this in #1080 |
I have AstroJS project, and I added Keystatic.
I have several pages in
src/content
folder, and it works in Astro:File
src/content/config.ts
:File
keystatic.config.ts
:Example of mdoc file:
src/content/docs/en/about.mdoc
I go to my Keystatic admin.
What I see:
No results No items matching "" were found.
What I expected to see: the list of my mdoc files form existing AstroJS project.
Node 18.17.0
MacOS Catalina
"dependencies": {
"@astrojs/markdoc": "^0.4.4",
"@astrojs/node": "^5.3.2",
"@astrojs/react": "^2.2.1",
"@keystatic/astro": "^0.0.8",
"@keystatic/core": "^0.0.114",
"@types/react": "^18.2.18",
"@types/react-dom": "^18.2.7",
"accept-language": "^3.0.18",
"astro": "^2.10.3",
"react": "^18.2.0",
"react-dom": "^18.2.0"
}
The text was updated successfully, but these errors were encountered: