Documentation Getting Started Tutorial #3907
Conversation
… user creation, latest Beta version and shortly the new repeatable fields. Using FoodAdvisor in this tutorial.
…lete with pictures
davidkartuzinski
requested review from
Aurelsicoko,
pierreburgy,
lauriejim,
alexandrebodin,
derrickmehaffy and
soupette
| Path: `~/Desktop/Projects/` | ||
|
|
||
| Use **only one** of the following commands to create a new Strapi project: | ||
|
|
||
| --- | ||
|
|
||
| - (Using **yarn** to install the Strapi project (**recommended**). [Install yarn with these docs](https://yarnpkg.com/lang/en/docs/install/).) | ||
| - (Use **yarn** to install the Strapi project (**recommended**). [Install yarn with these docs](https://yarnpkg.com/lang/en/docs/install/).) |
There was a problem hiding this comment.
We do not need () for all the line
There was a problem hiding this comment.
The corrections have been done.
| ``` | ||
|
|
||
| **or** | ||
|
|
||
| - (Using **npm/npx** to install the Strapi project.) | ||
| - (Use **npm/npx** to install the Strapi project.) |
There was a problem hiding this comment.
All parenthesis () have been removed as per instructions.
| ::: | ||
|
|
||
| You are now ready to create a new **Administrator** and new front-end **User**. | ||
|
|
||
| ## 2. Create an Adminstrator and front-end User | ||
|
|
||
| The first step is to create an **Administrator** (or "root user") for your project. An **Administrator** has all administrator privileges and access rights. You will need to complete the following fields: | ||
| The first step is to create an **Administrator** (or "root user") for your project. An **Administrator** has all administrator privileges and access rights. (You can read more about why **Administrators** and front-end **Users** are separate [here](https://blog.strapi.io/why-we-split-the-management-of-the-admin-users-and-end-users/). |
There was a problem hiding this comment.
Missing ) at the end of the sentence.
There was a problem hiding this comment.
Thank you. Good catch
|
|
||
| You are now at the screen to add fields for your **Restaurant Content Type**. | ||
| - Click on the `String` field | ||
| - In the **Name** field, type `Restaurant_Name`. This field is the name of the restaurant. |
There was a problem hiding this comment.
Why did you change the attribute name?
If you follow FoodAdvisor restaurant model you can use the same attribute name.
As you can see, we never use upper case letter in attributes name (but why not _ if needed)
This comment is for all other attributes.
There was a problem hiding this comment.
All attributes that were named without "_" have been changed.
|
|
||
| The Restaurant Content Type will have a **String** field for the restaurant name, and a **Text** field (with a **WYSIWYG editor**) for the restaurant description. | ||
| - Click on the `String` field | ||
| - In the **Name** field, type `name`. This field is the name of the restaurant. |
There was a problem hiding this comment.
The image here has a blue background (because of your auto insert)
There was a problem hiding this comment.
I fixed this and the user image. Thank you.
| At this point, your project is empty. You need to create a new **Content Type**. | ||
| ### The Restaurant Content Type | ||
|
|
||
| - Go to the **Content Type Builder** plugin, located in the left menu: Under **PLUGINS**: --> **Content Type Builder**. You are now able to see the three available **Content Types**. |
There was a problem hiding this comment.
You never use . at the end of all list lines. Expect here.
There was a problem hiding this comment.
These have all been fixed now.
|
This is now ready to be merged. |
Description of what you did:
This updated Getting Started Tutorial makes the major changes necessary for the new Groups and Repeatable Fields release:
In addition, the tutorial was almost completely rewritten to follow the upcoming style guide, better photos, and a more consistent tone.
My PR is a:
Main update on the:
Manual testing done on the following databases: