Merge pull request #543 from james0r/patch-1

Update blog-templates.md

Author: AugustMiller

docs/getting-started-tutorial/build/blog-templates.md

@@ -120,7 +120,7 @@ If you were to go back into the control panel and create some more posts, you co
 
 #### Feature Image
 
-Let’s output the image we attached via the “Feature Image” asset field. That field had a handle of `featureImage`, so it will be available on the `entry` variable as `entry.featureImage`, just like the title was:
+Let’s output the image we attached via [the “Feature Image” asset field](../configure/resources.md#feature-image). That field had a handle of `featureImage`, so it will be available on the `entry` variable as `entry.featureImage`, just like the title was:
 
 ```twig{4,15-19}
 {% extends '_layout' %}
@@ -187,15 +187,15 @@ If the lack of styles makes it difficult to evaluate whether you are staying on
 
 #### Topics
 
-Let’s add some more metadata to the top of our post. Our content model included a category field called **Topics**, which we can access in a really similar way to the feature image!
+Let’s add some more metadata to the top of our post. Our content model included a [category field](../configure/resources.md#categoriestopics) called **Topics**, which we can access in a really similar way to the feature image!
 
 Just below the existing `set` tag, add another one to fetch the attached categories:
 
 ```twig{3-4}
 {% set featureImage = entry.featureImage.one() %}
 
 {# Load attached topics: #}
-{% set topics = entry.topics.all() %}
+{% set topics = entry.postCategories.all() %}
 ```
 
 Because we’re allowing authors to attach multiple topics to a post, we’ve used `.all()` to fetch _all_ of them, instead of just _one_. This is important, because we will treat `topics` (plural) a little bit differently from `featureImage` (singular).
@@ -239,7 +239,7 @@ If you pasted this into `templates/blog/_entry.twig` and the indentation got mes
 
 #### Post Content
 
-Let’s output the post content stored in our Matrix field. This process starts in a familiar way:
+Let’s output the [post content](../configure/resources.md#post-content) stored in our Matrix field. This process starts in a familiar way:
 
 1. Load matrix blocks via the `postContent` field handle and store them in a variable;
 1. Loop over those blocks with a `{% for %}` tag;

docs/getting-started-tutorial/build/optimization.md

@@ -10,7 +10,7 @@ We have a host of other ideas for [next steps](../more/README.md) if you would p
 
 When building the blog and topic index pages, there was a lot of repeated code involved with outputting the post previews. Twig’s `include` tag can help us reduce that repetition by extracting it into a separate template, and referencing it in both places.
 
-We’ll start by taking the entire `for` loop from `templates/blog/_index.twig` and moving it to a new file, `templates/blog/_feed.twig`:
+We’ll start by taking the entire `for` loop from `templates/blog/index.twig` and moving it to a new file, `templates/blog/_feed.twig`:
 
 ```twig
 {% for post in posts %}
@@ -34,7 +34,7 @@ We’ll start by taking the entire `for` loop from `templates/blog/_index.twig`
 {% endfor %}
 ```
 
-In place of that block of code in `templates/blog/_index.twig`, `include` the new template (then make the same change to `templates/blog/_topic.twig`):
+In place of that block of code in `templates/blog/index.twig`, `include` the new template (then make the same change to `templates/blog/_topic.twig`):
 
 ```twig
 {% include 'blog/_feed' %}

docs/getting-started-tutorial/configure/resources.md

@@ -76,10 +76,10 @@ Assets are organized into _volumes_, which sit on top of a _filesystem_. Filesys
 
 We’ll create a local Asset Volume within the web root for blog post images:
 
-1. In the control panel, navigate to **Settings** → **Assets**.
-1. Click **+ New volume**.
-1. Enter “Images” in the **Name** field <Poi label="A" target="newVolume" id="volumeName" />.
-1. Click the **Asset Filesystem** menu <Poi label="C" target="newVolume" id="volumeFsMenu" /> and select **Create a new filesystem…**
+1. In the control panel, navigate to **Settings** → **Assets**;
+1. Click **+ New volume**;
+1. Enter “Images” in the **Name** field <Poi label="A" target="newVolume" id="volumeName" />;
+1. Click the **Asset Filesystem** menu <Poi label="C" target="newVolume" id="volumeFsMenu" /> and select **Create a new filesystem…**;
 
     Within the slideout that opens, provide these settings:
 
@@ -116,12 +116,12 @@ The second resource we need to create is a group for our blog’s _categories_.
 <img src="../images/new-category-group.png" alt="Screenshot of new category group fields" />
 </BrowserShot>
 
-1. Navigate to **Settings** and choose **Categories**.
-1. Choose **+ New category group**.
-1. In the **Name** <Poi label="A" target="newCategoryGroup" id="name" /> field, enter “Topics”.
-1. In the **Max Levels** <Poi label="C" target="newCategoryGroup" id="levels" /> field, enter `1`.
-1. Set the **Category URI Format** <Poi label="D" target="newCategoryGroup" id="uri" /> to `blog/topic/{slug}`.
-1. Set the **Template** <Poi label="E" target="newCategoryGroup" id="template" /> to `blog/_topic`.
+1. Navigate to **Settings** and choose **Categories**;
+1. Choose **+ New category group**;
+1. In the **Name** <Poi label="A" target="newCategoryGroup" id="name" /> field, enter “Topics”;
+1. In the **Max Levels** <Poi label="C" target="newCategoryGroup" id="levels" /> field, enter `1`;
+1. Set the **Category URI Format** <Poi label="D" target="newCategoryGroup" id="uri" /> to `blog/topic/{slug}`;
+1. Set the **Template** <Poi label="E" target="newCategoryGroup" id="template" /> to `blog/_topic`;
 1. **Save** <Poi label="F" target="newCategoryGroup" id="save" /> the category group.
 
 ## Custom Fields
@@ -143,7 +143,7 @@ The post summary will be entered in a _plain text_ field.
 
 1. Click **+ New Field**;
 1. Enter “Summary” into the **Name** field;
-1. Enter “Summaries should be one or two sentences.” in the **Default Instructions** field to give authors a hint about the field’s intended usage.
+1. Enter “Summaries should be one or two sentences.” in the **Default Instructions** field to give authors a hint about the field’s intended usage;
 1. Enable **Allow line breaks**;
 1. Set the revealed **Initial Rows** field to `1`;
 1. Save the field.
@@ -173,7 +173,7 @@ Posts’ primary images will be added to an _asset_ field.
 </BrowserShot>
 
 1. Click **+ New Field**;
-1. Enter “Feature Image” into the **Name** <Poi label="A" target="newAssetField" id="name" /> field;
+1. Enter “Feature Image” into the **Name** <Poi label="A" target="newAssetField" id="name" /> field (and note that Craft automatically generates a **Handle** of `featureImage`);
 1. Select **Assets** from the **Field Type** <Poi label="C" target="newAssetField" id="type" /> menu—the rest of the page will be updated with options specific to asset fields;
 1. Tick **Restrict assets to a single location?** <Poi label="D" target="newAssetField" id="restrict" />;
 1. Select the **Images** volume from the revealed **Asset Location** <Poi label="E" target="newAssetField" id="location" /> menu;
@@ -188,7 +188,7 @@ Posts’ primary images will be added to an _asset_ field.
 Our _topics_ field only needs a couple of options:
 
 1. Click **+ New Field**;
-1. Enter “Post Categories” into the **Name** field;
+1. Enter “Post Categories” into the **Name** field (and note that Craft automatically generates a **Handle** of `postCategories`);
 1. Choose “Categories” from the **Field Type** menu—the rest of the page will be updated with options specific to categories fields;
 1. Choose “Topics” from the **Source** menu (it will probably be selected, already);
 1. Save the field.
@@ -220,7 +220,7 @@ Matrix fields are inherently a bit more complex than other field types, because
 </BrowserShot>
 
 1. Click **+ New Field**;
-1. Enter “Post Content” in the **Name** <Poi label="A" target="newMatrixField" id="name" /> field;
+1. Enter “Post Content” in the **Name** <Poi label="A" target="newMatrixField" id="name" /> field (and note that Craft automatically generates a **Handle** of `postContent`);
 1. Choose “Matrix” from the **Field Type** <Poi label="C" target="newMatrixField" id="type" /> menu—the rest of the page will be updated with options specific to matrix fields;
 1. Within the **Configuration** <Poi label="D" target="newMatrixField" id="config" /> space, use the **+ New block type**  button to create two _block types_: