Closed logan-anderson closed 3 years ago
Latest commit: 4a7cbee33ebab19d69798496f43ab934543fbb8b
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.
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
An alternative version:
Setting up Tina...
Installing dependencies... ✅
Adding a content folder... ✅
Tina setup ✅
Before you get started:
1. Add the following scripts to your package.json:
"dev": "yarn tina-gql server:start -c \"next dev\"",
"build": "yarn tina-gql server:start -c \"next build\"",
"start": "yarn tina-gql server:start -c \"next start\""
2. Check the page and the post created at:
/Users/logananderson-forestry-mac/dev/tinacms/tina-graphql-gateway/apps/tmp/pages/demo/blog/[filename].tsx
/Users/logananderson-forestry-mac/dev/tinacms/tina-graphql-gateway/apps/tmp/content/posts/HelloWorld.md
Enjoy Tina!
@jeffsee55 is there anyway we could do a canary release so we can start doing some user testing? or should we just merge this ?
Feel free to do a canary, I've outline the steps here https://github.com/tinacms/tina-graphql-gateway/blob/main/CONTRIBUTING.md#creating-a-beta-release...
having said that I don't care either way, we haven't announced this feature publicly
I think merging it is fine for now
New output of init command Fixes https://github.com/tinacms/tina-graphql-gateway/issues/288
@mitchmac Does anything else need to be removed?