> For the complete documentation index, see [llms.txt](https://help.pixfizz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/build-a-12-month-wall-calendar.md).

# Build a 12-Month Wall Calendar

A complete walkthrough of the most common calendar product: a cover, twelve image pages, twelve month grids and a back cover, built from one page design.

A complete walkthrough of the most common calendar product: a cover, twelve image pages, twelve month grids and a back cover, built from one page design.

Steps 1 to 5 and step 7 are platform work and apply however your storefront is built. Step 6 is the Pixfizz CMS only; on your own storefront or an API integration you supply the start date when the project is created.

## Before you start

Have these ready:

* A design product created under **Admin > Products**, with a template attached.
* The finished artwork for the cover and the month page.
* A decision on whether weeks start on Monday or Sunday. This is set in the definition and is awkward to change once designs are laid out.

Copy the starting definition from [Example Calendar Templates](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/example-calendar-templates.md). The steps below follow the Monday-start 12-month wall calendar.

Also worth five minutes first: set up an AI assistant with the Pixfizz knowledge base and the Pixfizz Storefront plugin, following [aisetup.pixfizz.com](https://aisetup.pixfizz.com/). Its `xml-templates` skill can adapt the example definition to your page size before you start, and `photobook-layouts` can fill the theme with arrangements for the photo pages. See [Calendar Setup](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup.md) for what it is good and bad at.

## Step 1: Paste the template definition

1. Go to **Admin > Products > Templates** and open your template.
2. Paste the example definition into the **Definition** field.
3. Change the `width`, `height`, `bleed` and `dpi` values to your product's real print size.
4. Save.

The definition declares two sequences:

* `calendar-month` builds the 42 cells of a month grid, six weeks, and tags the days belonging to the previous or next month `out-of-range`.
* `by-month` produces the twelve dates the page set loops over, one per month.

The page set repeats once per date in `by-month`, producing an image page and a calendar page for each month. The cover and back cover sit outside the loop with `count="false"` so they are excluded from the page count.

## Step 2: Lay out the month page

1. Open the design in the admin design tool.
2. Build the grid: 42 day cells in six rows of seven, plus the seven weekday headings and a month title.
3. Name the month title element `month`. Select it, open the **Admin** panel and set the **Element name**.

Name any element you will later want to target from a transformation. Element names are the only reliable way to select one specific element on the page.

## Step 3: Bind the cells to dates

For each of the 42 day cells:

1. Select the text element and open the **Dates** panel.
2. Set the **series** to `calendar-month`.
3. Set the **index** to the cell's position, 1 for the top-left cell through 42 for the bottom-right.
4. Set the part of the date to print to the day number.

Then bind the month title:

1. Select the element named `month` and open the **Dates** panel.
2. Set the series to `calendar-month` and the index to any date inside the month, for example 15, so it never lands on a date from the previous or next month.
3. Set the part of the date to print to the month name.

Bind a year element the same way, printing the year part.

An element bound to an index the sequence does not produce is deleted at build time. That is how a six-row grid handles a month that only needs five rows.

## Step 4: Handle the days outside the month

The `calendar-month` sequence tags the leading and trailing days `out-of-range`. Decide what should happen to them and add one calendar transformation on the design page:

* To grey them, use the grey rule in [Example Calendar Templates](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/example-calendar-templates.md).
* To hide them completely, use the hide rule on the same page.
* To print them in the same style as the rest of the month, add no rule at all.

If days are greyed out and you do not want them to be, the rule doing it is a transformation on the design. Remove that rule. See [Calendar Troubleshooting](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/calendar-troubleshooting.md).

## Step 5: Add the per-month behavior

Anything that differs between months is a transformation, not a second design. Common cases:

| You want                                   | Rule set                                   |
| ------------------------------------------ | ------------------------------------------ |
| A logo on December only                    | A logo on December only                    |
| Alternating artwork on odd and even months | Alternating artwork on odd and even months |
| Red Sundays and holidays                   | Sundays and holidays in red                |
| A different background per season          | A background per season                    |

All four are in [Example Calendar Templates](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/example-calendar-templates.md). Paste the JSON array into the **Calendar Transformations** field on the design page in admin. If you use more than one rule set, merge them into a single array.

These rule sets are repetitive by nature, eleven or twelve near-identical lines. If you have the AI setup from [aisetup.pixfizz.com](https://aisetup.pixfizz.com/), ask it to generate the array for your element names rather than editing each line by hand, then read what it produces before pasting it in.

## Step 6: Turn on the start-date selector (Pixfizz CMS only)

> This step applies only to storefronts running the Pixfizz CMS, and the settings named are those of the Shopper 24 template. On your own storefront or an API integration, supply the start date when the project is created and skip to step 7.

The start date drives the whole calendar, so it is not optional.

1. On the product, set the custom field `select_date`. The Shopper product form renders the start-date selector only when that field is set.
2. Decide whether the customer picks a month as well as a year. Set `hide_select_month` on the product for a year-only selector, which suits a calendar that always runs January to December.
3. Check the year range. The year selector takes `min` and `max` as offsets from the current year, not absolute years; the Shopper default is this year plus three.
4. On a product where a wrong start year means a reprint, set the site checklist key `admin/checklist/confirm-start-date` to `TRUE`. That adds a confirmation checkbox and keeps Add to Cart disabled until it is ticked, with the wording taken from `admin/checklist/confirm_start_date_label`.

The default selection rolls over on its own: from September onwards it offers January of next year, before September the following month of the current year.

If the calendar should also carry dated captions, set the design custom field `personal_dates` to offer signed-in customers their saved life events, and `holiday_dates` to offer the website calendars created under **/calendars**. Captions from whichever calendars the customer selects are what the `calendar` transformation selector matches on.

## Step 7: Test before publishing

1. Create a project starting in January of next year.
2. Page through all twelve months. Check the first and last cell of every month, and check February.
3. Check a month that starts on a Sunday and one that starts on a Monday.
4. Place a test order and open the generated PDF. Confirm the page count, the page order and that the cover is not counted.
5. Repeat with a start date in a leap year.

## Tips

* Build one month correctly, then test, then add transformations. Fixing a grid after twelve months of transformations are in place is slow.
* Keep a copy of the working definition outside the platform. It is the fastest way to recover a design that has been edited into a broken state.
* If the same calendar is sold on several sites, build it once and copy the design rather than re-tagging 42 cells per site.
* Selling the same calendar at more than one size is a job for the `template-resize` skill in the Pixfizz Storefront plugin rather than a hand rebuild.
* On the Pixfizz CMS, `select_date`, `hide_select_month`, `personal_dates` and `holiday_dates` are custom fields. Each one needs its definition created on the site before a value can be stored, so check they exist when a selector does not appear on a new site.

## Related

* [Calendar Setup](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup.md)
* [Date Sequences Reference](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/date-sequences-reference.md)
* [Calendar Transformations](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/calendar-transformations.md)
* [Example Calendar Templates](https://help.pixfizz.com/products-and-design/how-to-create-templates/calendar-setup/example-calendar-templates.md)
* [Pixfizz AI setup guide](https://aisetup.pixfizz.com/)
