Add an example of seeding the first user

[zizzfizzix]

trafficstars

Add documentation to seed the first user during development for people frequently resetting their database, so they don't have to set up a user every time.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: d576ec536aae5d7d6ebe0c4de1daa6a400f601e0

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[bot]]

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

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Oct 10, 2022 at 10:55PM (UTC)

[codesandbox-ci[bot]]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d576ec536aae5d7d6ebe0c4de1daa6a400f601e0:

Sandbox	Source
@keystone-6/sandbox	Configuration

[dcousens]

Thinking about this @zizzfizzix, I think we should do everything we can to show better data seeding practices in the examples rather than in the documentation. If users are trying the project for the first time, we don't want to introduce any confusion about whether they need to seed data or not.

Thanks for the contribution though, as someone who frequently boots up the examples, this is my daily pain.