Open source website builder and Webflow alternative. Webstudio is an advanced visual builder that connects to any headless CMS, supports all CSS properties, and can be hosted anywhere, including with us.
TypeScript accessibilityalternativecloudflarecloudflare-workersdesignfreefrontendopen-sourceradix-uireactremixweb-developmentwebflowwebsite-builderwebsite-developmentwebsiteswebstudio
Update links after renaming the repository (#2214)
Oleg Isonen11e078b78f76
diff --git a/packages/cli/Readme.md b/packages/cli/Readme.mdindex 641003b227..6bb0ac2f9a 100644--- a/packages/cli/Readme.md+++ b/packages/cli/Readme.md@@ -48,7 +48,7 @@ The project is scaffolded now. You can run `npm install` and then `npm run dev`- To use a local version of the `cli`, you need to clone the repository.```sh-git clone https://github.com/webstudio-is/webstudio-builder+git clone https://github.com/webstudio-is/webstudio```- Then run `pnpm install` to install all the dependencies.diff --git a/packages/design-system/documentation/figma-design-tokens.md b/packages/design-system/documentation/figma-design-tokens.mdindex 1428eaff4a..9829682219 100644--- a/packages/design-system/documentation/figma-design-tokens.md+++ b/packages/design-system/documentation/figma-design-tokens.md@@ -11,7 +11,7 @@ We use [Tokens Studio for Figma](https://docs.tokens.studio) plugin to sync desi2. Ask Oleg to add you to the `@webstudio-is/core` team if you are not already in it.3. Go to https://github.com/settings/personal-access-tokens/new- Under "Resource owner" choose "webstudio-is" <br /><img src="./assets/1.png" width="349" />- - Under "Repository access" choose `webstudio-is/webstudio-builder` <br /><img src="./assets/2.png" width="514" />+ - Under "Repository access" choose `webstudio-is/webstudio` <br /><img src="./assets/2.png" width="514" />- Set "Repository permissions" / "Contents" to "Read and write", and leave other permissions as is <br /><img src="./assets/3.png" width="806" />- Press "Generate token and request access"- COPY THE TOKEN NOW AND SAVE IT SOMEWHERE SAFE (you won't be able to see it again)@@ -28,7 +28,7 @@ In case sync provider is not configured in the plugin, you can add one using the- Name: up to you- Personal Access Token: token generated using the instructions above-- Repository: `webstudio-is/webstudio-builder`+- Repository: `webstudio-is/webstudio`- Branch: `figma-tokens`- File Path: `packages/design-system/src/__generated__/figma-design-tokens.json`- baseUrl: leave empty@@ -48,7 +48,7 @@ The process:3. Assign some reviewers. Feel free to always assign me (@rpominov). A Pull Request can't be merged without at least one review. Also you might need a developer's help if you've renamed or removed a token that was used in code. <br/><img src="./assets/10.png" width="329" />4. Click "Create pull request" button. (It might be hidden behind "Draft pull request") <br/><img src="./assets/12.png" width="372" />5. In the PR you can already see the changes in the deployed app <br/><img src="./assets/8.png" width="926" />-6. Also, you can see the cnahges in a Storybook using this link https://figma-tokens--638affb61acca1e593c6e558.chromatic.com/ or by going to the bottom of PR page > "Show all checks" > "Storybook Publish: !webstudio-is/webstudio-builder" > "Details" <br/><img src="./assets/9.png" width="924" />+6. Also, you can see the cnahges in a Storybook using this link https://figma-tokens--638affb61acca1e593c6e558.chromatic.com/ or by going to the bottom of PR page > "Show all checks" > "Storybook Publish: !webstudio-is/webstudio" > "Details" <br/><img src="./assets/9.png" width="924" />7. If you see "This branch is out-of-date with the base branch" message at the bottom, this means that when you look at the changes with the links above, you see all your changes applied, but some of the changes made by developers might not be applied. To fix that, click "Update branch" button, but make sure to choose "Update with merge commit" <br/><img src="./assets/7.png" width="1029" />8. Sometimes a visual regression test may fail in the PR. Next sections describes how to fix it.diff --git a/packages/prisma-client/migrations-cli/TROUBLESHOOTING.md b/packages/prisma-client/migrations-cli/TROUBLESHOOTING.mdindex ce8a2ad7f8..63225da383 100644--- a/packages/prisma-client/migrations-cli/TROUBLESHOOTING.md+++ b/packages/prisma-client/migrations-cli/TROUBLESHOOTING.md@@ -1,7 +1,7 @@## A migration failed in PREVIEW, how do I fix the PREVIEW database1. Open a new PR where you'll do the fix-1. Go to https://vercel.com/webstudio-is/webstudio-builder/settings/environment-variables+1. Go to https://vercel.com/webstudio-is/webstudio/settings/environment-variables1. Set APPLY_MIGRATIONS to "true" for your PR's branch1. Fix the failed migration code1. Fix the database mannually if the migration have been applied half-way