Skip to content

Minor reword for the intro of the Templating article #8018

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Jun 13, 2017
Merged

Minor reword for the intro of the Templating article #8018

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 7 additions & 9 deletions templating.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,21 +4,19 @@
Creating and Using Templates
============================

As you know, the :doc:`controller </controller>` is responsible for
handling each request that comes into a Symfony application. In reality,
the controller delegates most of the heavy work to other places so that
code can be tested and reused. When a controller needs to generate HTML,
As explained in :doc:`the previous article </controller>`, controllers are
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO using something like "previous" here suggests that there is a sequence of the articles. But that's not really the case anymore.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right ... except that in this case this article is indeed a part of a series. The Getting Started section groups the basic articles to learn Symfony and they are all linked. You can see that at the bottom of each article, which encourage s you to keep reading the next articles.

responsible for handling each request that comes into a Symfony application and
the usually end up rendering a template to generate the response contents.

In reality, the controller delegates most of the heavy work to other places so
that code can be tested and reused. When a controller needs to generate HTML,
CSS or any other content, it hands the work off to the templating engine.

In this article, you'll learn how to write powerful templates that can be
used to return content to the user, populate email bodies, and more. You'll
learn shortcuts, clever ways to extend templates and how to reuse template
code.

.. note::

How to render templates is covered in the
:ref:`controller <controller-rendering-templates>` article.

.. index::
single: Templating; What is a template?

Expand Down