feat: add support for vercel visual editing - #233
Open
mwickett wants to merge 1 commit into
Open
Conversation
🦋 Changeset detectedLatest commit: 79ade70 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
📦 Canary Packages PublishedLatest commit: 79ade70 Published 2 packages@hashicorp/platform-cli@2.7.3-canary-2023513203633@hashicorp/platform-cms@0.5.0-canary-2023513203633 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎟️ Asana Task
Description
This adds necessary headers to our graphql requests to DatoCMS to enable the visual editing feature (Vercel Docs / Dato Docs)
This is similar to https://github.com/hashicorp/web/pull/455/files
Note: before this merges (really before the version is bumped on consuming projects), each Vercel project that uses Dato will need to have a
HASHI_DATO_PROJECTenv variable added with the slug of the Dato URL. For us, possible values include:hashicorpio-marketing-siteshashiconfhashidaysinternal-wwwhow-hashicorp-worksPR Checklist 🚀