jekyll 1.0.0.beta3 → 1.0.0.beta4

data/site/_posts/2012-07-01-permalinks.md

@@ -5,8 +5,15 @@ prev_section: templates
 next_section: pagination
 ---
 
-Jekyll supports a flexible way to build your site’s URLs. You can
-specify the permalinks for your site through the [Configuration](../configuration) or on the [YAML Front Matter](../frontmatter) for each post. You’re free to choose one of the built-in styles to create your links or craft your own. The default style is always `date`.
+Jekyll supports a flexible way to build your site’s URLs. You can specify the
+permalinks for your site through the [Configuration](../configuration) or in the
+[YAML Front Matter](../frontmatter) for each post. You’re free to choose one of
+the built-in styles to create your links or craft your own. The default style is
+`date`.
+
+Permalinks are constructed by creating a template URL where dynamic elements are
+represented by colon-prefixed keywords. For example, the default `date`
+permalink is defined as `/:categories/:year/:month/:day/:title.html`.
 
 ## Template variables
 
@@ -23,7 +30,7 @@ specify the permalinks for your site through the [Configuration](../configuratio
         <p><code>year</code></p>
       </td>
       <td>
-        <p>Year from the post’s filename</p>
+        <p>Year from the Post’s filename</p>
       </td>
     </tr>
     <tr>
@@ -31,47 +38,51 @@ specify the permalinks for your site through the [Configuration](../configuratio
         <p><code>month</code></p>
       </td>
       <td>
-        <p>Month from the post’s filename</p>
+        <p>Month from the Post’s filename</p>
       </td>
     </tr>
     <tr>
       <td>
-        <p><code>day</code></p>
+        <p><code>i_month</code></p>
       </td>
       <td>
-        <p>Day from the post’s filename</p>
+        <p>Month from the Post’s filename without leading zeros.</p>
       </td>
     </tr>
     <tr>
       <td>
-        <p><code>title</code></p>
+        <p><code>day</code></p>
       </td>
       <td>
-        <p>Title from the post’s filename</p>
+        <p>Day from the Post’s filename</p>
       </td>
     </tr>
     <tr>
       <td>
-        <p><code>categories</code></p>
+        <p><code>i_day</code></p>
       </td>
       <td>
-        <p>The specified categories for this post. Jekyll automatically parses out double slashes in the URLs, so if no categories are present, it basically ignores this.</p>
+        <p>Day from the Post’s filename without leading zeros.</p>
       </td>
     </tr>
     <tr>
       <td>
-        <p><code>i_month</code></p>
+        <p><code>title</code></p>
       </td>
       <td>
-        <p> Month from the post’s filename without leading zeros.</p>
+        <p>Title from the Post’s filename</p>
       </td>
     </tr>
     <tr>
       <td>
-        <p><code>i_day</code></p>
+        <p><code>categories</code></p>
       </td>
       <td>
-        <p>Day from the post’s filename without leading zeros.</p>
+        <p>
+          The specified categories for this Post. Jekyll automatically parses
+          out double slashes in the URLs, so if no categories are present, it
+          will ignore this.
+        </p>
       </td>
     </tr>
   </tbody>
@@ -160,4 +171,3 @@ Given a post named: `/2009-04-29-slap-chop.textile`
     </tr>
   </tbody>
 </table>
-

data/site/_posts/2012-07-01-plugins.md

@@ -6,19 +6,27 @@ next_section: extras
 ---
 
 Jekyll has a plugin system with hooks that allow you to create custom generated
-content specific to your site. You can run custom code for your site
-without having to modify the Jekyll source itself.
+content specific to your site. You can run custom code for your site without
+having to modify the Jekyll source itself.
 
 <div class="note info">
   <h5>Plugins on GitHub Pages</h5>
-  <p>GitHub Pages are powered by Jekyll, however all Pages sites are generated using the <code>--safe</code> option to disable custom plugins for security reasons. Unfortunately, this means your plugins won’t work if you’re deploying to GitHub Pages.</p>
+  <p>
+    <a href="http://pages.github.com">GitHub Pages</a> is powered by Jekyll,
+    however all Pages sites are generated using the <code>--safe</code> option
+    to disable custom plugins for security reasons. Unfortunately, this means
+    your plugins won’t work if you’re deploying to GitHub Pages.<br><br>
+    You can still use GitHub Pages to publish your site, but you'll need to
+    convert the site locally and push the generated static files to your GitHub
+    repository instead of the Jekyll source files.
+  </p>
 </div>
 
 ## Installing a plugin
 
-In your site source root, make a `_plugins` directory. Place your plugins
-here. Any file ending in `*.rb` inside this directory will be required
-when Jekyll generates your site.
+In your site source root, make a `_plugins` directory. Place your plugins here.
+Any file ending in `*.rb` inside this directory will be loaded before Jekyll
+generates your site.
 
 In general, plugins you make will fall into one of three categories:
 
@@ -28,9 +36,8 @@ In general, plugins you make will fall into one of three categories:
 
 ## Generators
 
-You can create a generator when you need Jekyll to create additional
-content based on your own rules. For example, a generator might look
-like this:
+You can create a generator when you need Jekyll to create additional content
+based on your own rules. For example, a generator might look like this:
 
 {% highlight ruby %}
 module Jekyll
@@ -68,8 +75,8 @@ end
 {% endhighlight %}
 
 In this example, our generator will create a series of files under the
-`categories` directory for each category, listing the posts in each
-category using the `category_index.html` layout.
+`categories` directory for each category, listing the posts in each category
+using the `category_index.html` layout.
 
 Generators are only required to implement one method:
 
@@ -94,18 +101,20 @@ Generators are only required to implement one method:
 
 ## Converters
 
-If you have a new markup language you’d like to include in your site,
-you can include it by implementing your own converter. Both the markdown
-and textile markup languages are implemented using this method.
+If you have a new markup language you’d like to use with your site, you can
+include it by implementing your own converter. Both the Markdown and Textile
+markup languages are implemented using this method.
 
 <div class="note info">
   <h5>Remember your YAML front-matter</h5>
-  <p>Jekyll will only convert files that have a YAML header at
-the top, even for converters you add using a plugin. If there is no YAML header, Jekyll will ignore the file and not send it through the converter.</p>
+  <p>
+    Jekyll will only convert files that have a YAML header at the top, even for
+    converters you add using a plugin.
+  </p>
 </div>
 
-Below is a converter that will take all posts ending in .upcase and
-process them using the UpcaseConverter:
+Below is a converter that will take all posts ending in `.upcase` and process
+them using the `UpcaseConverter`:
 
 {% highlight ruby %}
 module Jekyll
@@ -114,7 +123,7 @@ module Jekyll
     priority :low
 
     def matches(ext)
-      ext =~ /upcase/i
+      ext =~ /^\.upcase$/i
     end
 
     def output_ext(ext)
@@ -142,37 +151,46 @@ Converters should implement at a minimum 3 methods:
       <td>
         <p><code>matches</code></p>
       </td>
-      <td>
-        <p>Called to determine whether the specific converter will
-run on the page.</p>
-      </td>
+      <td><p>
+        Does the given extension match this converter's list of acceptable
+        extensions? Takes one argument: the file's extension (including the
+        dot). Must return <code>true</code> if it matches, <code>false</code>
+        otherwise.
+      </p></td>
     </tr>
     <tr>
       <td>
         <p><code>output_ext</code></p>
       </td>
-      <td>
-        <p>The extension of the outputted file, usually this will be <code>.html</code></p>
-      </td>
+      <td><p>
+        The extension to be given to the output file (including the dot).
+        Usually this will be <code>".html"</code>.
+      </p></td>
     </tr>
     <tr>
       <td>
         <p><code>convert</code></p>
       </td>
-      <td>
-        <p>Logic to do the content conversion</p>
-      </td>
+      <td><p>
+        Logic to do the content conversion. Takes one argument: the raw content
+        of the file (without YAML front matter). Must return a String.
+      </p></td>
     </tr>
   </tbody>
 </table>
 
-In our example, UpcaseConverter-matches checks if our filename extension is `.upcase`, and will render using the converter if it is. It will call UpcaseConverter-convert to process the content - in our simple converter we’re simply capitalizing the entire content string. Finally, when it saves the page, it will do so with the `.html` extension.
+In our example, `UpcaseConverter#matches` checks if our filename extension is
+`.upcase`, and will render using the converter if it is. It will call
+`UpcaseConverter#convert` to process the content. In our simple converter we’re
+simply uppercasing the entire content string. Finally, when it saves the page,
+it will do so with a `.html` extension.
 
 ## Tags
 
-If you’d like to include custom liquid tags in your site, you can do so
-by hooking into the tagging system. Built-in examples added by Jekyll
-include the `{{"{% highlight "}}%}` and `{{"{% include "}}%}` tags. Below is an example custom liquid tag that will output the time the page was rendered:
+If you’d like to include custom liquid tags in your site, you can do so by
+hooking into the tagging system. Built-in examples added by Jekyll include the
+`highlight` and `include` tags. Below is an example of a custom liquid tag that
+will output the time the page was rendered:
 
 {% highlight ruby %}
 module Jekyll
@@ -213,16 +231,20 @@ At a minimum, liquid tags must implement:
   </tbody>
 </table>
 
-You must also register the custom tag with the Liquid template engine as follows:
+You must also register the custom tag with the Liquid template engine as
+follows:
 
 {% highlight ruby %}
 Liquid::Template.register_tag('render_time', Jekyll::RenderTimeTag)
 {% endhighlight %}
 
-In the example above, we can place the following tag anywhere in one of our pages:
+In the example above, we can place the following tag anywhere in one of our
+pages:
 
 {% highlight ruby %}
-<p>{{"{% render_time page rendered at: "}}%}</p>
+{% raw %}
+<p>{% render_time page rendered at: %}</p>
+{% endraw %}
 {% endhighlight %}
 
 And we would get something like this on the page:
@@ -233,7 +255,10 @@ And we would get something like this on the page:
 
 ### Liquid filters
 
-You can add your own filters to the Liquid template system much like you can add tags above. Filters are simply modules that export their methods to liquid. All methods will have to take at least one parameter which represents the input of the filter. The return value will be the output of the filter.
+You can add your own filters to the Liquid template system much like you can add
+tags above. Filters are simply modules that export their methods to liquid. All
+methods will have to take at least one parameter which represents the input of
+the filter. The return value will be the output of the filter.
 
 {% highlight ruby %}
 module Jekyll
@@ -249,7 +274,12 @@ Liquid::Template.register_filter(Jekyll::AssetFilter)
 
 <div class="note">
   <h5>ProTip™: Access the site object using Liquid</h5>
-  <p>Jekyll lets you access the <code>site</code> object through the <code>context.registers</code> feature of liquid. For example, you can access the global configuration file <code>_config.yml</code> using <code>context.registers.config</code>.</p>
+  <p>
+    Jekyll lets you access the <code>site</code> object through the
+    <code>context.registers</code> feature of Liquid. For example, you can
+    access the global configuration file <code>_config.yml</code> using
+    <code>context.registers.config</code>.
+  </p>
 </div>
 
 ### Flags
@@ -269,24 +299,35 @@ There are two flags to be aware of when writing a plugin:
         <p><code>safe</code></p>
       </td>
       <td>
-        <p>A boolean flag that allows a plugin to be safely included in
-Jekyll core for exclusion from use with GitHub Pages. In general, set
-this to <code>true</code>.</p>
+        <p>
+          A boolean flag that informs Jekyll whether this plugin may be safely
+          executed in an environment where arbitrary code execution is not
+          allowed. This is used by GitHub Pages to determine which core plugins
+          may be used, and which are unsafe to run. If your plugin does not
+          allow for arbitrary code, execution, set this to <code>true</code>.
+          GitHub Pages still won't load your plugin, but if you submit it for
+          inclusion in core, it's best for this to be correct!
+        </p>
       </td>
     </tr>
     <tr>
       <td>
-        <p><code>priortiy</code></p>
+        <p><code>priority</code></p>
       </td>
       <td>
-        <p>This flag determines what order the plugin is loaded in. Valid
-values are: <code>:lowest</code>, <code>:low</code>, <code>:normal</code>, <code>:high</code>, and <code>:highest</code>.</p>
+        <p>
+          This flag determines what order the plugin is loaded in. Valid values
+          are: <code>:lowest</code>, <code>:low</code>, <code>:normal</code>,
+          <code>:high</code>, and <code>:highest</code>. Highest priority
+          matches are applied first, lowest priority are applied last.
+        </p>
       </td>
     </tr>
   </tbody>
 </table>
 
-To use one of the example plugins above as an illustration, here is how you’d specify these two flags:
+To use one of the example plugins above as an illustration, here is how you’d
+specify these two flags:
 
 {% highlight ruby %}
 module Jekyll
@@ -298,16 +339,15 @@ module Jekyll
 end
 {% endhighlight %}
 
-
 ## Available Plugins
 
 There are a few useful, prebuilt plugins at the following locations:
 
 - [Truncate HTML while preserving markup structure](https://github.com/MattHall/truncatehtml) by [Matt Hall](http://codebeef.com)
-- [Generic Blog Plugins by Jose Diaz-Gonzalez](https://github.com/josegonzalez/josediazgonzalez.com/tree/master/_plugins): Contains plugins for tags, categories, archives, as well as a few liquid extensions
+- [Generic Blog Plugins by Jose Diaz-Gonzalez](https://github.com/josegonzalez/josediazgonzalez.com/tree/master/_plugins): Contains plugins for tags, categories, archives, as well as a few Liquid extensions
 - [Domain Name Filter by Lawrence Woodman](https://github.com/LawrenceWoodman/domain_name-liquid_filter): Filters the input text so that just the domain name is left
-- [Jekyll Plugins by Recursive Design](http://recursive-design.com/projects/jekyll-plugins/): Plugin to generate Project pages from github readmes, a Category page plugin, and a Sitemap generator
-- [Tag Cloud Plugin from a Jekyll walk-through](http://vitobotta.com/how-to-migrate-from-wordpress-to-jekyll/): Plugin to generate a Tag Cloud
+- [Jekyll Plugins by Recursive Design](http://recursive-design.com/projects/jekyll-plugins/): Plugin to generate Project pages from GitHub readmes, a Category page plugin, and a Sitemap generator
+- [Tag Cloud Plugin from a Jekyll walk-through](http://vitobotta.com/how-to-migrate-from-wordpress-to-jekyll/): Plugin to generate a tag cloud
 - [Pygments Cache Path by Raimonds Simanovskis](https://github.com/rsim/blog.rayapps.com/blob/master/_plugins/pygments_cache_patch.rb): Plugin to cache syntax-highlighted code from Pygments
 - [Delicious Plugin by Christian Hellsten](https://github.com/christianhellsten/jekyll-plugins): Fetches and renders bookmarks from delicious.com.
 - [Ultraviolet plugin by Steve Alex](https://gist.github.com/480380): Jekyll Plugin for Ultraviolet
@@ -380,5 +420,9 @@ There are a few useful, prebuilt plugins at the following locations:
 
 <div class="note info">
   <h5>Jekyll Plugins Wanted</h5>
-  <p>If you have a Jekyll plugin that you would like to see added to this list, you should <a href="../contributing">read the contributing page</a> to find out how to make that happen.</p>
+  <p>
+    If you have a Jekyll plugin that you would like to see added to this list,
+    you should <a href="../contributing">read the contributing page</a> to find
+    out how to make that happen.
+  </p>
 </div>

data/site/_posts/2012-07-01-posts.md

@@ -5,77 +5,121 @@ prev_section: frontmatter
 next_section: pages
 ---
 
-One of Jekyll’s best aspects is that it is “blog aware”. What does that mean, exactly? Well, simply put it means that blogging is baked into Jekyll’s functionality by default. For people who write articles and publish them online, this means that you can publish and maintain a blog simply by managing a folder full of text-files on your computer. Compared to the hassle of configuring and maintaining databases and web-based CMS systems, this will be a welcome change for many.
+One of Jekyll’s best aspects is that it is “blog aware”. What does this mean,
+exactly? Well, simply put, it means that blogging is baked into Jekyll’s
+functionality. If you write articles and publish them online, this means that
+you can publish and maintain a blog simply by managing a folder of text-files on
+your computer. Compared to the hassle of configuring and maintaining databases
+and web-based CMS systems, this will be a welcome change!
 
 ## The Posts Folder
 
-As detailed on the [directory structure](../structure) page, the `_posts` folder in any Jekyll site is where the files for all your articles will live. These files can be either [Markdown](http://daringfireball.net/projects/markdown/) or [Textile](http://textile.sitemonks.com/) formatted text files, and as long as they have [YAML front-matter](../frontmatter) defined, they will be converted from their source format into a HTML page that is part of your static site.
+As explained on the [directory structure](../structure) page, the `_posts`
+folder is where your blog posts will live. These files can be either
+[Markdown](http://daringfireball.net/projects/markdown/) or
+[Textile](http://textile.sitemonks.com/) formatted text files, and as long as
+they have [YAML front-matter](../frontmatter), they will be converted from their
+source format into an HTML page that is part of your static site.
 
 ### Creating Post Files
 
-To create a new post, all you need to do is create a new file in the `_posts` folder. The filename structure used for files in this folder is important—Jekyll requires the file to be named in the following format:
+To create a new post, all you need to do is create a new file in the `_posts`
+directory. How you name files in this folder is important. Jekyll requires blog
+post files to be named according to the following format:
 
 {% highlight bash %}
 YEAR-MONTH-DAY-title.MARKUP
 {% endhighlight %}
 
-Where `YEAR` is a four-digit number, `MONTH` and `DAY` are both two-digit numbers, and `MARKUP` is an appropriate file extension for the format your post is written in. For example, the following are examples of excellent post filenames:
+Where `YEAR` is a four-digit number, `MONTH` and `DAY` are both two-digit
+numbers, and `MARKUP` is the file extension representing the format used in the
+file. For example, the following are examples of valid post filenames:
 
 {% highlight bash %}
-2011-12-31-new-years-eve-is-awesome.markdown
+2011-12-31-new-years-eve-is-awesome.md
 2012-09-12-how-to-write-a-blog.textile
 {% endhighlight %}
 
 ### Content Formats
 
-The first thing you need to put in any post is a section for [YAML front-matter](../frontmatter), but after that, it's simply a case of deciding which format you prefer to write in. Jekyll supports two popular content markup formats: [Markdown](http://daringfireball.net/projects/markdown/) or [Textile](http://textile.sitemonks.com/). These formats each have their own way of signifying different types of content within a post, so you should read up on how these formats work and decide which one suits your needs best.
+All blog post files must begin with [YAML front- matter](../frontmatter). After
+that, it's simply a matter of deciding which format you prefer. Jekyll supports
+two popular content markup formats:
+[Markdown](http://daringfireball.net/projects/markdown/) and
+[Textile](http://textile.sitemonks.com/). These formats each have their own way
+of marking up different types of content within a post, so you should
+familiarize yourself with these formats and decide which one best suits your
+needs.
 
 ## Including images and resources
 
-For people who publish articles on a regular basis, it’s quite common to need to include things like images, links, downloads, and other resources along with their text-based content. While the ways to link to these resources differ between Markdown and Textile, the problem of working out where to store these files in your site is something everyone will face.
+Chances are, at some point, you'll want to include images, downloads, or other
+digital assets along with your text content. While the syntax for linking to
+these resources differs between Markdown and Textile, the problem of working out
+where to store these files in your site is something everyone will face.
 
-Because of Jekyll’s flexibility, there are many solutions to how to do this. One common solution is to create a folder in the root of the project directory called something like `assets` or `downloads`, into which any images, downloads or other resources are placed. Then, from within any post, they can be linked to using the site’s root as the path for the asset to include. Again, this will depend on the way your site’s (sub)domain and path are configured, but here some examples (in Markdown) of how you could do this using the `{{ "{{ site.url " }}}}` variable in a post.
+Because of Jekyll’s flexibility, there are many solutions to how to do this. One
+common solution is to create a folder in the root of the project directory
+called something like `assets` or `downloads`, into which any images, downloads
+or other resources are placed. Then, from within any post, they can be linked to
+using the site’s root as the path for the asset to include. Again, this will
+depend on the way your site’s (sub)domain and path are configured, but here some
+examples (in Markdown) of how you could do this using the `site.url` variable in
+a post.
 
 Including an image asset in a post:
 
-{% highlight bash %}
+{% highlight text %}
 … which is shown in the screenshot below:
-![My helpful screenshot]({{ "{{ site.url " }}}}/assets/screenshot.jpg)
+![My helpful screenshot]({% raw %}{{ site.url }}{% endraw %}/assets/screenshot.jpg)
 {% endhighlight %}
 
 Linking to a PDF for readers to download:
 
-{% highlight bash %}
-… you can [get the PDF]({{ "{{ site.url " }}}}/assets/mydoc.pdf) directly.
+{% highlight text %}
+… you can [get the PDF]({% raw %}{{ site.url }}{% endraw %}/assets/mydoc.pdf) directly.
 {% endhighlight %}
 
 <div class="note">
   <h5>ProTip™: Link using just the site root URL</h5>
-  <p>You can skip the <code>{{ "{{ site.url " }}}}</code> variable if you <strong>know</strong> your site will only ever be displayed at the root URL of your domain. In this case you can reference assets directly with just <code>/path/file.jpg</code>.</p>
+  <p>
+    You can skip the <code>{% raw %}{{ site.url }}{% endraw %}</code> variable
+    if you <strong>know</strong> your site will only ever be displayed at the
+    root URL of your domain. In this case you can reference assets directly with
+    just <code>/path/file.jpg</code>.
+  </p>
 </div>
 
 ## Displaying an index of posts
 
-It’s all well and good to have posts in a folder, but a blog is no use unless you have a list of posts somewhere for people. Creating an index of posts on another page (or in a [template](../templates)) is easy, thanks to the [Liquid template language](http://liquidmarkup.org/) and it’s tags. Here’s a basic example of how to create an unordered list of links to posts for a Jekyll site:
+It’s all well and good to have posts in a folder, but a blog is no use unless
+you have a list of posts somewhere. Creating an index of posts on another page
+(or in a [template](../templates)) is easy, thanks to the [Liquid template
+language](http://liquidmarkup.org/) and its tags. Here’s a basic example of how
+to create a list of links to your blog posts:
 
 {% highlight html %}
 <ul>
-  {{ "{% for post in site.posts " }}%}
+  {% raw %}{% for post in site.posts %}{% endraw %}
     <li>
-      <a href="{{ "{{ post.url "}}}}">{{ "{{ post.title "}}}}</a>
+      <a href="{% raw %}{{ post.url }}{% endraw %}">{% raw %}{{ post.title }}{% endraw %}</a>
     </li>
-  {{ "{% endfor " }}%}
+  {% raw %}{% endfor %}{% endraw %}
 </ul>
 {% endhighlight %}
 
-Of course, you have full control over how (and where) you display your posts, and how you structure your site. You should read more about [how templates work](../templates) with Jekyll if you’re interested in these kinds of things.
+Of course, you have full control over how (and where) you display your posts,
+and how you structure your site. You should read more about [how templates
+work](../templates) with Jekyll if you want to know more.
 
 ## Highlighting code snippets
 
-Jekyll also has built-in support for syntax highlighting of code snippets using [Pygments](../extras), and including a code snippet in any post is easy. Just use the dedicated Liquid tag as follows:
+Jekyll also has built-in support for syntax highlighting of code snippets using
+[Pygments](../extras), and including a code snippet in any post is easy. Just
+use the dedicated Liquid tag as follows:
 
-{% highlight ruby %}
-{{ "{% highlight ruby"}} %}
+{% highlight text %}
+{% raw %}{% highlight ruby %}{% endraw %}
 def show
   @widget = Widget(params[:id])
   respond_to do |format|
@@ -83,7 +127,7 @@ def show
     format.json { render json: @widget }
   end
 end
-{{ "{% endhighlight"}} %}
+{% raw %}{% endhighlight %}{% endraw %}
 {% endhighlight %}
 
 And the output will look like this:
@@ -100,7 +144,14 @@ end
 
 <div class="note">
   <h5>ProTip™: Show line numbers</h5>
-  <p>You can make code snippets include line-numbers easily, simply add the word <code>linenos</code> to the end of the opening highlight tag like this: <code>{{ "{% highlight ruby linenos " }}%}</code>.</p>
+  <p>
+    You can make code snippets include line-numbers by adding the word
+    <code>linenos</code> to the end of the opening highlight tag like this:
+    <code>{% raw %}{% highlight ruby linenos %}{% endraw %}</code>.
+  </p>
 </div>
 
-Those basics should be more than enough to get you started writing your first posts. When you’re ready to dig into what else is possible, you might be interested in doing things like [customizing post permalinks](../permalinks) or using [custom variables](../variables) in your posts and elsewhere on your site.
+These basics should be enough to get you started writing your first posts. When
+you’re ready to dig into what else is possible, you might be interested in doing
+things like [customizing post permalinks](../permalinks) or using [custom
+variables](../variables) in your posts and elsewhere on your site.