Partial in content

[Jonathan]

Hi Lonnie,

I'd like to include a partial in one of my content file, but simply
putting {side} in the content file just prints "{side}". Is there a
way around that?

Thanks

[Lonnie Ezell]

The {side} call that your using needs to be called liked: {partial:
side} and then have the partial defined in the top of the file. I'll
illustrate with the home page of blueiceapp.com.

The index page is not using a _shared.txt file to specify partials. In
the content file, though it is pulling in the Table of Contents for
the help pages. The main page looks like this:

--- /// START INDEX.MD ///---
page_title: BlueIce - the anti-CMS
partial_sidebar: sb_home
partial_toc: toc_docs

## The Anti-CMS

BlueIce is the **anti-CMS**. There are no users. No admin area. No
database. All changes are done through folders and text-files on the
server.

BlueIce is not for everyone. It is designed for smaller websites,
primarily "static" information, run by a single person, though plugins
can be easily created to do most anything you need the system to do.

For those that are comfortable using [Markdown](), a text editor, and
FTP, then this might be the right choice for you.

BlueIce was heavily inspired by the excellent portfolio app, [Stacey]
(http://staceyapp.com).

{partial: toc}
--- /// START INDEX.MD ///---

Hope that helps.
Lonnie

[Jonathan]

Thanks, Lonnie

Yes I realized that my {side} call wouldn't work...
So I have this at the top of my index.txt (don't want it passed
through Markdown) content file :
<pre>
page_title: Six Pixels
partial_head: header
partial_foot: footer
partial_side: servicios
description: Six Pixels es un estudio de desarrollo y de diseño web,
basado en España.
home: active
</pre>

and further down I have {partial: side} But it doesn't do anything at
all. The calls to {partial: head} and {partial: foot} in the template
work perfectly. If I put {partial: side} in the template, it works
fine too, although it appears in the wrong place...

Thanks anyway

[Lonnie Ezell]

One thing I did notice is that sometimes order matters in the partial
definitions at the top of the file. You might try reordering so that
the partial_side is before the other partials. I'm not 100% sure why
this is happening, but that's fixed it for me a couple of times.

Hope that helps!