After logging in, on the admin-local & admin pages, I see the text “Please wait while we log you in”.
After I refresh, I see the correct admin page

When navigating to /about, and opening the sidebar, I see the "Welcome to Tina, let's set up a form" copy in the sidebar.

Then if I navigate to /home, I still see that same empty state copy in the sidebar.

See gif:

Ultimately, it would be great if we could make it easy to deploy this starter.

It would be great to have a deploy button at the end of this readme.
With the Vercel deploy button you can specify required parameters. We could add NEXT_PUBLIC_REALM_NAME, NEXT_PUBLIC_TINA_CLIENT_ID, and maybe: NEXT_PUBLIC_REDIRECT_URI.

I'm unsure what flow is the best here. The Vercel deploy button requires a git repository URL, which we won't know in advance if the user has already forked the repo.

Also, one thing to note is that the NEXT_PUBLIC_REDIRECT_URI needs to match the app's redirect_uri within the dashboard.

If we cannot work out a good solution with the Vercel deploy button, maybe it's just a matter of adding some extra documentation to the readme.

This could be divided into:

• Add readme instructions for deploying as-is
• Figure out the path for a "slick" deploying experience

See: https://discord.com/channels/835168149439643678/848932514911354880/870269806992035851

CC @damiensedgwick

Got this error

Started Filesystem GraphQL server on port: 4001
Generating Tina config
Cannot find module 'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\.tina\\__generated__\\temp/schema.js'
Require stack:
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql, exiting...
D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:1
Error: Cannot find module 'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\.tina\\__generated__\\temp/schema.js'
Require stack:
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js
- D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\bin\tina-gql
    at compile (D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:275:22)
    at async FSWatcher.<anonymous> (D:\Dev\WebDev\NextJS\tina-cloud-starter\node_modules\tina-graphql-gateway-cli\dist\index.js:511:9) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\dist\\index.js',
    'D:\\Dev\\WebDev\\NextJS\\tina-cloud-starter\\node_modules\\tina-graphql-gateway-cli\\bin\\tina-gql'
  ]
}
Done in 21.12s.

Noticed a few weird issues with the list / nav items

https://www.loom.com/share/c0908295966e4c7fa6de76c783692cbe

• Rearranging the nav-items isn't reflected in the page (until the nav-item itself is edited)

https://www.loom.com/share/7c9387e0483441128ab24b746776f33a

• Nav item is occasionally duplicated.

It may make sense to split this up into separate issues.

We noticed during user sessions that you might sometimes hit the default Next.js 404 page, would be nice if this page could list some valid links from the starter, in order to reduce friction.

Given I'm running the starter locally
When I browse http://localhost:3000/admin/posts/voteForPedro
Then I get the following error message in the browser console

Cannot query field "getCollections" on type "Query". Did you mean "getSections" or "getSection"?

And I can't edit the page

Grab “redirect URI” from window.location instead of an environment variable.

This saves us from having to deploy the app, and set the redirect URI environment variable in 2 separate steps

Editing content on the About page is harder than it should at the moment.
Can we set the page so that you can type in the textarea and hit return here?

Demo: https://www.loom.com/share/589745ee28a24bd7818d1a4b281a33a3

Env: Firefox/macOS

See loom video here:

https://www.loom.com/share/ec514231f121445ab29f0690a3650cd3

After navigating between the home and about pages, I need to hard refresh in order to see the proper content on the page and in Tina.

See video: https://www.loom.com/share/561b1e2621464fff97e744bd23130848

Opening the sidebar to edit on a page (like /about) opens the getGlobalDocument form. It's not immediately obvious what this form is for.

There are a few changes that might help:

1. Default to the getPagesDocument form, as content edits are more frequent than global edits
2. Label each form with a user friendly name
3. Provide help context within each form about their purpose

How do I update site-wide config rather than content files?

Given I'm following the quickstart guide on https://github.com/DirtyF/tina-cloud-starter/blob/main/.env.development
and I set NEXT_PUBLIC_USE_LOCAL_CLIENT=0 in env.development
When I run yarn dev and click the edit button on localhost:3000
Then I do not get Tina Cloud modal auth because https://github.com/tinacms/tina-cloud-starter/blob/main/.env.local.sample#L10 still says to use local client.

Hello,

we are trying to setup inline-editing with TinaCloud and are a bit overwhelmed by the different docs and concepts that exist in the TinaCloud/TinaCMS space. My current understanding is that we need to "switch" to an inlineForm inside the https://tina.io/docs/tina-cloud/client/#formify callback and then also use https://tina.io/docs/tina-cloud/client/#field-customization to return inline-editing fields. Is that the correct approach?

Is there anywhere an example of how to setup TinaCloud including inline-forms?

Thanks in advance.

Given I'm on the homepage
When I edit the text and use backticks and click save
Then I get an error

Warning: Each child in a list should have a unique "key" prop.

Check the render method of `LandingPage`. See https://fb.me/react-warning-keys for more information.
    in Fragment (created by LandingPage)
    in LandingPage (at pages/index.tsx:25)
    in div (at helper-components.tsx:19)
    in div (at helper-components.tsx:18)
    in div (at helper-components.tsx:17)
    in Wrapper (at pages/index.tsx:24)
    in HomePage (at _app.js:24)
    in MyApp
    in ErrorBoundary (created by ReactDevOverlay)
    in ReactDevOverlay (created by Container)
    in Container (created by AppContainer)
    in AppContainer
    in Root react.development.js:315
    React 5
    LandingPage landing-page.tsx:7
    React 13
    renderReactElement index.tsx:518
    doRender index.tsx:777
    _callee2$ index.tsx:413
    Babel 8
    render index.js:452
    <anonyme> next-dev.js:85
    displayContent fouc.js:14

Uncaught (in promise) TypeError: res is undefined
    onSubmit index.js:1040
index.js:1040

We need to display more useful error messages to editors.

Given you're visiting our default demo URL https://tina-cloud-starter-orcin.vercel.app/
When you click on the Edit with Tina button
Then you get a blank page because you can't connect through Tina Cloud

test: https://www.loom.com/share/e4b2655187ee46ca882a38bbd39b63e0

Hi,

we are a holocratic organized software development company and are exploring the usage of tina cloud starter / tina cms as our main "cms engine" for our internal work aswell as the software we are writing for our clients. Unfortunately I have not found some license indication for the code found in this repo, could you kindly clarify if the starter is aswell released under the Apache-2.0 license?

Thanks!

Christoph

NEXT_PUBLIC_REALM_NAME became NEXT_PUBLIC_ORGANIZATION_NAME

Right now, the starter just renders the JSON of the blocks.
It would be nice to have some level of UI, even if it is very minimal

I've seen a few users run into issues with the NEXT_PUBLIC_USE_LOCAL_CLIENT environment variable.

• Some users have not understood that locally, things are talking to the local server, instead of Tina Cloud.
• I've also seen some users try and use NEXT_PUBLIC_USE_LOCAL_CLIENT on their deployed site (which wouldn't work in most cases).

I'm open to other suggestions, but I was wondering if offering multiple scripts might help with the issue:

"scripts": {
    "dev-local": "cross-env NEXT_PUBLIC_USE_LOCAL_CLIENT=1 yarn tina-gql server:start -c \"next dev\"",
    "dev": "yarn tina-gql server:start -c \"next dev\"",
    // ...
}

I could see this offering a few benefits:

• I think it would be unlikely that users would try and use the local client on Vercel / Netlify
• When users enter dev-local, it gives more an indicator that things are running locally (compared to the more tucked away .env approach)
• There are only 2 environment variables to use (client-id / org-id), regardless if you are working locally, or on Vercel/Netlify. If these are eventually generated in a .tina folder with tina init down the road, we can avoid using environment variables altogether.

Given I'm on the Vote for Petro post
When I open the sidebar
Then Author select is empty

Expected: I can change Author from Napolean to Pedro.

1. When creating a new document, it says "choose template", but there are no options

2. It still kicks you over to a new page, but you get a 404.

3. Then things fly off the handle ;)

4. Then the refresh button didn't work (filed new issue for that tinacms/tinacms#2002)

Prevent Media Manager to be shown in the sidebar while we don't support image fields on Tina cloud.

Content security policies provide an extra layer of security for various theoretical vulnerabilities. We could provide a sample CSP implementation in the starter or use the starter to guide documentation on potential CSP approaches.

It would be nice to display some first-level explanations (and point to relevant docs if necessary) when you're in development mode, or through a global option (like help: true)

e.g instead of just displaying a raw JSON or render, give some explanation on how content modeling is done, etc.

If we expect people to follow a scenario, it could also be instructions on the next steps to take, to build an explanation storyline.

If you follow this link you and click edit, your browser tab crashes.

Then you get this:

Also, should we add local dev commands to the readme, to save people from having to read the guide just to test it out? (tagging @jamespohalloran because I think you might have taken this over)

Clicking "Reset" while editing content doesn't reset the rendered content's state.

The body field in the sidebar doesn't seem to do anything on the /admin page.
Can we remove this field? or should we wire up the page to use body?

Previously we had a perfect Lighthouse Score, would be nice if we could get all green on this one too.
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Ftina-cloud-starter-orcin.vercel.app%2F

Navigating around the starter feels clunky. If you click a page it takes a few seconds to load.

https://www.loom.com/share/acfa34eb297e4d2ba40ade1edf71b7a2

The link for the Vercel deploy button in the readme can contain required environment variables, see https://vercel.com/docs/more/deploy-button#required-environment-variables

This should make it a bit more clear which environment variables the starter is expecting to function properly when deployed.

I just created a new repository from the starter template, and I'm getting empty template when trying to add a new blog post:

Expected: I can create a new blog post (bonus: if there's one option per select, then they are the default option selected).

Originally posted by @DirtyF in #153 (comment)

It was brought up that there may be some confusion around the production site not being updated when editing on admin-local. It's a bit different of a flow from the /admin page that might not be clear.

When making a save on admin-local, should we show an alert stating something like:
"The change has been made to the filesystem. Commit/Push this change to git to see this change in production"
(Maybe a bit wordy)

Context

With Next.js default CRA you can't run two server on the same port, if you try to launch next in two terminals, you get an error: Port 3000 already in use and the command exits.

Issue

Given you're already running another project on port 3000
When you do use tina cloud starter default yarn dev command
Then the output tells you the site is accessible on http://localhost:3000
And when you click you land on the other project already running on 3000
And you don't know if tina cloud starter runs on another port.

Expected

When the port is already in use, then the command exits and warns you about it.

Given I'm running yarn dev on the current main branch locally
When I create a new document for the blog
Then alert says Document created
And created Markdown file is empty
And I get an error data is null when refreshing the blog

Demo: https://www.loom.com/share/6f9782941958419e9e3faa549e77a6a5

Sorry to waste anyone's time but I have spent all day trying to integrate Tina Cloud and am hitting some issues.

The first thing which really confused me and might want be clarified is when you have not got a query prop on every page an exception gets thrown in the Inner component when useGraphqlForms is called which is slightly obscure.

I also cannot seem to switch to using Tina Cloud. I am getting the error ReferenceError: localStorage is not defined and I understand why the token code would use that when a user is editing but I am not sure how to populate the token when next builds.

Also I notice the usage of createLocalClient for example at https://github.com/tinacms/tina-cloud-starter/blob/main/pages/posts/%5Bfilename%5D.tsx#L41 and https://github.com/tinacms/tina-cloud-starter/blob/main/pages/index.tsx#L45 which ignores the NEXT_PUBLIC_USE_LOCAL_CLIENT option. Should this not just be createClient()?

Sorry if I have misunderstood how this works and thanks for your time.

Replace references to Realm name in environment variables, matching README snippets, and code to Organization ID.

At the same time, it would be good to make the environment variable to be consistent with the existing Client ID env var by prefixing it with TINA.

NEXT_PUBLIC_REALM_NAME => NEXT_PUBLIC_TINA_ORGANIZATION_ID

The starter is built to show folks how they can use Tina without it getting in the way of their site. We could show folks how this plays out with the Lighthouse scores of the starter.

Longer term, it would be interesting to view the impact of changes on Lighthouse scores as a check during Pull Requests.

Now that we provide an admin url in the dashboard, can we remove the "edit this site" link from the sidebar of the starter?

It's important that we keep a separation of concerns (no Tina code in your prod site) and that link sends the wrong message

Some images in public/uploads don't seem to be needed for the sample content.