-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Fix template docs for v4 #665
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
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/strapijs/documentation/Hy1NqYVCvZNYWrdGm8gq6hKLEky6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm (minus TW)
|
Thank you for updating it, @remidej ! |
|
Also, we'll try to make sure this document is properly included in the TOC. For now, documentation for templates is only accessible by search. |
* In our introductions, bullet lists are usually reserved for items that will be described in sections of the current document (they act like a mini-TOC (table of content) * Avoid using "you" when not necessary (see our https://handbook.strapi.io/user-success-manual/12-rules-of-technical-writing)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you again @remidej for this update!
I've done a thorough technical writing review of this file.
You will find:
- suggestions that you can directly apply here on GitHub
- content that I directly modified in subsequent commits (as I can't comment on lines that weren't modified by the PR)
Once suggestions are applied, we'll have to rethink the structure a bit as it's missing a clear path.
We could have something like:
- using a template
- creating a template:
- requirements
- intro with the 3 requirements (template folder, package.json, template.json)
- template folder requirements (allowed files)
- template.json requirements
- package creation and publication on npm
- requirements
We can discuss it further if you need help.
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
…n/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…n/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…n/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…n/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…n/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
…n/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
|
Hi @samuel-2018, and thank you for your question. It has been deprioritized for now. In the meantime, you can still visit the temporary URL deployed with this PR here, and I can check with the team if we have the resources to publish a final version before the end of the quarter. Hope this helps :) |
docs/developer-docs/latest/setup-deployment-guides/installation/templates.md
Outdated
Show resolved
Hide resolved
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Thanks for the updates, @gpene. Looks good to me, I'd suggest a few style-related updates:
|
* Ignore me, just testing something (#1377) * fix issue #1321 * fix logger middleware example. closes #1360 * fixes #1301 * Add missing parentheses Parentheses are missing from some of the examples for v4. * Added --no-cache and --production flags for docker * update google-app-engine.md * Fix/possible null returned (#1340) * Fixing possible bug/error Removed all the env helper function usages from anywhere but config file, per laravel documentation. ref: https://laravel.com/docs/9.x/helpers#method-env If you execute the config:cache command during your deployment process, you should be sure that you are only calling the env function from within your configuration files. Once the configuration has been cached, the .env file will not be loaded and all calls to the env function will return null. * Refactored config file example - Removed unused entries from config file. - Removed redundant comments, since it offers no additional information. * Copy edit Co-authored-by: Gabriel <83644514+gpene@users.noreply.github.com> * Remove the duplicated `of` in the Troubleshooting document (#1392) There is a useless `of` in the part `typical count of of component entries` * Add possible Variable for user-permission emails found this only in an issue on github: strapi/strapi#12771 Would have saved me some time if I had found it earlier here :) * Remove reference to Hobby Dev plan of Heroku Postgres add-on. * Fix template docs for v4 (#665) * Fix template docs for v4 * Reword introduction * In our introductions, bullet lists are usually reserved for items that will be described in sections of the current document (they act like a mini-TOC (table of content) * Avoid using "you" when not necessary (see our https://handbook.strapi.io/user-success-manual/12-rules-of-technical-writing) * Avoid overusing you. Write procedure-based instructions. * Neutral tone + use of `(e.g. )` to list examples * Use bullet points + `e.g.` + code blocks (for a prettier look) * Avoid overusing you + example format consistent with the whole documentation * Include important information in a caution callout if it could break the app * Add link to file structure section * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Apply piwi feedback * Update docs/developer-docs/latest/setup-deployment-guides/installation/templates.md * rework structure * fix link * typo fix * feedback updates Co-authored-by: Pierre Wizla <pwizla+github@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> Co-authored-by: Gabriel <83644514+gpene@users.noreply.github.com> * add install command (#1393) Co-authored-by: DMehaffy <derrickmehaffy@gmail.com> Co-authored-by: Shaun Brown <shaun.brown@strapi.io> Co-authored-by: Keit Oliveira <keit.oliveira@icloud.com> Co-authored-by: Simen Daehlin <sdaehlin@luno.com> Co-authored-by: Yoram Swiers <yoram@swiers.be> Co-authored-by: Shaun Brown <97027841+StrapiShaun@users.noreply.github.com> Co-authored-by: Nika Jorjoliani <nikajorjika1993@gmail.com> Co-authored-by: Gabriel <83644514+gpene@users.noreply.github.com> Co-authored-by: RainX <101971+rainx@users.noreply.github.com> Co-authored-by: michaelroth-xx <62610391+michaelroth-xx@users.noreply.github.com> Co-authored-by: Alan Carrie <alanjcarrie@gmail.com> Co-authored-by: Rémi de Juvigny <8087692+remidej@users.noreply.github.com>
Why is it needed?
v4 handles templates differently than v3. On v3, we used Github to host them. Now they are published as npm packages.
Some features were also removed on v4:
template.jsconfig feature was also removed. That's because templates can now be versioned with npm. So there's no need to dynamically generate the config, users should instead create a new template version instead.