docs: add section about disabling indexing

[florian-lefebvre]

Following #486

cc @simonswiss

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6fd7674

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
keystar-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 23, 2023 11:38am
keystatic	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 23, 2023 11:38am
keystatic-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 23, 2023 11:38am

[simonswiss]

Hey @florian-lefebvre ✨

I know I asked you to open this PR in the Astro guide, but I sort of changed my mind on where this information should belong.

Last week and the conversations with the Astro docs team led us to a huge re-think of how we should approach guides, particularly framework integration guides.

After a major rewrite of this guide with a sharp focus on avoiding any "side quests", I can't help but feel that this section about shutting down /keystatic routes in production should belong somewhere else. It just snaps the user out of the procedural, step by step installation.

I see this info in something like a recipe or a tutorial, for a specific need. It's great content and very useful when you need it, but IMO, it does not belong in the "get setup with Astro" guide itself.

I like what the Astro docs do with recipes:

If you don't mind, I'll try to stand a "Recipes" section in the nav tomorrow and make your contribution one of these guides.

I think it will work better that way.

Sorry about the flip-flopping around 😅 I've become very passionate about keeping integration guides as short and to-the-point as possible, and move all tangential content to another place.

Let me know what you think!

[simonswiss]

Update: I've tried two things: a blog post, and a new recipes section:

The blog post is cool because it has your author link in it that you can point to your portfolio or other link, and it's nice to have community contributions in there. But if we go that route, we'll need to revisit the blog index copy that mentions news and updates from the Keystatic team.

I'll push this commit so you can have a look at both, and we can all decide what the best implementation is.

[florian-lefebvre]

Hey! No worries, I also think it makes more sense to get it out of the integration guide. I think recipes are more relevant so that it's not mixed with "official" posts from the team.

Regarding the author link, one idea could be to add contributors to recipes like on nuxt v2 section (scroll all the way down on this page).

Wdyt?

[simonswiss]

Gotta go to bed now, but I've pushed my code in this branch (did not have access to push in your fork): #579

That PR contains all the commit history of this PR here.

I also think the recipes is a better place. Right now all docs pages are the same content type in Keystatic, so adding an author would mean every docs page has an author field.

I think we can add a contributed by aside callout at the top of the recipe for that effect 👍

Feel free to make suggestions, and let's try to get this merged tomorrow!