Skip to content

Commit 5d50467

Browse files
committed
renaming sub-templates to partials to be consistent with Mustache's naming conventions
1 parent db9a9e2 commit 5d50467

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# CakePan - CakePHP Mustache Support (CakePHP v2.x)
22

3-
CakePan is a CakePHP view helper that renders Mustache templates. It will also load and process sub-templates!
3+
CakePan is a CakePHP view helper that renders Mustache templates. It will also load and process partials!
44

55
### Why use Mustache templates in CakePHP?
66
<strong>Portability and scalability!</strong> If you have an app that uses lots of front-end coding, you only have to write your templates once. Mustache templates can be rendered in PHP, Javascript, Ruby, Scala, even C++! If you want to move to or from some other framework (Rails, Grails, Lithium etc.), you can be sure that your views and design won't have to be re-built.
@@ -54,9 +54,9 @@ All the variable set by the controller are available, and merged with values pas
5454

5555

5656

57-
### Sub-templates
57+
### Using Partials
5858

59-
Sub-templates should follow the same naming convention. Mustache will pass the variables to the sub-template in the context that it's called. For example, a nested template for a blog `post` with `comments` might look like:
59+
Partials should follow the same naming convention. Mustache will pass the variables to the partial in the context that it's called. For example, a nested template for a blog `post` with `comments` might look like:
6060

6161
/app/View/Elements/posts/post.mustache:
6262

0 commit comments

Comments
 (0)