A Block is a container that allows you to add additional content to a region in your page. You can add images, contact information, a list of related links, an event promotion or anything you’d like to feature!

Blocks can be:

• dynamic or static; generated as a Block display in a View, on-the-fly by various modules, or created with static text/images.
• configured to display on specific pages, content types, and/or for specific people or types of people (roles).
• assigned to the various Regions on your site.

Adding a Block

Create Blocks based on the needs of a specific site structure.

1. Select Structure -> Blocks from the Administrator’s toolbar.
2. Click on the + Add block link above the list of links.
3. Enter the name of the Block in the Block title; this is shown as the title of the block to the user when placed in a Region.
4. Enter a description in the Block description; this is shown on the Administration page to identify the Block.
5. Enter text and images in the Block body. 
   
    
6. Scroll down and select the Regions you want this block to display on.
   
    
7. Indicate the pages you want the block to display/not display, Content Types it should be available for, and/or the Roles who should be able to see this block.
   

Editing Blocks

You can easily edit the content in any Block using the Gear icon that is a new feature in D7. Simply hover over the upper right corner of your Block. A contextual menu displays with options available based on the type of block you are working with:

• Menu - List links, Edit menu, Configure block
• View - Edit view, Configure Block
• Block - Configure block

Select the option Configure block and it brings you to the configuration area for that specific block.

Menus are a set of links that allow site visitors to locate content on your site. When a Menu is created it is available as a Block and can be placed in the various regions of your site. Like Blocks, menus can be configured to display on specific pages, content types, and/or for specific people or types of people (roles).

There are two menus you can use to manage your navigation.

• Main Menu – the main navigation of the site that displays across the top of your site.
• Sub Menu - links that appear in your left navigation.

Adding a Menu

You can also create additional menus based on the needs of a specific site structure.

1. Select Structure -> Menus from the Administrator’s toolbar.
2. Click on the + Add menu link above the list of links.
3. Enter the name of the menu and a description (optional)
   

Adding a Link to your Menu

Once your menu is created you can add an item to it. These steps are useful for adding links to files or pages outside of your site. If you are adding new pages to your site, you could add them to the menu as you create the pages. (See Add your page to a Menu)

1. Click on the + Add link 
   
2. Enter the text you want to display as the link in the menu and the path to the URL you want the link to open.
   • for pages within your site enter a forward slash (/) and the URL (/url-path see example below)
   • for pages outside your site, enter the full URL including http://
3. The Parent menu defaults to the menu you have just created.
   
4. Scroll down and Save the menu link.
5. Repeat for each menu item you want to add.

Opening External Links in a New Window

If you add a link to an external site, it is recommended you open that link in a new window. To do this, you need to enable the Menu Attributes module. Once enabled, you can configure each link to open in a new window. 

Rearranging the Order of Menu Items

Once your menu has been created, you might want to rearrange the order. Simply:

1. Go to your Menu - Structure > Menus or click on the Gear Icon and select List Links.
2. Press, hold and drag the 4-pronged arrow to the desired location.
3. To create child or sub menus, drag the item over and under the item you want to be the main item.
   

Taxonomy is a way to categorize your content using “tags”. Once tagged, the content can be grouped and listed based on the terms associated with the content.

A Taxonomy group is called a Vocabulary; a specific tag is called a Term. Once a Vocabulary is created, Terms are added. Then the Taxonomy can be added to the Content Type as a Term Reference field type.

To add Taxomony Vocabulary

1. Select Structure > Taxonomy from the Administration Menu.
    
2. Click on Add vocabulary and add the name for the Vocabulary (description is optional).
   
3. Click on Add terms and add terms and term name
   
4. Enter the name of the term, scroll down and click Save.
5. Repeat this process until you have all the terms added. 
6. You can create a hierarchical list of terms by selecting the parent term before saving.
   
7. When you are done, you can rearrange as desired using the arrow icon and dragging the term to the appropriate location.
   

Different types of content have different meanings. Content Types allow you to define the content on your site using fields to capture pieces of information independently of one another. Each Content Type is treated differently; different properties, fields, page displays, etc. With Content Types, you can arrange what and how you want your content to be displayed as well as control who manages and creates that type of content.

Your YaleSite has built-in features that provide Content Types to make it easier for you to create, update and display your information about your department or organization. In addition to creating basic pages with the Basic Page Content Type, you can create the following types of content providing the features are enabled on your site:

• Basic page
• Event
• News
• Private Files
• Rotating Header Image
• Slideshow
• Video

Your YaleSite automatically creates friendly URLs using Clean URLs and the Path Auto module. When you create and save a page, the URL is translated to the title of the page, replacing spaces with dashes (-) and eliminated words with three letters or less (a, and, the, etc.).

However, there may be times when you want more control over the path generated for pages you create with specific content so that it follows a logical path. For example, you might want to have the URL alias for faculty member pages begin with the word “faculty” – sitename.yale.edu/faculty/john-smith. This can be done with the Automated URL Alias feature. This is especially important to ensure blocks display on specific pages using the shorthand academics/* (all the Academic pages get the Academic Menu Block).

YaleSites URL Alias Settings

It is important to note that URL aliases are set for the Basic Page Content Type and Content Types for other pre-built features.

• The pre-built features are set to define the path starting with the name of the content Type
  • sitename.yale.edu/news/news-item-title or sitename.yale.edu/gallery/senior-class-field-trip.
• The Basic Page Content Type using a token that allows you to create pages based on the menu structure. So if you are creating a Basic Page and select Academics as the “parent” menu item, your URL alias would be:
  • sitename.yale.edu/academics/page-name

If the “parent” is Graduate Programs under Academics (see Sample Hierarchy above) the URL would be:

• sitename.yale.edu/academics/graduate-programs/page-name.

Creating a URL Alias

If you create your a Custom Content Type you will need to assign a URL alias to that Content Type if you want to defined the path of the URL:

1. Go to Configuration -> Search and metadata -> URL Aliases from the administration toolbar.
2. Click on the Patterns tab. There you will see several options for creating URL aliases based on the type of content you are working with.
3. Select Node paths to create URL aliases for specific types of content.
4. Build the path you want to create: Type words to define the base “folder” or “directory”.
5. Use tokens/replacement patterns to build the rest of the URL string:
   • [node:title] - title of the page
   • [yyyy]/[mm]/[dd] - date the page was created
   • [node:author] - author name
   • [term-raw] - taxonomy term
6. Save the configuration. As you create your pages, the URL paths will automatically be built to match your configuration. 

Important Note: This is an important step when creating any Content Type to ensure the URL alias is set as content is created. Pages created prior to URL alias setup do not automatically update to the new URL alias.

Views are a powerful and flexible way to list and display content. Views can be used to create lists, generate reports, create summaries, and display collections of images or other content. The Views module provides a GUI interface allowing technical and non-technical people to build simple and complex queries with little or no coding. Data is entered once in a Content Type, displayed in various filtering formats and re-purposed throughout the site.

For YaleSites, the custom Views are listed under Structure ->Views in the Administrators toolbar.

Creating Views

Views is a very complex process that requires more than this one page tutorial. However, these instructions will give you an overview of the basic setup.

1. Click Structure -> Views -> Add View
   
2. Enter the View name, path, choose the format and indicate you want to list fields.
3. Enter the number of records to display and Menu options.
4. Scroll down and enter similar information for a Block display.
   
5. Click on Save and continue working.

The Views Interface

Views are complex but these pointers can help to reduce the complexity. It is important to note that some of the settings change depending on the type of Display you are working with.

• Master - this is the foundation for other block and page displays. Add the filters, fields and other common settings that you want to use for other displays. These settings can be overridden if need be.
• Title: title of the display i.e. Title: Demonstration
• Format: the way the list displays. Display options out of the box are HTML List, Unformatted, Table. Settings vary based on the format chosen. i.e. Format: Unformatted list | Settings
• Fields: list fields to display in your view i.e. Content: Title
• Filter: choose criteria to help limit the data that will display i.e. Content: Published (Yes) and Content: Type (= Book page)
• Sort criteria: indicates which fields to sort by and whether to sort ascending or descending.  i.e. Content: Title (asc) will sort alphabetically.
• Access: limit who can see the view by role or permissions.
• Header: add text at the top of the list.
• Footer: add text at the bottom of the list.
• Pager: create a pager and indicate the number of items you want to display. i.e. Use pager: Full | Paged, 10 items More link: No

• Contextual filters - dynamic filters to pass as arguments.
• Relationship - create links between 2 or more Entities and/or Content Types.

View Pointers

Here are some key points that are helpful when creating Views:

	If you are changing the Display from the Master, you must choose the This page (override) from the top of the page. Otherwise, the Masterdisplay is changed.
	Italics indicate the value has changed from the Master.

Add fields, filters, relationships etc. and rearrange the order of the list for that specific type.

Settings - link next to the structure indicates additional configuration can be done.

Views Cheat Sheet

If you are working on more than one site that have similar content structure, you can use the Bundle Copy module to export and import the code for the Content Types and Views. Once imported, you can adjust the Content Types and Views by adding fields and changing the display. Therefore, we recommend reviewing the basics for creating with Custom Content types.

Importing a Content Type

If you want to duplicate a Content Type or use a custom Content Type on more than one site, you can import the code with a simple copy and paste. 

Enable the appropriate modules

1. Select Modules > Bundle Copy
2. Locate and enable the Bundle Copy Module in the Module listing.

Importing a Content Type

1. Select Structure > Content Types > Export from the Administration toolbar.
2. Locate the Content Type you want to export, in this example Rotating Header Image.  
   
3. The next dialog asks you to select the fields you want to export. Be sure to click on the top checkbox to get all the fields. This example has only one field, but for more complex Content Types there would be more fields.
   
4. Click on Export and the following page with all the code that makes up the Content Type is listed. 
   
5. Place your cursor in the text and select all the text; then copy to the clip board. Be sure not to add any spaces or other characters. 
6. Select Structure > Content Types > Import from the Administration toolbar.
7. Change the name and paste the code in the fields as shown below
   
8. Click on the Import button and the Content Type is created. 
9. Check your Content Type by clicking on Structure > Content Types > Name of Content Type
10. Click on Comments to ensure they are turned off. 
11. Click on Display Settings and uncheck Display author and date information.

Export/Import a View

You can export a view and then import it to another site.  The view is the first step to creating the list or display you want; once imported, the view will need to be adjusted according to the site specifications. For more information on working with views, we recommend you review the YaleSites Views tutorial.

Export the View

1. Select Structure > Views > Export
2. Locate the view you want to export, click on the Export button and copy the code like you did in the Content Type above. 

Import the View 

1. Select Structure > Views > Import
2. Locate the view you want to export, click on the Export button and copy the code like you did in the Content Type above.
3. Paste the code in the field and click on the Import button.

Your page/block, etc is available for you to link or place on the site as desired.

One of the great features of Drupal is the ability to display an image in multiple sizes, without physically resizing the image, eliminating the need for multiple sizes of the same image on your server. This feature is called Image Styles and it allows you to define an image “preset” size which can then be chosen for display for a specific content type and/or view. To create an Image Style:

1. Select Configuration > Media > Image Styles > Add style.
2. Add the name of the Image Style (use lowercase, no spaces).
3. Select Scale and Crop from the Effect section and click on Update Style.
   
4. You will be prompted to enter the height and width for the image style.
   
5. Click Add effect and the Image Style is added to your list.
6. Close out of that window, then go to a View or Content Type and you will see the Image Style listed as an option to change an image size to display.
   

The Date and Time settings for your YaleSite come with many display options but might not display in the order or format that you want. You can add a new date format that will be available in the list of the standard date formats (Configuration > Date and Time formats >  .

YaleSites comes with a variety of Date formats, but they are limiting. However, you can easily create a new date format in the following way:
 

1. Select Configuration from the Toolbar then Regional and Language > Date and Time formats. The Date and Time page displays.
   

2. Click on the Formats tab and click on +Add format. The Formats dialog displays with the ability to configure and create custom formats. 

3. Enter the PHP codes you using the PHP Manual link to indicate how you would like your date to be formatted. 
   

4. The PHP manual provides explicit instructions for which codes to use to get the desired result. For this example, I wanted the date to be set to month/day/year so I used the following codes: l, F n, Y where l is the full day spelled out, F is the full month, n is the day number without the leading zero, and Y is the 4 digit year. The new format displays when the configuration is saved.
    

 Adding as a Type

Once you have created your format, you have the option to name the format as a Date Type so that it shows up as an option on the date formats list in your Views or format options for Content Types.

1. Click on Add Date Type.
2. Create a name (Date type) and choose your newly created date format (Date Format).
   
3. The new format displays in the list:
   

Assigning the date format to the View or Content Type

Once the date has been created it will be available in the list for views and/or content types. Just click on the drop-down menu (in this case a view) and select it as an option. You can also use it for any of the standard formats including Long, Medium and Short.

View

Choosing a date and time format for a View

Content Type

Choosing a date and time format for a Content Type:

YaleSites Secure is a Feature that offers additional security for sites that store or collect sensitive data for research projects or collecting information for study participants. YaleSites Secure has all the features that are included in a standard YaleSite with the following differences:

• Security (SSL) - Provides a secure version of the http protocol (https). Data is encrypted between client and server.
• Field Encryption - Provides the ability to select which fields can be concealed from unwanted sources using encryption.
• Native user login - Together with SSL allows the creation of secure accounts for study participants.
• Search Indexing Prevention - Site is not indexed by search engines, content would not appear as part of Google, Yahoo, etc. 

Data that should NOT be stored

The following is a list of the types information that should NOT be included in your site.

• No user identifiable data including email addresses
• De-identification Fields are listed in Exhibit 5039 - EX.A
• Further information can be found under HIPAA Procedure 5039 - PR.1

Before you develop your secure website

The following is a list of important points that require consideration before developing your site with YaleSites Secure.

Prior to any development:

• All sites must through a preliminary Security Design Review (SDR) with the Yale Information Security Office (ISO).
• You must participate in YaleSites secure onboarding* to ensure the process is understood 

Going Live:

• Once your site has been built, a final Security Design Review (SDR) scan will be performed to validate URLs and site security.
• Any SDR Scan issues found in the final scan must be fixed and approved before the site can go live. Sites will not be moved to production until the final SDR scan is fully approved and issues have been resolved.
• Resolving/approving these changes may take 2-4 weeks. Please plan your site warranty based on the approval date of the final SDR scan rather than the day development is completed. The warranty period should begin after website is in production.  

Requ​esting YaleSites Secure Site

1. Complete the Request a YaleSite form.
2. Click on the checkbox to indicate you want YaleSites Secure.
3. Request a Security Design Review (SDR) with the Yale Information Security Office (ISO). 
4. Participate in onboarding* meeting setup by YaleSites Web Team and ISO.

*YaleSites Secure Onboarding

In order to ensure the policies and process required for YaleSites Secure are understood, the vendor and site owner must attend a preliminary onboarding meeting. During this meeting the YaleSites Web Team and Yale Information Security Office (ISO) will provide you with the requirements necessary to build a YaleSites Secure site. Development on the site cannot take place prior to the onboarding meeting.

Important Note: The request and approval process for YaleSites Secure may take 2-4 weeks. Please plan accordingly.

Site U​RLs

YaleSites are provisioned in the development stage (.dev) unless otherwise requested.

• Development: https://site_name.dev.ys.yale.edu
• Production: https://site_name.ys.yale.edu
• If someone types in http://site_name.yale.edu, they will be redirected to https://site_name.ys.yale.edu

Website A​ccess

Access to the site is determined by role a person has in development, participation and/or viewing the content. Important Note: Anyone who has access to the information on a YaleSites Secure site must complete HIPAA Privacy and HIPAA Security training on Yale’s Training Management System (TMS).

Site Building and Maintenance

1. Administrators, Site Builders and Site Editor roles have access to administrative pages for the purpose of building functionality and maintaining the site content.
2. VPN is required to access administrative pages when working on the site on or off-campus.
3. Administrators, Site Builders and Site Editor roles must login using CAS (append cas to the end of their URL https://site_name.dev.ys.yale.edu/cas)

Participants

A participant is identified as someone who has access to the site to contribute to the study or research program, but does not have permission to access the administrative pages. Participants are given access to the site using native Drupal login.

1. Direct participants to https://site_name.ys.yale.edu/user where they will be asked to login or create an account. Please use the following guidelines:

• Login accounts and passwords may not be user identifiable and may not be email addresses
• Users should not be able to receive email with their login / password
• Users should not be able to request passwords (module NoReqNewPass installed and configured)
• All login and passwords provided must be at least 8-14 characters as per Yale Compliance Requirements
• Third Party Authentication (HybridAuth) is NOT supported.

Participants who are logged in a given the default role of authenticated user. Additional Roles can be assigned to participants as dictated by site requirements.

Important Note: Email notification for new accounts must be setup to change the language to meet program/project needs.

Site Visitors

Anonymous users will only be able to view public pages of the site as determine by the root directory. 

Page URLs and Site Structure

YaleSites Secure is setup to allow participants, anonymous users or site visitors to view pages that are in the public virtual directory. In order to create the virtual public directory, you must create a URL alias for each Content Types of any pages that will be viewed by the public (public/[node:title]). All pages that are available to anonymous users or people who are just visiting the site are stored in the public virtual directory.

• https://site_name.ys.yale.edu (index page)

• https://site_name.ys.yale.edu/public/page-url

Restricted Access

Configuration and administration pages are restricted to Administrator, Site Builder and Site Editor roles. The following URLs are helpful for administrators to determine the path necessary when coding advanced template files and modules to ensure the path is correct.

/sites/default/files/* (images, pdf, other digital assets)  

/sites/all/modules/* (modules used by the website)

/sites/all/themes/* (js, css used by the website)

/user/* (user profile details available only to authenticated user)

/flag/* (allowing for bookmarks using flag module)

/sites/all/libraries/* ()

/cas (allowing users to login with Yale CAS)

Security Standards

Digital Assets

All digital assets (images, pdf, etc.) cannot contain user identifiable information, examples include:

• PDF documents with contact information or personal information
• Images with text containing personal or contact information

Secure Login - Username and Password Creation

• Login accounts and passwords may not be user identifiable and may not be email addresses
• Users should not be able to receive email with their login / password
• Users should not be able to request passwords (module NoReqNewPass installed and configured)
• All login and passwords provided must be at least 8-14 characters as per Yale Compliance Requirements
• Third Party Authentication (HybridAuth) is NOT supported.

Prevent Search Engine Indexing

• This feature contains a robots.txt file with following content to prevent search engines indexing pages. 

User-agent: *
Disallow: /