Your Top Five Concerns With Using Rock as a CMS

1. Rock will never have all the features of my current CMS.
   Yep, you're right. We'll never be able to have every feature that your current CMS has, although chances are, they don't have every feature we have either. Rock makes creating powerful websites easy. We’ve stolen borrowed the best ideas from the top CMS out there. We've leveraged our years of experience building sites to create tools we’ve always wanted.
2. We'll never be able to find someone who knows Rock; everyone knows xxxxx.
   We're working hard to establish an ecosystem full of vendors and freelancers who can help you. Not only that, but documentation like this manual makes it simple to quickly bring any web designer vendor up to speed. You should probably hesitate to use any vendor who resists using the tool the customer wants and instead uses their favorite tool. Remember, you're the one who needs to live with the site.
3. Rock is built on Microsoft .Net. Come on, no serious CMS uses that.
   While there are several popular .Net CMS systems (Umbraco, DotNetNuke, Orchard) that really isn't the point. When looking for a CMS, you need powerful features with blazingly fast performance that can scale. Rock excels at each of these. Think about it this way: Should the builder be judged by the tools he brings to the worksite or the building that stands when he's finished? That's not to say we're not proud of our tools. We LOVE .Net and we think you will too once you try it on.
4. There are a limited number of .Net webhosts to run Rock on and the ones that do exist are more expensive.
   True, there are fewer than our PHP/MySql cousins, but there are numerous vendors to pick from. We've outlined a couple of recommended choices in our Rock Solid External Hosting guide. As far as price, .Net hosting on average costs about 20% more than Linux hosting. On the lower end this translates into $2-$3 dollars a month. The return on investment with using Rock as your CMS will far outweigh this small difference.
5. But I’m a PHP developer; I don’t know .Net.
   That's just a part of the job. Constant change is the career you’ve chosen. Technologies like LESS, jQuery and Bootstrap didn't exist two years ago. To not change is to become extinct. Don't see yourself as a .Net Developer, instead look at yourself as just a developer who today uses .Net. If you're a developer, you'll have no trouble with .Net. It's an elegant and well-designed language.

But What Are the Benefits?

Hopefully you're starting to see that some of the barriers aren't as large as they may appear. But there's no reason to change for change's sake; the benefits must outweigh the cost. Reading through this manual will show you numerous ways to exploit the power of Rock's CMS features. But let’s touch on one simple example. The biggest "killer app" of Rock is personalization. Just picture adding the markup below into your baptism page using Rock's on-page HTML editor (You’re going to love the editor!):

{% if Person %} 
    {% if Person.BaptismDate != '' %}
        {{ Person.NickName }}, remember the joy of your baptism? Share that joy
        with a friend who hasn't yet taken the plunge at one of our upcoming
        baptism events!
    {% else %}
        {{ Person.NickName }}, now is the time! Don't put off baptism any longer,
        take the plunge at one of our upcoming events!
    {% endif %}
{% else %}
    Take the plunge at one of our upcoming baptism events!
{% endif %}

Rock uses an upcoming templating engine called Lava. Paired with Rock data, Lava is very powerful. The markup above does this:

• If the user is logged in and has been baptized it shows the message: "Alisha, remember the joy of your baptism? Share that joy with a friend who hasn't yet taken the plunge at one of our upcoming baptism events!"
• If the user hasn't been baptized yet they will see: "Alisha, now is the time! Don't put off baptism any longer, take the plunge at one of our upcoming events!"
• Otherwise, if the user is not logged in, the greeting reads: "Take the plunge at one of our upcoming baptism events!"

Armed with just a little knowledge of Lava, we've created a very personal experience on our site; one that is much more likely to draw the user in and promote action. Are you starting to see the power of Rock? And we're just getting started.

Sites

The top of the CMS hierarchy is the site. Each website you create should be created as a unique site. Think of sites as a collection of related pages that share a consistent look and feel. Sites aren't limited to external websites though. You can use them to contain your check-in pages or a set of pages for a metrics dashboard.

Sites are created and managed under Admin Tools > CMS Configuration > Sites. Be sure to use the chapter Creating a New Site before setting out on your own.

Themes

Themes are a set of resources that add styling to the pages of a site. The theme is defined at the site level. This makes it very easy to change the look of an entire site with a single configuration change. You can read more about themes in the chapter Working With Themes.

Pages

The concept of pages is pretty obvious; they represent a single web page. Unlike many CMS however, the page does not exist as a file on the website. Instead, a page is dynamically assembled by Rock with each request. This allows each page to be personalized by the person requesting it and allows you to secure portions of the page based on the security rights of the user.

Pages are arranged in a parent-child hierarchy. This hierarchy allows us to build dynamic menus.

Layouts

Each page is configured to have a specific layout. This determines the content areas (or zones) that the page has. Available layouts are defined by the theme that the site is configured to use. While you can create as many new layouts as you'd like, we strongly recommend that you use the standard names for reasons that will be made obvious in future chapters.

Zones

Zones are content areas that are defined by the layout. They represent things like the header, navigation menu, footer and content areas.

Blocks

Blocks make up the actual content of the page. They come in all shapes and sizes. Each has a specific purpose. The most common block is the HTML Content block. This block allows you to display and edit HTML content to a specific zone. Other blocks are used to generate navigation menus, list groups, show maps, etc. Think of blocks as your Legos® that you can use to build a world of new inventions.

Blocks can be placed on either a page or a layout. When tied to a layout they are displayed on every page that uses the layout. This is very helpful when adding content like navigation in the header or footer text that should be the same across all pages.

The Anatomy of a Page

Now that we've covered all of the components of the Rock CMS system let's look at a visual representation of a page.

1 Header Zone

The header zone is used for the organization's logo and tagline.

2 Navigation Zone

The navigation zone holds the site's main menu.

3 Login Zone

The login zone allows users with accounts to access protected portions of the site.

4 Feature Zone

The feature zone holds the main content of a homepage which in many cases will be an ad rotator.

5 Sub Feature Zone

The sub feature zone seconary ads or content on the homepage.

6 Footer Zone

The footer zone wraps links and content in the footer.

As you work on your site, you’ll want to add new pages. There are two ways to do this: through your external organization site, or through your internal Rock site. Both methods end in the same result (new pages with blocks and content), you just take different paths to get there. Each approach has its pros and cons. Creating pages from your external site allows you to view the pages as you’re creating them. Creating pages from your internal site allows you to create and configure pages faster as well as to easily see how the new pages fit into the overall site structure.

Let’s start by looking at how to add a page from your external site.

Adding a Page (External Site)

To add a page from your external organization site, follow these steps:

1. Navigate to the parent page that you want the new page to be under.
2. Click the (Child Page) button from the Admin Toolbar.
3. From the Child Page dialog, click the button to add a new page to the list.
4. The Add screen will allow you to provide a name for your page and choose a layout. To configure the page fully you'll need to click on it from the child page list and then click its (Page Properties) button on its Admin Toolbar.

Adding a Block to a Page (External Site)

A small part of your content management duties will be to add and configure blocks on a page. To add a block to an existing page follow these simple steps.

1. Navigate to the page you’d like to add the block to.
2. Select the (Page Zone Editor) button in the page’s Admin Toolbar.
3. This will highlight all of the zones on the page for you.
4. Select the fly-out toolbar for the zone you wish to add the block to and click its (Zone Blocks) button. This will bring up the zone's block list.
5. From here you have a decision to make. Do you want the block to live on just this page, on every page that uses this layout, or across your entire site? Decide by picking the appropriate tab at the top of the dialog: Page, Layout or Site. Keep in mind, choosing any option other than Page carries some risk. The Layout and Site options are best used for blocks you're certain belong on multiple pages, such as headers and footers.
6. Next, click the (Add Block) button to add the block to the layout. Like adding a page you'll just provide a name for your block and the type of block you wish to add. You'll add more configuration later.
7. Next, determine what order you want your block to appear in the zone. You can move it up or down by dragging and dropping the order on the list.
8. Now that you've added your block to the list, click the Done link and reload your page. Your new block will now be on the page.
9. In most cases, you'll now need to configure your block. To do so click the (Block Configuration) button in the Admin Toolbar. This will highlight each block on the page.
10. To edit the settings, click the (Block Properties) button from the block's fly-out menu. This will bring up the block properties dialog with all of the settings for the selected block.

Now that your page is created and your block structure is set up, it’s time to configure your page properties and add content. To learn how to do this, see the Managing Content and Pages section below.

Adding a Page (Internal Site)

Adding a page from your internal site allows you to both create a page and configure its properties in the same place.

Begin by going to Admin Tools > CMS Configuration > Pages. You’ll see in a tree navigation of the pages of your site, as well as an Add Page button. Click Add Page and select either Add Top-Level or Add Child To Selected. Rock will display the Add Page screen.

The Add Page screen has three tabs: Basic Settings, Display Settings, and Advanced Settings. This is where you set up the new page’s properties.

1 Parent Page:

You can easily change the parent page for your selected page. This will alter where that page is displayed in the navigation.

2 Internal Name:

This is the name of the page that is used in the admin menus and page pickers. Often, in these situations, you want the page to have a more descriptive name than you might want to be displayed in a menu on the site. For instance you might want the homepage of a site to have the internal name of "Youth Sports Homepage" but when you're on the site the title should be simply "Home" on the menu.

3 Page Title:

This is the name that will be used for the page title element on the page. It will also be used in the navigation menus and breadcrumbs.

4 Browser Title:

For Search Engine Optimization it's often important to have a different name in the browser's title. This setting allows you to edit this.

5 Site:

Each page belongs to a site. You can change the site for a page with this setting. Keep in mind that the page gets its theme from the site so changing this setting could change how the page is displayed.

6 Layout:

This selects the layout that the page should use. Further discussion of layouts can be found in the chapter Looking Deeper at Layouts.

7 Show Icon:

An icon can be used in the page title and breadcrumbs if it is enabled with this setting.

8 Icon CSS Class:

This setting allows you to enter the CSS class for the font icon you wish to use. While Font Awesome is installed, there's no reason you can't add your own alternate font icon collection and enter your custom class here. When using Font Awesome, you should use the syntax fa fa-.

9 Description:

The description gives a short summary of the page and its intent. You can use this as "internal documentation" or, using Lava, you can use it in your menus and page listings.

1 Page Display Settings:

These settings control the view state of various components of the page (title, breadcrumbs, description, etc.) How these actually render on the page is somewhat dependent on the theme you are using.

2 Menu Display When:

How and when a page is displayed in a menu has several different options.

• When Allowed:With this default option a page will only be displayed in the menu when the user has view permissions to the page.
• Always:You may want some pages that require a login to be displayed in the menu even when a user isn't logged in. When the user clicks the link, they will be asked to log in before proceeding to the page. This is helpful for things like group toolboxes where you want the user to see the option and then log in before they can view the contents.
• Never:Some support pages aren't meant to ever be navigated to directly. Setting them to never display ensures that a user never accidentally views them in a menu.

3 Breadcrumb Settings:

These settings determine whether a page should be displayed in the breadcrumbs and if so, whether an icon should be included. Some designers set the name to not display but they do show an icon for homepages.

1 Force SSL:

This ensures that the page will always load using SSL. This is important for pages like giving or online registration where credit card information will be used on the page. This does require that your webserver is configured to support SSL.

2 Enable ViewState:

ViewState is a .Net technology that allows a page to remember it's state across postbacks. If this doesn’t make complete sense to you, you probably should not uncheck the box. In most cases bad things will happen if you do.

3 Cache Duration:

This setting sets a page cache header in the page that tells the browser to cache the page locally for the provided timeframe.

4 Body CSS Class:

You can enter a specific CSS class for a specific page in this field. For example, if you want to change the look and feel of a particular registration landing page, you can create a unique CSS class for that page and designate the class here.

5 Page Routes:

You can enter page routes for the page here. Several routes can be configured by delimiting them with commas. For more see the Routes chapter below.

5 Header Content:

As a web designer we know you'll have custom scripts, meta tags, styling and more that you'll want to add to the page's header. Whatever text you add to this setting will be placed into the page's header.

Click Save when you’re done. Now it’s time to add content to your page. To learn how to do this, see the Managing Content and Pages section below.

Editing a Page (Internal Site)

You can also edit a page’s block configuration and properties from the internal site. From the Pages screen (Admin Tools > CMS Configuration > Pages), click the page you want to edit from the tree navigation.

From here, you can edit an existing block by clicking the button. You can also add a new block by selecting the zone where you want the block to go from the dropdown menu on the right, then clicking to display the Add Block window.

Note here the option to add this block to the Page, Layout, or Site. Just as when adding a block to your external site, you need to decide if you want this block to only appear on the current page, on any page using this layout, or across your entire internal site. The Layout and Site options are best used when adding a block you know for sure belongs on every page, such as a header or footer. Otherwise, it's best to use the Page option.

To edit an existing block’s properties, click the button. Rock will display the Block Properties screen. The options displayed will depend on the the kind of block you're editing.

Page Load Time

When we started to plan for Rock, we listed out our high-level goals for the project. One of these was "Speed as a Feature." For us that was more than just words, we wanted it to real and measureable. One of the first features we added was the page load time in the admin bar. From that moment on speed was put in front of us on every page we loaded. We kept it there, not only as our contract with you, but also so you could measure your custom modifications.

Block Configuration

Clicking the block configuration button () in the admin toolbar will bring up a fly-out menu over each block on the page. Rolling over these menus will allow you to:

• Block Settings: This brings up a dialog that allows you to manage the block settings for that block.
• Block Security: This item allows you to edit the security of the block. This not only allows you to control who can view a block, but also who can edit and administrate blocks.
• Move Block: Selecting this item allows you to move the block to a different zone on a page. You can also move the block from the pages zone to the layouts zone. This will make the block available to each page that uses the layout.
• Delete Block: For everything there is a season; a time to add and a time to delete. When it’s time to delete, use this option.

Page Properties

The page properties () dialog allows you to edit all of a page's settings. We'll walk through each in detail. (If you created your pages using the internal site method above, the following page properties screens might look familiar.)

Basic Settings Tab

1 Parent Page:

You can easily change the parent page for your selected page. This will alter where that page is displayed in the navigation.

2 Internal Name:

This is the name of the page that is used in the admin menus and page pickers. Often, in these situations, you want the page to have a more descriptive name than you might want to be displayed in a menu on the site. For instance you might want the homepage of a site to have the internal name of "Youth Sports Homepage" but when you're on the site the title should be simply "Home" on the menu.

3 Page Title:

This is the name that will be used for the page title element on the page. It will also be used in the navigation menus and breadcrumbs.

4 Browser Title:

For Search Engine Optimization it's often important to have a different name in the browser's title. This setting allows you to edit this.

5 Site:

Each page belongs to a site. You can change the site for a page with this setting. Keep in mind that the page gets its theme from the site so changing this setting could change how the page is displayed.

6 Layout:

This selects the layout that the page should use. Further discussion of layouts can be found in the chapter Looking Deeper at Layouts.

7 Show Icon:

An icon can be used in the page title and breadcrumbs if it is enabled with this setting.

8 Icon CSS Class:

This setting allows you to enter the CSS class for the font icon you wish to use. While Font Awesome is installed, there's no reason you can't add your own alternate font icon collection and enter your custom class here. When using Font Awesome, you should use the syntax fa fa-.

9 Description:

The description gives a short summary of the page and its intent. You can use this as "internal documentation" or, using Lava, you can use it in your menus and page listings.

Display Settings

1 Page Display Settings:

These settings control the view state of various components of the page (title, breadcrumbs, description, etc.) How these actually render on the page is somewhat dependent on the theme you are using.

2 Menu Display When:

How and when a page is displayed in a menu has several different options.

• When Allowed:With this default option a page will only be displayed in the menu when the user has view permissions to the page.
• Always:You may want some pages that require a login to be displayed in the menu even when a user isn't logged in. When the user clicks the link, they will be asked to log in before proceeding to the page. This is helpful for things like group toolboxes where you want the user to see the option and then log in before they can view the contents.
• Never:Some support pages aren't meant to ever be navigated to directly. Setting them to never display ensures that a user never accidentally views them in a menu.

3 Breadcrumb Settings:

These settings determine whether a page should be displayed in the breadcrumbs and if so, whether an icon should be included. Some designers set the name to not display but they do show an icon for homepages.

Advanced Settings

1 Force SSL:

This ensures that the page will always load using SSL. This is important for pages like giving or online registration where credit card information will be used on the page. This does require that your webserver is configured to support SSL.

2 Enable ViewState:

ViewState is a .Net technology that allows a page to remember it's state across postbacks. If this doesn’t make complete sense to you, you probably should not uncheck the box. In most cases bad things will happen if you do.

3 Cache Duration:

This setting sets a page cache header in the page that tells the browser to cache the page locally for the provided timeframe.

4 Body CSS Class:

You can enter a specific CSS class for a specific page in this field. For example, if you want to change the look and feel of a particular registration landing page, you can create a unique CSS class for that page and designate the class here.

5 Page Routes:

You can enter page routes for the page here. Several routes can be configured by delimiting them with commas. For more see the Routes chapter below.

6 Header Content:

As a web designer we know you'll have custom scripts, meta tags, styling and more that you'll want to add to the page's header. Whatever text you add to this setting will be placed into the page's header.

Child Pages

The child pages () dialog allows you to see a list of child pages of the current page. From this list you can reorder the pages, delete a page, copy an existing page, or add a new page. You can also use this list to navigate to a page that might not be available in the menu.

When copying an existing page, not only is the page copied, but also the page blocks, child pages, and child page blocks. What a time saver! Even though Rock will re-wire up any references between the new blocks and new pages, it is wise to double check your block settings to to verify everything is what you expect.

Page Zone

Clicking the Page Zones button () will enable the zone fly-out menu for each zone defined on the page. From this menu you can bring up the zone dialog below.

From the zone dialog you can add or delete blocks in a zone. The tabs at the top of the page determine if the blocks will be added to the current page or the layout. Adding the block to the layout will enable it to be shown on all pages that use that layout.

Page Security

The Page Security () dialog allows you to set security for the page. This allows you to determine who can view and administrate the current page. Note that page security is hierarchical. If no specific security rights are defined by a page, it will use the security settings of its parent and its parent's parent. If no page above it defines any specific rights it will use the rights defined for the site. This allows for a robust and flexible security implementation with minimal configuration.

Short Links

Short links () are exactly what their name implies: short, user-friendly links that take the place of long, complicated URLs. Rock makes it easy to create your own short links. Clicking the button displays the Shortened Link window.

1 Site:

This is where you choose which site you want to use for the short link. Only sites that have the Enabled For Shortening option checked will appear in the options. The Enabled For Shortening option is located in the site's Site Detail screen. See Creating A New Site for more information.

2 URL:

This is the url the short link will redirect users to. The default is the URL of the current page, but you can change it to any valid URL.

3 Token:

The token is a unique, random value at least seven-digits long that is used to identify the page in a short link. Rock generates a default token for you, but you can also provide your own. Remember, the token must be unique and at least seven digits long.

4 Short Link:

This is the short link created from the Site, URL and Token values. The short link will automatically update when values in the Site, URL and Token fields change. Clicking the link will automatically copy it to your clipboard.

5 Save:

The short link will not work until you click Save. Clicking Save will also automatically copy the short link to your clipboard.

Managing Short Links

As you create short links, they can be viewed and managed in the Short Links screen found at Admin Tools > CMS Configuration > Short Links.

Click on a short link from the list to view and/or edit its details, as well as to see where and how it's been used. Click the button to copy the short link to your clipboard.

Rock Information

Clicking the Rock Information button () will display the System Information window where you can view the version info and diagnostics.

Version Info

1 Rock Version:

This shows the current version of Rock that you are running.

2 Server Culture Setting:

These are the language and culture settings that the webserver is configured to use. This setting helps Rock determine how some of the international settings should be configured.

3 Clear Cache:

As you'll see, Rock's cache is an incredible thing. It drastically speeds up the performance of the site. It’s also very smart and will clear old or modified content. At times though, you may need to clear the cache to remove information that is no longer valid. If you make a change and don't see it reflected on a page, consider trying to clear the cache with this option.

4 Restart Rock:

Rarely you might get into a situation where you need to "reboot" Rock. This button acts as Rock's reboot switch.

Diagnostics

The diagnostics tab lists the complete configuration of your Rock environment. It’s useful when working with others to debug an issue.

Basic Usage

To edit the HTML, click the icon in the Admin Toolbar at the bottom of the page. Next, place your cursor over the (Block Fly-out) toolbar and select the (Edit) button. This will bring up the edit modal (shown below). This modal allows you to edit the contents of the HTML. You can also set a date range that the content is valid for. This is great for adding date-sensitive messages.

HTML Content Block Settings

While the default HTML block settings are great for typical usage, you have a ton of extra options that you can use to do some really cool things. Like any block, to get to the settings click the icon in the Admin Toolbar at the bottom of the page and then select the button from the block fly-out menu. This will bring up the block settings dialog. Let’s look at each setting in detail.

Merge Fields

It's time to change the paradigm of how you write content. With Rock, content doesn't have to be impersonal any longer. Using merge fields, you can customize the content for the logged-in user. Not only can you add their name, but you can look at all of the person attributes and make the content relevant to their relationship with your organization. Let's revisit the example from the introduction.

Adding the following on a baptism page allows for a personal and actionable content:

{% if Person %} 
    {% if Person.BaptismDate != '' %}
        {{ Person.NickName }}, remember the joy of your baptism? Share that joy
        with a friend who hasn't yet taken the plunge at one of our upcoming
        baptism events!
    {% else %}
        {{ Person.NickName }}, now is the time! Don't put off baptism any longer,
        take the plunge at one of our upcoming events!
    {% endif %}
{% else %}
    Take the plunge at one of our upcoming baptism events!
{% endif %}

Note the use of Lava syntax to add logic to the page. Here's how the markup above would look:

• If the user is logged in and has been baptized it shows the message: "Alisha, remember the joy of your baptism? Share that joy with a friend who hasn't yet taken the plunge at one of our upcoming baptism events!"
• If the user hasn't been baptized yet they will see: "Alisha, now is the time! Don't put off baptism any longer, take the plunge at one of our upcoming events!"
• Otherwise, if the user is not logged in they are greeted with: "Take the plunge at one of our upcoming baptism events!"

Besides information on the current person you also have access to all organization attributes and items in the context of the page. For more information on Lava syntax see the Lava Basics.

Pages vs Layouts

While it's already been noted before, remember that blocks can be assigned to either a page or a layout. When a block is assigned to a layout, it will be displayed on all pages that use that layout. This is especially useful with the HTML editor block as you'll often want bits of content to be consistently applied to several pages.

Components of Dynamic Content

Rock's dynamic content tools are made up of of three components.

1 Content Channel Types:

Channel types define the structure for the dynamic content tools. They define what attributes are available on both the channels and content items. Rock ships with the following channel types: Website Ads, Bulletins, Blogs, Podcast Messages, Podcast Series, Universal Date Range Channel Types, Universal No Date Channel Types and Universal Single Date Channel Types.

2 Content Channels:

Content channels are implementations of the channel types. For instance, because there is a channel type of Blogs, you can make blog channels for the organization's website, a specific person and/or a specific area of your organization.

3 Content Items:

These are the specific data elements that make up a content channel. For a blog channel these would be the specific blog posts; for the website ads channel these would represent the specific promotions.

Now, let's jump right into adding and managing content items.

Managing Content Items

While it's possible to add new content items on the channel configuration page (Admin Tools > CMS Configuration > Content Channels), most of your staff won't have access to these screens. For staff, it's easier for them to add their content under Tools > Content. On this screen they will see a list of each content channel they have View access to. Clicking one of the items will display the content items for that channel.

1 Content Channels:

List of the content channels that the current user has View rights to. A count of the number of Pending items is displayed in the upper right corner of the channel.

2 Display Toggle:

Toggle switch to display all content channels, or only those with pending items.

3 Content Items:

A listing of all content items in the channel with the ability to filter by status, date range or title.

Adding Content Items

To add a new content item, click the button in the grid footer. This will bring up the add/edit screen below.

1 Title:

The title for the content item.

2 Status:

If approvals are enabled for the channel and the user has Approval rights, they will be able to set the approval status.

3 Priority:

The channel defines if the content items have a priority. If it's enabled, you can set the priority here.

4 Dates:

Dates associated with the content item are defined here. The channel determines if the items is a single date or a date range.

5 Content:

Every content item, no matter what type, has a content field. The channel can determine if this field should use the HTML editor or the code editor.

6 Summary Text:

A short description of the item.

OK, now that we have an idea of how dynamic content works, let's take a closer look at content channels and content channel items.

Channel Types

The first concept we'll discuss is channel types. As you work on your site, look for repeating data patterns. Items like web promotions are well-structured having data items like title, image, summary text, intended audience and content. While you could edit all of this content with the HTML editor, hopefully you can already see how that would be very tedious and prone to error. Here's where content channel types come into play.

Content channel types help define reusable data structures (think of a container for specific types of data). Rock ships with a couple of these channels already defined. Let's look at each one to see its role and purpose:

• Website Ads: This channel type is used to help manage your website promotions. It allows your staff to enter promotion information that your website administrator can approve, with the option to edit, and then publish to the site.
• Bulletins: This content type is used to help manage the bulletin creation process.
• Blogs: The blog content type is useful to build blogs for your organization.
• Universal Channel Type: This is a unique and powerful tool to help you from having to create 'One-off' channel types. We discuss this channel type in more detail below.

Anatomy of a Content Channel

As we mentioned before, the role of the content channel type is to define the container and settings for a particular type of content. Let's walk through the administration screen found under Admin Tools > CMS Configuration > Content Channel Types.

1 Name:

The name of the content channel type.

2 Date Range Type:

The individual content items that are added to the content channels can be valid for a specific date (for example a blog post would have a specific publish date) or a date range (a web promotion ad would be valid for a range of dates).

3 Disable Priority:

Some content items might have the concept of priority, while others may not. For instance, a web ad might be low priority (which would limit when and how it's shown), while a blog post would not need to use the concept of priority. This setting allows you to turn the need for priority on or off.

4 Disable Content Field:

This option allows you to disble or hide the content field, which can be really helpful if you want to simplify the screen view as you build your channel, or if you want to create a kind of blank template using only attributes.

5 Disable Status:

This option allows you to bypass the status and treat all content as "approved".

6 Channel Attributes:

This section allows you to define attributes that relate to the channel. For a blog channel this might be something like blog description, author, or image. Channel attributes aren't as common as item attributes; so don't worry if you have a hard time coming up with any.

7 Item Attributes:

Item attributes apply to each content item that is added to the channel. Each content item does get a date (either a single or date range depending on the Date Range Type discussed above) and a content field. Any other bit of information you want to track for the content item will need an attribute to store it. For example, the website ads channel has the following item attributes:

• Summary Text
• Image
• Detail Image
• Campuses
• Primary Audience
Secondary Audiences

Content Channels

If content channel types define the structure, content channels represent the implementation. Here's an example: you might have a channel type of Blog and channels Pastor Foster's Blog and Rock Solid Church's Blog that implement this type. You might be wondering why channel types are even needed. The answer is that they help enable reuse. In our blog example above, if you didn't have channel types you would have to define the structure every time you wanted to create a new blog - yuck!

When you create a new channel under Admin Tools > CMS Configuration > Content Channels, you have the following options:

1 Name:

The name of the channel.

2 Description:

A brief description of the channel. This description is available to be displayed on the page.

3 Type:

The content channel type that this channel is implementing.

4 Icon CSS Class:

A CSS icon class to be used on the various internal entry and administration screens.

5 Child Content Channels:

If content channel items are allowed to have child items this setting determines which content channel those items are allowed to be from.

6 Upload Blog Image:

This is where you can upload a logo or other image for the content channel.

7 Default Content Control:

This setting determines which editor should be displayed when adding content.

8 Items Require Approval:

Depending on your use case, you might want content items to require approval before they are displayed. This setting allows you to define this on a per channel basis.

9 Indexing Enabled:

Select this option if you'd like the content channel to be indexed.

10 Content Channel Item Publishing Point:

If you want to provide a direct link to the content channel, you can enter the URL into this Lava-enabled field.

11 Items Manually Ordered:

Many times content channel items will be ordered by date. Sometimes though, you'll want to manually order them. This setting enabled manually ordering.

12 Child Items Manually Ordered:

This setting determines if child content channel items should be ordered.

13 Item Attributes:

Content channels inherit all of the item attributes defined by the channel type. There maybe times when a specific content channel needs to add a new attribute specific to it's implementation. You can add these new attributes here.

14 Enable RSS:

This setting enables the channel's RSS features. This allows the content items to be published to an RSS feed that can be consumed by an individual's RSS aggregator or another software system that supports RSS integrations.

15 Enable Tagging:

Select this option if you'd like to allow the items in this content channel to be tagged.

16 Tag Categories:

If you select Enable Tagging, the Tag Category dropdown menu is displayed, allowing you to select which category of tags you want to use to identify the items in this content channel.

Content Channel Tags

Just as you can tag people in Rock, you can also use tags to help identify and categorize content channels. One small difference, though, is only organizational tags can be used with content channels (as opposed to personal tags), and those tags must belong to a category specified when the content channel is configured.

Let's take a closer look at how to set this up.

1. The first thing you need to do to start using tags with content channels is set up tag categories. Categories are created in the Category Manager, found at Admin Tools > General Settings > Tag Categories . Create as many categories as you want. Once a category is created you will need to add a Role to the secuirty under the Tag section for each. Otherwise added tags in that category will not be saved.



Using Categories

Each category will have a list of tags. Say you have a "Sermon" category and a "Podcast Sermon" category you would create two tags for each category. Tags are all about how you want to organize your Content Channel's. The power is in your hands to create the categories the way it makes sense for your organization.



2. The next step is enabling tagging in your content channels. Select the content channel you want to tag from the list found at Admin Tools > CMS Configuration > Content Channels, and click Edit to modify its configuration. Check the Enable Tagging box, then select the categories you'd like to be available for the content channel.


3. The final step is creating the tags you'll use with your content channel items. You can create as many as you need. Tags are created in the Tags screen, located at Admin Tools > General Settings > Tags. For each tag you create, use the Entity Type of "Content Channel Item" and select "Organizational" for the Owner. Leave the Qualifier Column and Qualifier fields blank. Alternatively, you can add tags directly from the content channel. You will be able to view and edit those tags in the general settings after they've been created if need be.

Now that your categories and tags are set up, you can add tags to content channel items. Simply type the tags you want to use in the "add tag" area of the Content Detail screen and click Save when you're done.

Content Items

Once you have your channels defined, it’s time to add content. You can do this in one of two ways:

1. You can enter content right on the Admin Tools > CMS Configuration > Content Channels screen under the channel details. This is more of an administrative screen.
2. Specific content entry pages can be found under Tools > Content. These are the pages that your staff will use to enter content, and your communications team will use to approve and manage entries. These screens are covered in the Communicating with Rock manual in detail.

The Universal Channel Type

As you start brain-storming ideas for using content channels you'll find yourself needing to create one-off channel types that will be used by a single content channel. For instance, when we set out to create the Lava documentation we first needed to create a new channel type called 'Lava Channel Type'. We could then add a new content channel 'Lava Documentation' that implemented that type. Creating the type for use with a single content channel was wasted effort, especially since content channels can add their own item attributes.

Hence the generic Universal Channel Type was born. This channel type is a generic type that you can use to build your one-off content channels from. It has no attributes defined so your channel will define all of the item attributes you need. No wasted effort.

Showing a Channel on a Page

Now that you understand how to create content channels and items, the next step is presenting this data out to your external website. The main block you will use to format channel content is the Content Channel View block. Adding this block to a page zone will allow you configure the following settings:

1 Channel:

The content channel you would like to display on the screen.

2 Status:

The content item status to filter on when creating a list of content items.

3 Format:

This is the Lava template selected to iterate through when displaying content items on the screen. See the Rock Lava documentation for tips and tricks on using Lava in Rock.

4 Items Per Page:

The number of items to make available for the Lava template.

5 Item Cache Duration:

Rock can cache the items returned from the database to help improve performance.

6 Output Cache Duration:

Rock can cache the page output as well. This improves speed, but is best used for non-personalized information. (You don't want to display a wrong name because the page is displaying cached output!)

7 Set Page Title:

This will set the page's title based on the channel content. By default, it will display the channel name. If the query string contains an item id (in the format of Item=1) then that item's title will be used for the page title.

8 Merge Content:

When this setting is enabled, the block will look for Lava fields in your content and attributes. Then, it will compile and render the Lava. This allows you to put Lava logic in your actual content. Think of the power of having blog posts that can actually be dynamic to the user reading them!

9 Detail Page:

This setting allows you to define the detail page to add as a Lava merge field. This allows your Lava template to link to the detail page.

10 Filter:

The content filter is very similar to the data view screens. This section allows you to filter by any attribute or property of the content item.

11 Order Items By:

Allows you to set the display order of the content items.

12 Meta Description Attribute:

This setting allows you to pick an attribute to use for the meta description tag in the page header. This description is used when people share the page on social media.

13 Meta Image Attribute:

Allows you to set the page’s meta image tag in the header to the select image attribute defined on the content channel.

14 Enable Query/Route Parameter Filtering:

When this setting is enabled, the block will try to determine the content item to display based on a query string or route parameter value (other than the default ‘Item’ parameter). For example if you set this property and then include “?Title=Car Show” in the url, the block will look for an item that has a Title of ‘Car Show’. You can also add an item attribute for your channel ("slug", for instance) and include that attribute in the route to this page (series/{slug}, in this case).

But Wait... There’s More

The settings above provide a ton of capabilities when adding dynamic data to a page. This block can also respond to specific query string parameters to alter its behavior. Let’s look at each of them:

• Item: If you pass in an item’s numeric id, the block will only load that specific item into the Lava merge fields.
• Page: If you have more items than fit on a single page, you can navigate between pages using the Page query parameter. Simply pass in the page number you wish to display. If you pass in a page number beyond the last page, the last page will be shown. If the page number is less than 1, the first page will be displayed.

Showing a Single Item on a Page

Your Content Channel View block is great for showing all of the posts in a channel, but what about a block to show a single content item? You can use the Content Channel View block and use an ID or Title parameter, but we really want more SEO-friendly URLs. Enter the Content Channel View Detail block, which brings you this and more.

This block gives you the option to "lock" it to a specific channel so that you can have a sermon series called "Moneywise" and a blog post titled "Moneywise" without having to worry about your pages getting confused about which item to show. To limit its search to a single channel, simply specify the Content Channel in the top input.

The Lava Template is the template which will be used to determine what shows up on the page. Initially, this will simply show the title of the item and the content below, but you can get really detailed in specifying how this page will be laid out. Using the Item object, you can access the properties and attributes of your content item for display on the page and even provide links to other pages.

In the Visitor Settings section, you can choose whether an interaction is logged every time someone views an item on a page with this block. You can also specify a Workflow Type that should be launched whenever this block is used to show an item. (The workflow will be passed a Person entity which you can use to store the person who viewed the page (if they're logged in). If your workflow has a Content Channel Item attribute with a key of ContentChannelItem, that attribute will be automatically filled in as well. You can use that attribute to discover which item they viewed, and optionally perform different actions based on that information.

The Social Media Settings section will let you link any item attributes you added to the channel to special meta tags on the page. For instance, if your blog post has an image they've provided in an attribute, you might want that image to be shown on the preview that appears in Facebook when someone shares your post there. But you might want to ask your post author to provide a different image for Facebook than the image for Twitter, so you can use these fields to specify which attribute will be used for each social network.

Finally, in Advanced Settings, you can specify what this block calls a slug, if you use that parameter in the URL. For example, if you wanted to provide a URL with ?sermon=MoneyWise at the end instead of ?slug=MoneyWise, you could type "sermon" into this box and it would look for an item with a slug matching the "sermon" parameter in the URL. (Of course, using parameters like this would break the SEO friendliness that this block was designed for, so it would be an unusual case that you would want to put anything in this field). Usually you'll just want to access the page using an address like "/sermon/MoneyWise" which would match a Page Route of sermon/{slug}.

You can also specify whether the output and the item content itself is cached to speed up page loads. You can also allow the item being viewed to set the page title so that your users aren't seeing a generic title like "Our Sermons" when they load a page that is showing a sermon called "Our Cloud of Witnesses".

Tips and Tricks

Below are some tips and tricks to help you maximize your usage of dynamic data:

• When you enable the ability to use Lava in content items, be sure that your Lava is set up to display data when the current user or other merge items are not available. When the content is made available via RSS, many of the merge fields will not be available.
• The RSS feed for a channel can be linked to from the address: http://yourserver/GetChannelFeed.ashx?ChannelId=N where N is the channel id.

Publishing Content Through Feeds

Once you enter your content, you may want to make it available through feed systems like RSS. Rock provides an endpoint that allows you to push your content in this way. The URL for this end point is:
http://yourserver.com/GetChannelFeed.ashx?ChannelId=X

The only required parameter is the ChannelId of the channel you want to publish. This channel must be configured to Enable RSS for the feed to return content.

The structure of the feed is defined by a Lava template. The RSS template is used by default, but you can create and configure additional templates to suit your needs. These templates are managed under Admin Tools > General Settings > Defined Types > Lava Templates. Once you create a new template, you can enable it by placing the TemplateId= parameter in the query string. The TemplateId will be the Defined Values Id. Note that the defined value can also set the MIME type that should be used with the template.

Other query string parameters you can pass into the handler include:

• Count: Limits the number of content items to return. The default value is 10.
• TemplateId: The defined value id of the Lava template you wish to use.
• EnableDebug: If present on the query string (with any value), the feed will output all available merge fields for you to view.

Child Content Channel Items

Content channel items can have child items. These child items can be from other channels. For instance, the podcasting feature in Rock uses this capability. The 'Podcast Series' content channel items are configured to have child items from the 'Podcast Messages' content channel. This concept is powerful as it allows the series items to have their own attributes and settings, yet they can work together to create robust applications.

When adding a child content channel item, you have the ability to select an existing item, or to create a new item. This is helpful as it minimizes the amount of clicking required to add child items.

Keep in mind that a single channel item can have more than one parent. Child items can also have their own children. The sky's the limit on what you can create.

What Are Landing Pages and Why Should I Use Them?

Landing pages are designed to drive people to a single focus, usually for a specific event or resource. For instance, you might set up a landing page with information about your Christmas services, to register for a conference, or to join a small group.

It's different from your external website's homepage because your homepage has a lot of information about your church in general, with links to more specific areas the visitor might be interested in. A Landing Page is designed to be self-contained, with very few links off of the page, and usually gives all of the information someone might need about the topic on a single page.

This is important because it helps you make sure that you're providing your visitors with exactly the information they're looking for, without making them search through your entire site for it. It's a better experience for them, and helps your message reach the people who are looking for it - talk about a win-win!

If your goal is to get your visitors to take a specific action, such as joining a group or filling out a form (referred to as a "Call To Action"), you'll be able to add those items to these pages as well so that they can take action as soon as they have the information they need.

A Sample Landing Page

Enough talk! Let's take a look at the sample Landing Page that comes with Rock and you can start to see what you can do with these types of pages.

1 Logo

The logo you provide in the site configuration will be shown at the top left of any of your landing pages

2 Headline and Hero Image

Each page will have a Headline zone where you can add an HTML block, for instance, and get your succinct "above the fold" message up front and center. The Hero Image is a page attribute, so you can specify the background for this area on each page.

3 Workflow

The sample page has a Workflow Entry block, showing you how you can provide a Call To Action to fill out a form. Check out the Blasting Off with Workflows for more information on building these forms.

4 Page Content

There are several zones in the main body of the page where you can add multiple blocks, such as HTML blocks, content channel blocks, etc.

5 Secondary Hero

Near the bottom of many of the Landing Page layouts is a secondary hero section. You can specify which image is used for each page on the page settings, and provide an HTML block or other type of block to display content and secondary calls to action over the image.

Getting Started with Landing Pages

Hopefully your imagination is already running with all of the ways you will be able to use these simple and beautiful pages! The best part is, all of the complex styling to get the text in the correct positions over the images is already done for you. All of the content on this sample page can be added using the HTML block WYSIWYG editor - no knowledge of HTML needed.

So, let's get started! Your Rock installation already has a Landing Page site with the LandingPage theme installed. Your landing pages will usually be a page on this site, rather than being an entire Rock site of their own. You can find this page from your internal site by clicking on Admin Tools > CMS Configuration > Pages and choosing "Landing Pages Home Page" in the menu on the left.

Now click the copy button shown below, and de-select "Include Child Pages".

Once the page is created, click Edit and you can fill in a little bit of information about the new landing page.

1 Page Names

Provide at least an Internal Name for the new page: this is the name you'll see for the page from the admin side of Rock. Frequently this will be the same name as you provide for the Page Title (which can be displayed on the page body itself) and the Browser Title (which is what the browser tab will be called when the page is loaded), but they can be different if you wish.

2 Layout

On a site using the LandingPage theme, you have more layout options than most of your other themes. Select the layout you want for this particular landing page here (refer to the below section for more information on your choices)

3 Header Image

This is where you can upload an image that this page will use as the background for the hero image at the top of the page. All of the fancy formatting is done for you- you just need to provide the image itself

4 Secondary Image

Some layouts have a secondary hero image near the bottom of the page (such as we saw in the sample Landing Page above). If the layout you selected above has this zone, you can upload an image here for it to use as the background.

Once you've updated all of the information for the new page, click Save. When the page reloads, you'll see a link to your new Landing Page, which will usually look similar to /page/123 . Click that link and you'll be taken to your new landing page, with the logo and graphics already in place, and content copied from the initial demo page, ready for you to edit as you wish.

Wasn't that easy? Now you can use the "Zones" button on the Admin Toolbar and start adding blocks and content to your page

More Information on Landing Page Layout Options

As we mentioned above, Landing Pages have a few more layouts than other site templates. Here are some thumbnails of the layouts available to you along with the available zones, so you can decide which layout to use for your new page.

Notice that some pages are designed not to scroll (those called "Simple") and will adjust to the height of the browser they're loaded on whenever possible. Most of the "Full" layouts have hero image sections based on the height of the browser (which is labeled "Viewport Height" on these thumbnails). You don't have to have content in all of the zones shown; they're simply available to you to make sure you can easily add any blocks to the page where you want them to lay out. Any of the layouts with two image placeholders will use both the Header Image and the Secondary Image you specify in the Page Attributes.

Let Dynamic Content Do the Work

The dynamic content tools discussed above can save you a lot of time by giving you an easy workflow for adding content to pages. Think of these tools as structured bits of content that can be scheduled to display on your site. On each page think about how dynamic content could be used to keep the content fresh.

Remove the Bottleneck through Delegation

It sounds scary but allowing your ministry leaders to edit their content on the website can be safe. The secret is in the configuration. Below are some tips to make this a success.

• Give the ministry leaders access to small pieces of content, not the whole page.
• Use the HTML editor's pre/post text to ensure that the wrapping markup cannot be changed. Say for instance you give the ministry access to edit a Bootstrap alert box on the page. Be sure that the markup for the alert is in the pre/post text so the user can not remove or edit it.
• Enable the HTML editor's approval system. This will allow you to review the changes before they are published to the site.
• Use security wisely. Don't give a single user access to edit a specific content block. Instead, consider creating reusable security roles (e.g. Website Editors – Childrens). This will allow you to add similar user permissions in the future.

Advanced Routes

So far we've looked at how to create simple routes. Pages that contain dynamic content might have one or more required query parameters to be able to display. Consider a page that displays calendar events. Its default route might be http://www.rocksolidchurchdemo.com/page/234?EventId=12. Creating a route with the value of Event/{EventId} would add the ability to load the page with the address of http://www.rocksolidchurchdemo.com/Event/12. This new address is not only visually more appealing but is also SEO friendly.

You can add as many query parameters to your route as you like. For instance, the route of Event/{EventId}/{TabId} would enable the address of http://www.rocksolidchurchdemo.com/page/234?EventId=12&TabId=3 to be represented as http://www.rocksolidchurchdemo.com/Event/12/3.

If you would like to manage all routes defined in Rock you can see them listed under Admin Tools > CMS Configuration > Routes. From here you can edit or delete any route in the system.

Routing Order

Rock uses the following order to choose what page is displayed for a provided URL. In cases where there is no matching route on a given site the oldest matching route from any site is used.

1. Page ID (/page/12)
2. Matching page route and matching site
3. Matching Shortlink and matching site
4. Oldest matching page route from other site
5. Oldest matching shortlink from other site
6. Page not found (404)

Creating a new site in Rock is simple. But, it helps to do things in the proper order. Following the steps below will lead to a well-configured site every time.

1. First, navigate to the site list page Admin Tools > CMS Configuration > Sites
2. Click the (add) button at the bottom of the grid of sites.
3. Fill in the site configuration outlined below:



1 Name:

Provide a name for your site. This name will not appear on the site itself, just the admin screens used to support it.

2 Description:

Provide a description for your site.

3 Theme:

Select a theme for your site. If your theme is not yet ready, we recommend that you pick the Stark theme basic template.

4 Default Page:

Important: We highly recommend leaving the default page blank. If you do not provide a default page, Rock will create it for you at the root page level with all the right settings. Creating this page before the site can cause misconfiguration.

5 Login Page:

Each site defines its own login page. This page will be used when an unknown user clicks to a page that requires additional security. You do not have to select one at the time of creation. You may wish to configure this later.

6 Domain(s):

In order for Rock to serve up your site, it needs to know what domains (e.g., www.rocksolidchurchdemo.com) it represents. You can provide multiple domains in this field delimited with a comma.

7 Error Page:

Let's face it, errors happen. Instead of displaying the default Rock error page you can design and show a custom page for your site.

8 Google Analytics Code:

You might want to integrate your site with Google Analytics. Rock makes this simple by allowing you to provide your site's Google Analytics code. We'll do the rest.



1 Change Password Page:

This setting will determine the page to link to for changing the password.

2 Communication Page:

The Grid uses this setting to determine what page to redirect the user to when clicking the New Communication button at the bottom of a grid of people.

3 Group Registration Page:

The group registration page setting is not yet implemented in Rock.

4 404 Page

You have the option to provide a custom page not found (aka 404) page for your site. This too can be set at a later date.

5 Require Encryption:

This setting will require that all pages on this site load with SSL encryption. If a page is attempted to be loaded with http, Rock will redirect it to https.

6 Enable Shortening

Should this site be available when creating shortlinks?

7 Site icon:

If you want your site to have a site icon (aka, 'favicon'), upload it here. The recommended image size is 192x192. Rock will automatically create all of the sizes required by different browsers and devices based on the image you supply. Once uploaded, you can turn the icon on and off for individual pages by checking the Site Icon box in each page's properties, accessed in the Admin Toolbar. Similarily, there's an option to upload a site logo, which some themes use to apply some change to a site. See the theme's documentation for sizing information.

8 Page Attributes:

This is where you can add attributes to the pages of your site. Page Attributes apply to all of the pages of the site, but each page has its own value for each attribute. To learn more, see the Page Attributes section below.



1 Enable Mobile Redirect:

This checkbox enables mobile redirects. This allows you to route your mobile users to a different page or site if they visit any page on this site.

2 Log Page Views:

This setting determines if each page view of this site should be tracked. This allows you to gain valuable metrics about a page AND more importantly about your guests' activties and interests.

3 Page View Retention Period:

If page tracking is enabled, you can set how long the page views are stored. You'll find that for popular sites this data will grow quickly. You may want to limit how much of it you keep.

4 Allowed Frame Domain(s):

If you need to allow an external site/domain to be able to embed your site (such as in an iframe) just enter each domain as a space delimited list. Rock will then take care of sending the correct page headers that block all sites not in the list. The value you enter here will be used for the <source> as described in Content-Security-Policy frame-ancestors directive.

NOTE: Your Rock URL must also appear in this list otherwise you will lock yourself out of Rock's modal popups (such as the HTML editor, block settings, etc.) Therefore, if you wanted to allow www.yoursite.com to be embedded on www.xyz.com, you would specify the following in your list:
http://www.yoursite.com https://www.yoursite.com http://www.xyz.com https://www.xyz.com

5 Page Header Content:

The content provided in this field will be added to each page's head section. This is one area where you can do a lot of interesting customization of your site by using page attributes. For more information, see the Page Attributes section below.

6 Allow Indexing:

This setting will enable or disable the pages of the site from being indexed by web indexes such as Google an Bing. If you disable indexing, Rock will add <meta name="robots" content="noindex, nofollow"> tag in the page header to keep web indexes from crawling your site.

4. Once you've provided the above information and clicked Save, your site is ready for the next step, which is to start creating pages. The best way to get to your new default page is to use the Page Map under Admin Tools > CMS Configuration > Page Map. From here you can click on your default page.

Page Attributes

The Page Attributes section of the Add Site screen is an advanced setting that gives you a ton of control over your layout of your site. The attributes you create here will apply across all of the pages of your site, but each page will have its own attribute value. For example, you create an image attribute for a page, then dynamically access that attribute in your header, as shown in the following sample code:

                <script runat="server">
                    protected void Page_Load( object sender, EventArgs e )
                    {
                    var page = ( RockPage ) this.Page;

                    var bannerImage = page.GetAttributeValue( "BannerImage" );
                    headerMainText.InnerHtml = bannerImage;
                    }
                </script>

                <header id="headerMain" runat="server">
                </header>

One Thing You Must Do

If you can only do one thing, we highly recommend adding a description to each page you believe will be shared on social media. This is quick and easy to do by accessing the Page Settings from the Admin Toolbar at the bottom of each page.

Without a page description, the social shares will try to figure out a description for your page by stripping the first chunk of text from your page that looks to be the main content. But why make the social networks guess when you can give them the exact description you'd like?

Getting Deeper

Setting the Page Description is nice, but that's just the start. Each social network allows you to describe how your page should be shared using meta tags in the page's header. Unfortunately, there is little consistancy in how this is done. Below we show you how to optimize each page's social network share information using Lava. Simply put these tags in any HTML block on the page and your site will be socially beautiful.

Adding Make Up For Facebook

Let's start with Facebook. The three main attributes you want to set for an attractive Facebook share are the title, description, and an image. Below we show you the Lava for each. Again, these Lava statements can be on any HTML block on your page.

• Title {{ 'Title for Page Here' | AddMetaTagToHead:'property','og:title' }}
• Description {{ 'Description for Page Here' | AddMetaTagToHead:'property','og:description' }}
• Image {{ 'URL to image here' | AddMetaTagToHead:'property','og:image' }}
  Note: You'll need to upload the image to the website and link to it for the URL. Your image should be sized to: 1200px x 630px.

After setting these values, your share should look something like the example below.

Don't simply trust that it'll look right though. Use the Facebook Share Validator to see your formatted share along with tons of debugging information.

Terrific Tweets

Just like Facebook, Twitter has several custom page attributes for you to use to make great looking shares. In fact, Twitter allows you to control even more settings. Let's take a look at the basic settings and we'll move on from there.

• Title {{ 'Title for Page Here' | AddMetaTagToHead:'property','twitter:title' }}
• Description {{ 'Description for Page Here' | AddMetaTagToHead:'property','twitter:description' }}
• Image {{ 'URL to image here' | AddMetaTagToHead:'property','twitter:image' }}
  Note: You'll need to upload the image to the website and link to it for the URL. Your image should be sized to: 440px x 220px (well that's one recommended size at least, read on...)

Very similar to Facebook, no? But wait... there's more... Twitter allows you to define 2 different formats of shares which they call summary cards. One card has a large image and the other a smaller.

Large Image

{{ 'summary_large_image' | AddMetaTagToHead:'property','twitter:card' }}

Small Image

{{ 'summary' | AddMetaTagToHead:'property','twitter:card' }}

Twitter also has a helpful validator to help visualize what your share will look like. You can also read more about what's possible by reading their documentation.

Calendar Events

Of all the content on your site calendar, events are probably one of the most shared types of content. To assist you in making this easy we've added the social attributes Lava above in the Lava templates for calendar events. We've also added two new event attributes on the public calendar to help you upload specifically formatted images for both Facebook and Twitter. If you've created a custom theme before Rock v6, you'll want to copy and paste this Lava code into yours.

Bootstrap

Bootstrap is a front-end framework that brings consistent styling to Rock. We are currently using Bootstrap version 3.3.7. Whether you're tweaking content on a page or writing a custom template, you’ll want to get familiar with the standard HTML/CSS mark-up that Bootstrap provides. Reading through their excellent documentation in its entirety is a great way to get started.

Font Awesome

Rock uses icons in several areas of the application. These fonts all come from the Font Awesome library. Since these icons are all font-based vectors, they can be colorized and resized very easily. To see a listing of all the icons in the collection visit http://fortawesome.github.io/Font-Awesome/.

jQuery

jQuery is a Javascript framework that's used by a majority of Internet sites. If you’re only interested in making minor changes it’s likely you'll never need to work with jQuery, but if you plan to make custom themes or blocks, you'll want to get familiar with it. Rock currently uses version 3.3.1. You’re welcome to use a newer version in your theme, but be sure that your version is backwards compatible to 3.3.1 to ensure Rock's core jQuery plugins work correctly. You can find out more about jQuery at jquery.com.

Less

If you're familiar with Cascading Style Sheets (CSS), you've probably experienced the frustration of repeating selectors and duplicate color definitions. Less blends a programming language and CSS. It offers concepts like reusable variables and object-oriented mix-ins. If you're worried about learning another new technology, don't be. Less is super simple. Soon you'll be able to brag to your friends about your knowledge of Less! You can read up on what's available in Less at http://lesscss.org/.

Liquid

Liquid is a templating engine written by Shopify. We've extended and customized Liquid in Rock to form our own templating engine called Lava (get it... liquid rock...). You've already been briefly exposed to the power of Lava in the introduction of this manual. Lava is used in several places in Rock, so it's worth your time to learn it well. Below are just a few of the places it's used:

• HTML Editor: Used for dynamically mixing in personal merge fields with your content.
• Menus: Navigation menus and page lists use Lava to assemble the HTML that is used to display them on the page.
• Email Content: Emails and SMS communications use Lava to personalize their content.

Learning Lava will make you feel like a superhero. Definitely take the time to master it. We've provided some great resources for you to learn Lava on our website.

Lava Shortcodes

Shortcodes are a way to make Lava simpler and easier to read. They allow you to replace a simple Lava tag with a complex template written by a Lava specialist. This means you can do some really powerful things without having to know all the deals of how things work.

For example, instead of writing out Lava code to display a Google map with custom pins and styles, you can insert a Lava shortcode where you want the map to be displayed, and let Rock do the work for you. Rock will replace the shortcode with the full Lava code, which will then be displayed as a customized map when rendered by the browser. Shortcodes put the power of Lava in your hands without you needing to be a coding expert.

To learn how to create and use Lava shortcodes, check out The Long & Short on Shortcodes.

Methods to Compile

Theme List

You can view a list of installed themes under Admin Tools > CMS Configuration > Themes.

1 Theme Name

Pretty obvious…the name of the theme.

2 Allows Compile

A theme designer can keep a theme from being compiled by Rock. This is rare and is usually only done for internal themes developed for a specific organization.

3 System

This notes that this theme is a system theme that came with Rock. These themes cannot be deleted.

4 Compile

This button allows you to manually compile a theme.

5 Clone

This button allows you to copy the theme to a new theme with a name of your liking. This allows you to change it without worrying about effecting others.

6 Delete

This button allows you to delete the theme.

Theme Styler

Selecting the theme from the list will take you to the Theme Styler. Below is the theme styler for the default internal Rock theme.

1 Theme Variables

You'll notice that theme designer has provided several variables for you to modify. These variables allow several different customizations. Some you'll notice allow you to choose colors. Others modify fonts, images and units of measure.

2 Variable Refresh

After changing a variable you'll notice a small x next to it next time you enter the theme styler. Selecting this x allows you to return the value back to its original state. Be creative… you can always go back to the default if you don't like your selection.

3 CSS Overrides

You may find that there is no variable for the change you want to make. Never fear, you can enter any overriding CSS in this box. It will be placed at the bottom of the compiled CSS to ensure that it gets the last say on how an element should be styled.

4 Save

Pressing the save button will not only save your changes, but also compile the Less file to CSS. If you're editing the internal Rock theme you'll notice your changes right away!

Free vs. Pro

Font Awesome has always been free and will continue to be so. In version 5 they are also offering a Pro version. The Pro version gives you not only tons of new icons, but different weights (solid, regular and thin) as well. While the free version does have two weights, only the solid weight is icon complete (has all the icons implemented). Because of this, “solid” is the only choice in Rock if you have the free version.

Installing Font Awesome Pro

If you do purchase the Pro version (again, this is completely optional), you'll now need to install it in Rock. To start, you will need to log in to your account at fontawesome.com. You'll need to get both your Key and the Pro Download file. See the below screenshot to make sure you're getting the right items:

1 Key

First, take note of your Font Awesome Pro key in the "Licenses" section. You'll need this in a minute

2 Download link

Next, click the download link for Font Awesome Pro from the "Products & Services" section.

3 Pro for Web

You'll need to click on the "Pro for Web" file on the page that opens, shown here.

Now that you have your key and the .zip file, log in to your Rock site and navigate to Admin Tools > CMS Configuration > Font Awesome Settings. This is where you'll paste in your Font Awesome Pro Key and upload the Font Awesome Pro for Web package that we just downloaded. Then click Update and it will tell you that Font Awesome Pro has been updated. You'll need to do this again from time to time as Font Awesome adds new icons to their Pro package.

Font Weights

As we mentioned above, you need the Pro edition to have access to the various font weights in Rock. Currently, there are 3 weights: solid, regular and thin. It's our intent to allow you to pick a weight and have the theme auto update to show your selected weight.

Each of the weights is implemented in a separate font file. There is also a separate font file for all the brand icons. To reduce page load times, we allow you to select which fonts you’d like to implement on your theme.

Font Awesome 5 added the ability to specify the weight of the icons in CSS. So, if you wanted a light icon, you’d use “fal fa-cog.” However, this hard-codes the icon to always be light. Instead of using the weight classes, we highly recommend that you continue to use the normal fa prefix (e.g. fa fa-cog). This will allow Rock to dynamically change the weight based on administrator preference.

SVG Fonts

You might be asking, "What about SVG fonts? There are a bunch of new features that only they support!" At this point, we have not supported the Font Awesome SVG fonts natively in Rock. While that might change in the future, the community felt that the increased file sizes of the SVG font files was a concern and that the traditional font files were a better option for now. We hope that Font Awesome will have a solution to these concerns in the future.

Other Features

Font Awesome 5 has a ton of other features that you should read about on their How To Use page.

Custom Themes

If you are writing a custom theme you can select to either hard code your theme to use a specific weight of Font Awesome or plug into Rock’s theme customizer to allow Rock Administrators to update it from the UI. Both options are discussed below. Note that if you don't do anything, Rock's core Bootstrap implementation will include the solid weight for you.

@import "../../../Styles/FontAwesome/_rock-fa-mixins.less";
.fa-font-face( 'thin' );

Contents of a Theme

• The .system file tells Rock that this theme is a system theme. This prevents it from being deleted in the Themes list.
• The Assets folder is used for all of the images, icons and other support files needed by your theme. This folder also contains a Lava child folder for all of the Lava files needed for your theme.
• The Layouts folder contains all of the layouts your theme supports. For external sites, your theme should define implementations for all of the standard layouts covered in the Looking Deeper At Layouts chapter.
• The Scripts directory will be used for any custom scripts your theme requires. Be sure to only place unique scripts here that are not contained in the global scripts folder.
• Finally, the Styles folder contains all of the files needed to generate your CSS. Specifics of these files is discussed in depth below.

Stark

No, this is not our Ironman theme, but this theme will become your go-to for custom theme development. Stark gets its name from the fact that it is basic and minimally styled. In fact, it comes with the least amount of styling possible. We created it as a starting point for you to create new works of art. Think of it as your blank canvas.

To start a new theme you should start by copy/pasting the Stark theme and then renaming it. Then start restyling the theme using the .less files.

How Rock Uses Less

There are two sets of .less files. Those in the core Styles folder and the theme .less files. The purpose of the core styles is to provide the basic structure and look/feel to the various Rock blocks. The theme's .less files add the final polish to the blocks and override any of the CSS attributes you desire. Let's take a quick look at each Less file that makes up a theme.

• .nocompile: This file tells Rock's Less compile tools to ignore this theme. This file should only be used in cases where a custom theme designer wishes to manually compile the theme's Less files (rare).
• _css-overrides: This file contains the Theme Styler's CSS overrides. It should not be manually edited.
• _print.less: This Less style file helps set specific print styles that make Rock pages look better when printed. The contents of this file are imported (appended) into the theme.less file. For the most part, you should not need to modify these styles unless there is a specific print styling you would like to add.
• _variable-overrides: This file contains the Theme Styler's variable overrides. It should not be manually edited.
• _variables.less: This is a very powerful file. It contains a rather large list of style settings that you can change. Simply changing a couple of colors can make your theme match the brand colors of your organization. We highly recommend that you make a copy of the Stark theme and start playing with the variables in this file. You’ll be surprised how easy it is to make some dramatic changes.
• bootstrap.less: This is the core Bootstrap Less file. You should not change this file. If you need to modify a style setting in Bootstrap you should either identify the variable that Bootstrap uses to control that style in the _variables.less file or write a specific override in your theme.less file.
• theme.less: This is the file that contains all of your theme's custom styling. If you can’t style it with a variable change in the _variables.less file it should be added here.

Once you make changes to your Less files, you’ll need to compile them to .css files for the browsers to use. There are a number of Less compilers you can use for this.

Themes Are More Than Looks

Keep in mind as you develop your theme that you need to be concerned more than than just how your theme looks in the visitors browser. You should also be testing to ensure your theme works well with Rock's in-page editing features. Zone and block editor features should work well with your theme to allow web administrators access to edit the pages.

To help you with this Rock will add classes to the <body> tag when the zone and block editors are enabled. These classes are 'zone-highlight' and 'block-highlight' respectively. With these classes you can adjust your layouts when these editors are at work.

Rock will also add the class 'modal-open' to the <body> tag when a modal is open. This allows you to do special styling when this event occurs.

Lava

Every theme should include some implementations of the standard Lava files in the theme’s ./Assets/Lava folder. Each of these files is covered below.

• AdList.lava: This is used to render HTML for the various lists of ads on pages.
• AdDetails.lava: This is used to render HTML for the details of a specific ad.
• AdRotator.lava: This provides the markup for the large ad rotator on the homepage.
• BlogItemList.lava: Renders markup for a list of content channel blog entries.
• BlogItemDetail.lava: Renders markup for a content channel blog entry.
• PageListAsBlocks.lava: This lava is for rendering a list of pages as blocks like the ones on the various Admin Tools pages.
• PageListAsTabs.lava: This renders markup for showing a list of pages as a Bootstrap tab or pill navigation.
• PageNav.lava: Used for a page's main navigation.
• PageSubNav.lava: Renders markup for a page's sub-navigation.
• RSSFeed.lava: Renders markup for a content channel RSS Feed.
• RSSFeedItem.lava: Renders markup for an item in a content channel RSS Feed.

Testing Your Theme

As you're working on your theme you might be wondering how you can view it without everyone seeing what you’re working on. Well prepare to have your mind blown. Because you're a Rock Genius, you know that when a page loads it gets the active theme by looking at the site's theme setting. Pretty simple. You can, however, override this setting by adding the query parameter theme='themename'. For instance if your page is available at:

http://www.rocksolidchurchdemo.com/page/1
you can have that page display your new theme by typing in:
http://www.rocksolidchurchdemo.com/page/1?theme=MyStarkTheme

The best part is that only you will see it. Everyone else will see the current theme defined on the site. Pretty James Bond, huh?

As an example to the warning above if you're using certain CSS filter you may find that you need to escape them. For instance if you add the CSS below:

.item { filter: blur(8px) !important; }

You may find that your compiled CSS is blank. To fix this you'll need to escape the filter using by appending a ~ and wrapping the filter in quotes like:

.item { filter: ~"blur(8px) !important"; }

Theming for the Styler

As you have already seen, Rock's Theme Styler is a powerful tool for allowing others to edit your theme. It's easy for you to enable others to change your theme by making a few small changes to your _variables.less file. Below is a side-by-side comparison of the _variables.less file for the internal Rock theme and the UI created from it in the Rock Styler.

Let's look at a few lines to see how the _variables.less file is magically transformed into this nice editor.

• Line 1: Adding a '//' followed by text will create a new variable grouping. To turn this grouping into a panel in the styler you'll also need to append *show in editor*. This allows you to also create groups that are not editable.
• Line 2: Line two and we're already adding our first variable. The label for the variable will be the variable name (minus the @ character). All dashes in the variable names will become spaces. The values in the comments will be used for the help text. Finally, if the comment ends with #color, Rock will render it as a color field. The color field is smart enough to render as a plain 'ol textbox if it contains less functions like darken.
• Line 4: Placing the characters '//--' will insert line breaks in the editor. This allows you to easily sub-group your variables.
• Lines 7-28 These lines were omitted to simplify the illustration.
• Line 29: Note that there is no end marker for variable groupings. When you're done with one, simply start a new one.

Lava On Layouts

As you create your themes and layouts you might start to see a pattern of having to create HTML blocks to provide content that won't change often. For example you might add an HTML block at the top of every page to place an image from a page attribute, or some sort of welcome message. Luckily, there is a way of adding content using Lava right on your layout. (You've always been able to do these types of things in C#, but honestly, who wants to resort to C#?!)

When creating your layouts you can add Lava right in your .aspx files. To do this use the Rock:Lava tag. Below is a quick example of what you can achieve.

<Rock:Lava ID="lavaHeader" runat="server">
    {{ CurrentPage | Attribute:'HeaderImage' }}

    {% if CurrentPerson %}
        Hello {{ CurrentPerson.FullName }}
    {% endif %}

    {% cache key:'external-header-grouplist' duration:'3600' %}
        {% sql %}
            SELECT [Id], [Name] FROM [Group]
            WHERE [GroupTypeId] = 25 AND [IsActive] = 1
        {% endsql %}

    
        {% for group in results %}
            {{ group.Name }}
        {% endfor %}
    {% endcache %}
</Rock:Lava>

The example above is a bit of a kitchen sink script showing all sorts of functionality. Let's look at some of the features packed in there to see what's possible

• Page Attributes: One of the best uses of Layout Lava is interacting with page attributes. It's a great idea to add a page attribute for things like page header images. You can then place them right on your layout. Bonus points if you provide a default image in your attribute settings so if a page doesn't provide an image a default one is used instead.
• Custom Messages Remember, this is Lava. You have access to common objects like the CurrentPerson. Use this for your fame and fortune.
• Lava Commands We assume that anyone who is allowed to edit a file on your server has administrative rights (because they do, if your can edit a file on the web server you can pretty much do what you want if you know C#) so we've enabled all of the Lava commands when using Lava templates on the layout. This simple example lists all active small groups using the SQL command.
• Think Speed You want your website to be fast right? Think about how you can use the Lava cache tag to remember content that comes from the database. In this case we cache the group list for one hour (3600 seconds). Be careful though. You don't want to cache personalized messages, or if you do use the two-pass option in the Lava cache command.

Rock Folders

• App_Browsers/ – You should not need to worry about this directory. It's a special directory that allows ASP.Net to identify specific browsers and determine their capabilities.
• App_Code/ – This directory contains un-compiled code for Rock. You do not want to alter or add files in this directory.
• App_Data/ – This directory allows you to store data without having to worry that a client could browse directly to it. For instance, Rock writes a log of severe error messages to this directory (specifically ~/App_Date/Logs/RockExceptions.csv). But, because the webserver blocks requests to access these files directly, you do not need to worry about someone being able to access them. You'll also notice that Rock keeps a cache of binary files in ~App_Data/Cache/. For the most part you don't need to know about this, but it’s good to know how things work under the hood.
• Assets/ – This is the global assets folder where Rock stores images, icons, fonts, etc. that are a part of the core install. You should refrain from storing your files in this directory.
• Bin/ – ASP.Net keeps its compiled assemblies (aka .dlls) in this folder. If you have custom plugins with compiled assemblies, you'll want to add them here. Keep in mind that if you add/modify/delete any file in this directory Rock will restart which could impact people using Rock at the time. You should only do this after hours.
• Blocks/ – These are the core Rock blocks. As you can see they are organized by function. You should not modify any of these blocks nor add your own. This location is reserved for the core blocks.
• Content/ – This is where you'll add your custom content for your various sites. While it's up to you to determine the best file and folder structure, we recommend that you at least keep the content for the various sites separate. Over time these folders can get quite messy so it's best to come up with a good filing structure from the beginning.
• Plugins/ – The plugins folder is where you'll place all of your custom blocks. The organization of the files in this folder is very important. To help keep things straight the following pattern should be used.



1. The top-level should start with a reverse domain organization notation. For instance if your organization uses the domain rocksolidchurchdemo.org your top-level folder should be org_rocksolidchurchdemo.
2. Under your root folder you’ll have a child folder for each plugin that you develop.
3. Under the plugin folder you’ll have folders for things like Assets, Styles and Scripts. You’ll also put the blocks themselves in the root folder.
• Scripts/ – This is the core scripts folder. You should not add scripts to this folder. Instead add your scripts to your custom theme folders.
• Styles/ – The styles folder is for Rock's core .less files. You should not edit these files as they will be overwritten during updates. If you need to modify the properties of a certain style you should override them in your custom theme files.
• Themes/ – This is the location of all the themes for your Rock install. See the chapter Working With Themes for more information on themes.
• Webhooks/ – Webhooks are HTTP handlers (Web 2.0 geek-speak for very basic webpages) that receive requests from Internet services like Mandrill and Twillio. For instance, Twillio will call a specific webhook every time someone responds to your SMS message to notify you of the details of the response. When you write a custom webhook you can place it in this folder.

Couple of Important Files

While we won't cover every file in the root Rock folder, below are a couple that you should be aware of.

• License.aspx: Rock uses several open-source projects in its core. Attribution for each of these projects is given here. We also note each of their licenses so as to show that our license (Apache) is not in conflict to theirs.
• Web.config: This is the core settings file for any ASP.Net application. Unless you know exactly what you're doing you should stay away from editing this file. Keep in mind that any change to this file will cause Rock to restart.

File Manager

The file manager provides a basic interface to help you to upload and delete files and manage directories without having to setup or share FTP credentials. Its root folder can be configured allowing you to enable a specific user or security role to manage a specific part of a folder heirachy. By default a File Manager block can be found Admin Tools > CMS Configuration > File Manager.

Tips for Creating Your Form

When you're creating your form you can use any HTML you'd like. We provide an inclusive sample that shows you many of the advanced features. Below are a few points to consider:

• You have access to Lava in your form. If the guest is logged in, you can personalize your message.
• If they are logged in you can also pre-enter many of the fields. In some cases you may want to simply add their name to the name field and allow them to change it. In other cases you can put their information in as text that can't be changed. When you do this you can pass the value of their name in a hidden field. The sample shows both cases. It's up to you to determine which one will work best.
• Your email form can include attachments. This is shown at the bottom of the sample form.
• You do NOT need to have an HTML tag in your markup. Don't add one or you'll break the page.