Merge/maintov3 #506
Merged
Merge/maintov3 #506
Conversation
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
* Add temp workaround for legacy domain Adds a function that checks for node_env and if it's legacy it sets the base key to `/documentation/` else it just sets the base to the vuepress default `/` Also added a replacement for the landing meta-refresh * revert resource center redirection * add resource center link
The word "built-in" is much more common than "inbuilt". Go has packages, and we don't need to refer to them as "packages/modules". Also, add a missing comma.
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
* Change code snippet for service create customisation * Review changes
* Add consistency * Add strapi & prerequisites Markdown containers Note: Using babel-style for plugins declarations as it seems to work better with multiple declarations for vuepress-plugin-container * Use :::strapi and :::prerequisites in existing docs * Add generic callout, tweak strapi & tip callouts, and clean config file * Clean up unused inline styles from Markdown files * Remove 🤓 from Markdown files in strapi callouts as it's now included * Use generic callout for congratulations in QSG * Add api-call, request and response custom containers * Fully redesign style for request & response containers * Use api-callout container on existing documentation * Remove emoji from :::strapi as it's included * Add 'note' custom callout * Add 'important', 'caution' and 'warning' custom callouts In our mind, they are 3 different levels: - important, the less strong - caution, medium importance ( = VuePress's default 'warning') - warning, the strongest ( = VuePress's default 'danger') * Remove important callout & cleanup CSS We decided that we'll go with a unique callout, "caution". The title can still be adjusted when necessary. * Merge branch 'repo/snippets' into repo/vuepress-enhanced * Apply new callouts and minimal tab styles everywhere * Apply minimal tabs to integration guides * Update VuePress to 1.8.2 * Temporarily setting root url (testing Vercel deploy) * Revert "Temporarily setting root url (testing Vercel deploy)" This reverts commit ba7b7d2. * Use code-blocks and code-groups everywhere appropriate * Tweak request/response CSS based on designers feedback * Simplify some wordings in i18n doc * Apply api-call/request/response containers throughout the docs * Tweak request/response CSS for use outside of :::api-call * Update callouts in the user guide * Remove Google Analytics Vuepress plugin and add GTM See [this PR](#380) * Temp remove yarn.lock to fix conflicts * Fix emoji for warning callout * Converting warning to note callout in Templates file * Fix QSG callouts * Add yarn.lock * Remove marketing note at end of 21yunbox hosting guide * Removing GTM script from plugins (it's already in head) * Don't make text prop required in badges as a default is already provided Co-authored-by: Mégane Lacheny <megane.lacheny@strapi.io>
* Remove breaking markdown on laravel page There was a line that broke the layout of the entire page, making everything after the tag be placed inline. By removing this it will all be normal and readable again. * Close a block in the angular documentation * Close a block in the gridsome documentation * Close a block in the 11ty documentation
Fixed the syntax error in line 125.
Fixed a wrong word
from "is uses" to "uses"
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Node v10 is not supported anymore. See https://strapi.io/documentation/developer-docs/latest/setup-deployment-guides/deployment.html Use Node v14 in Standard Environment. See https://cloud.google.com/appengine/docs/standard/nodejs/runtime#node.js-14 Note about Flexible Environment: It will derive the right Node version from package.json. See https://cloud.google.com/appengine/docs/flexible/nodejs/runtime Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
See https://stackoverflow.com/a/67395883/856702 Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
A config file is needed Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
* Update migration-guide-3.4.x-to-3.4.4.md * Update migration-guide-3.4.x-to-3.4.4.md
Update Node version: https://strapi.io/documentation/developer-docs/latest/setup-deployment-guides/installation/cli.html#preparing-the-installation `Node.js (opens new window): only LTS versions are supported (version 12.x minimum). Other versions of Node.js may not be compatible with the latest release of Strapi. The 14.x version is most recommended by Strapi.`
* Fixed grammatical error * Fixed to better match style guide Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
See: https://stackoverflow.com/questions/29939697/npm-build-doesnt-run-the-script-named-build-in-package-json This should also be updated across the docs wherever its found. Maybe I'll go hunting soon if this one gets merged (first time contributor here 😊)
Co-authored-by: DMehaffy <derrickmehaffy@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
servers.js should be server.js
* [v3] CLI Node version reference * make it clear we won't backport node 16 support Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
The mongodb dashboard does not have an 'Overview' section anymore as implied in the strapi mongodb docs. They now have a 'Deployment' section and 'Database Access' has been moved to the 'Security' section. Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
derrickmehaffy
added
source: repo
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/strapijs/documentation/7qDnoQgDaR1dyNak2FE5x7XLXvnd |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
25 participants
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.
Legacy copy of v3 docs