Designing Yearly GridTemplates

Navigation:  GridTemplates : Designing > GridTemplate Structure >

Designing Yearly GridTemplates

Previous pageReturn to chapter overviewNext page

The most important thing about yearly grids design, is knowing when not to use it.


The way GridTemplates are imported into Q++Studio, many of the grids your marketing would consider as yearly, are actually treated as monthlies (12 months/2 pages, etc...). To decide if the grid you are designing is a yearly, as seen by Q++Studio, refer to the topics :


Monthly Grid Structure.

Yearly Grid Structure.


Once you are convinced that the grid you are working on is a yearly, there are a few simple guidelines to follow :


Μake sure that any headers you use (eg. Year 2000) have tokens whose DayValues will place them in the current year. Using the DayValue 8, like in monthlies, is usually a safe bet.


Because of the above, it is usually a good idea to put a DayValue Marker token on each page of a yearly grid (use a DayValue = 1). Otherwise Q++Studio might misinterpret the grid as containing 8 days.


Yearly grids are often a series of 12, 24 or 36 MiniCalendars covering many years. Designing such a grid for Q++Studio is not complicated.


Make sure you put a DayValue Marker, and only one.


Having MiniCalendar tokens go into future years is not a problem; you can have them refering to dates up to 8 years (99 months) in the past and future.


For the labels (eg. Years 2000-2001-2002), resist the temptation to type the text as is, without tokens. You can use any DayValue which you are sure will be in the desired year (remember that you have a DayValue Marker). For a 3-year monthly grid, oyu can use [8yyyy]-[374yyyy]-[740yyyy], which corresponds to 8 plus multiples of 366.

Topic 87100 updated on 03-May-2018.
Topic URL: