Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🚀 Production hotfix: Fix missing routes code example #1312

Merged
merged 365 commits into from
Dec 1, 2022
Merged

Conversation

pwizla
Copy link
Collaborator

@pwizla pwizla commented Dec 1, 2022

Properly opens a code block, so that now both JS and TS versions are rendered.

stb13579 and others added 30 commits September 22, 2022 17:44
* Updated Heroku deployment documentation

Added a line to recommend WSL for windows users on step 5 of the postgres setup, as that was something that would have saved me some time while following the guide.

Also fixed a numbering error

* Update docs/developer-docs/latest/setup-deployment-guides/deployment/hosting-guides/heroku.md

Co-authored-by: Pierre Wizla <[email protected]>

* Added multiple options for windows users on step 5

* Remove WSL suggestion and format as a tip

Co-authored-by: Pierre Wizla <[email protected]>
* Update admin-customization.md for plugin translation

Add instructions to admin-customization.md for extending a plugin's translations, which requires prefixing the key/value pair (declared in the plugin's translation file) with the plugin's name, for example `"content-type-builder.plugin.name": "Constructeur de Type-Contenu"` in order to translate the `plugin.name` key declared in `content-type-builder` plugin.
This wasn't made clear by the documentation previously, since even for default plugins (such as content-type-builder) some fields are not translatable with the default method because they are declared independently in the plugin's files. I couldn't find any reference in the docs to the fact the plugin's name needed to be added as a prefix in order to extend a plugin's key.

* Update docs/developer-docs/latest/development/admin-customization.md

Co-authored-by: Pierre Wizla <[email protected]>

Co-authored-by: Pierre Wizla <[email protected]>
* Support HTML in SidebarGroup title

* Add hotjar

* Delete SidebarGroup.vue
Latest Windows OS version is Windows 11
Windows Desktop Recommended Version Correction
fix: the youtube link for video demo is outdated
Add GraphQL Plugin config to TypeScript example similar to JavaScript
I follow the AWS guidelines for a fresh start. When I came to the pm2 step, I noticed some missing environment variables in ecosystem.config.js.
This reverts commit 9a9dffd, reversing
changes made to 318b284.
stb13579 and others added 19 commits November 30, 2022 07:45
Update database connection properties
This reverts commit cf39be4874a765f97b0e6604c1847694ecbf6d38.
* Update LTS version for node to include v18

* Update docs/developer-docs/latest/developer-resources/cli/snippets/installation-prerequisites.md

Co-authored-by: Pierre Wizla <[email protected]>

Co-authored-by: Pierre Wizla <[email protected]>
Update getting started guide to fit new strapi response format and describe new Nuxt 3 features.
* Fix missing opening tag for the code block

* Fix missing file prefix
@pwizla pwizla self-assigned this Dec 1, 2022
@vercel
Copy link

vercel bot commented Dec 1, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
documentation 🔄 Building (Inspect) Dec 1, 2022 at 5:33PM (UTC)
documentation-docu-mvp ❌ Failed (Inspect) Dec 1, 2022 at 5:33PM (UTC)

@pwizla pwizla merged commit c692693 into production Dec 1, 2022
@pwizla pwizla added source: Dev Docs PRs/issues targeting the Developer Docs pr: fix Used on the docs repo for anything that is not "new" or "updated" content: chore, typos, fixes, etc. internal PRs created by the Strapi core team target: v4 Documentation PRs/issues targeting content from docs.strapi.io (main branch). size: small If the PR includes only 1 file with <10 lines of text or a small code fix labels Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal PRs created by the Strapi core team pr: fix Used on the docs repo for anything that is not "new" or "updated" content: chore, typos, fixes, etc. size: small If the PR includes only 1 file with <10 lines of text or a small code fix source: Dev Docs PRs/issues targeting the Developer Docs target: v4 Documentation PRs/issues targeting content from docs.strapi.io (main branch).
Projects
None yet
Development

Successfully merging this pull request may close these issues.