> For the complete documentation index, see [llms.txt](https://docs.parameter1.com/base-cms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parameter1.com/base-cms/content-management/scheduling.md).

# Scheduling

Scheduling content is how you get it to appear on the website, newsletter, or print magazine.  In most cases, without an active schedule, the content will not live outside of the CMS.

## Newsletter Scheduling

{% content-ref url="/pages/-MK0Q0SywyyI5BTaM6FP" %}
[Scheduling Content to Newsletters](/base-cms/newsletter-management/new-framework/scheduling-content-to-newsletters.md)
{% endcontent-ref %}

## Magazine Scheduling

{% content-ref url="/pages/-MK0PhRJ-wUkFvtGB\_Nv" %}
[Scheduling Content to Magazines](/base-cms/print-issue-management/scheduling-content-to-magazines.md)
{% endcontent-ref %}

## Website Scheduling

Before we get started, I want to reiterate that the [**Primary Section**](/base-cms/content-management/adding-and-editing-content.md#primary-site-primary-section) field under the **SEO Fields** portion of the content **does not correlate** **to where the content displays on the website.**  

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0V0EYeyU0KyHDyvNb%2Fimage.png?alt=media\&token=e27cd1be-1de3-44f0-8bbf-b771baaf4a28)

{% hint style="info" %}
The **Primary Section** SEO field is what's displayed on the content when it appears as a thumbnail across the website. 
{% endhint %}

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0V3K-MJr-PzHTJPLK%2Fimage.png?alt=media\&token=a688be71-bb1d-4b6f-a159-f6d3002b768c)

### Adding a new Website Schedule

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0V4z6xlugS6d4VetC%2Fimage.png?alt=media\&token=f6aa5563-4cd4-4e5b-b788-80ba45c40738)

There are three drop-downs for website scheduling.  The first asks you which site you want to schedule to.  If this is not a multi-site (most users will only have one site), then the default will be auto-selected to the only website choice available.  

The second field allows you to select the "Option".  By default, you will have **Standard** and **Pinned,** although some sites may have additional options, such as **Sponsored**. See table below for descriptions of Standard vs Pinned:

{% tabs %}
{% tab title="Pinned" %}
Pinning an item will "stick" or "pin" it to the hero block on the home page and primary channel/section pages.  It will take priority over items scheduled as **Standard** regardless of scheduled date of **Standard** items.  This can be useful if you know certain stories should appear on a section for several days at a time, without having to worry about another piece of content with a newer section schedule taking its place in the meantime.

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0V78pOe_iZMQvD8JI%2Fimage.png?alt=media\&token=71c1363c-1005-40f0-b81e-7fe234b3788a)

Pinning items should be used sparingly, since they will always take priority over **Standard** items.  If there are too many pieces of content Pinned to a section, it can be difficult to maintain and organize your website.

*If multiple pieces of content are pinned to a section, they will be sorted based on scheduled date, from newest to oldest.*  

{% endtab %}

{% tab title="Standard" %}
This is the most commonly used status and should be used 90%+ of the time.  It is the default option for scheduling content to sections.  If there is nothing **Pinned** to the section, content will flow from **newest to oldest.**  (Specific to scheduled date - as opposed to Created, Modified, or Published date, although these may share the same date(s)).
{% endtab %}
{% endtabs %}

### Selecting a Section

This is an auto-fill field where you can start typing the name of the section you wish to schedule to, or select the drop-down and scroll through existing sections.  

{% hint style="info" %}
You may not create/modify or delete sections through this interface.  Any section change requests must first be approved, then submitted to Base Support for implementation.
{% endhint %}

Once a section has been selected, the website schedule will appear below:

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0VBP_KpVGMgKZNjGF%2Fimage.png?alt=media\&token=9e927cf4-5785-4e31-943f-358b757cde93)

* The scheduled date and time will default to the **Content Published Date**.  If the content does not have a published date set, it will default to the **Created Date**.  Content on the website flows from top to bottom, with the most recent schedule date appearing at the top.   
* To adjust the **Scheduled Date**, or to modify the section or option, select the **Edit** button directly to the left of the red X.
* To **Delete a section,** click the red box with an X.

### Here's a short video of how we added a website schedule to a webinar:

{% file src="/files/-MK0VFvB-OojUuzaqr19" %}
Adding a Website Schedule
{% endfile %}

## Example of typical website scheduling structure.

Many homepages are structured in a similar fashion, where it begins with a Hero block that's meant for the newest content that will get the most visibility, and is followed by columns of other blocks, typically corresponding to the site's Primary Sections.

### Hero Block

A Hero block will typically appear at the top of the homepage, as well as at the top of Primary Section landing pages.  

To scheduled content to the hero block of the homepage, you'll schedule the content to the "Home" section of your website, like this:

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0VRoAHg-1mWCrcbUs%2Fimage.png?alt=media\&token=f157c450-0cf5-4f7c-8f91-5bddc6c3a5f8)

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0VUfIFhuTAG-6V8Q5%2Fimage.png?alt=media\&token=b2489514-2be3-40fe-a089-9db3f5476079)

Following the homepage, there are usually a series of columns that correspond to the website's Primary Sections, and usually look something like this:

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0VWb-gB0ndbX3S8yi%2Fimage.png?alt=media\&token=48f62e0f-9831-4eaf-a980-f3b9445710e5)

For content to appear in those blocks on the homepage, they will need to be scheduled to the corresponding section.  The content with the newest schedules will appear in those blocks on the homepage.  **They will also appear on the section landing page.** 

For example, let's look at **"Big Ass Fans Brings Back the Pivot"**  under the "Tools & Equipment" section from the screen shot above.  That content has the most recent schedule to the "Tools & Equipment" section.  Therefore, it's going to be the first to appear in that block:

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0V_mPvtvuLZBKQKNq%2Fimage.png?alt=media\&token=4b2aa954-6c48-4553-90fc-6039255befcf)

It will also appear on the section landing page for "Tools & Equipment" like so:

![](https://3240145413-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJm8TT5zrveJuijYYUO%2F-MK0UB0NebPmTUvXvj-a%2F-MK0VbgWdZsN6D008Fcv%2Fimage.png?alt=media\&token=09f1758c-5ea2-4212-943e-7493939de992)

{% hint style="warning" %}
**If there is also a schedule to "Home", that content may appear up top in the Hero block instead of the "Tools & Equipment" block.**  Content will only appear on a page once, so if it's not displaying where you want it to, see a list of troubleshooting techniques[ here](/base-cms/content-management/scheduling/troubleshooting.md).
{% endhint %}