Galavante Site Help - Galavante (Travel & Lifestyle Website)

Welcome to the Galavante Help section. This short guide will give you information on how to create content for our site. Please note: when uploading pictures or files, please make sure there are no spaces the file name or else the picture / file might not be found by the site!

Creating Content

In the upper left hand corner of the you should see an Icon of a Wrench. Click that to bring out the side bar admin. If you don’t see this, you don’t have permissions. Please as your site admin to give you them.

Creating Content

Creating an Article

Content in this site are referred to as “nodes”. There are several different node types, seen in the blue box on the visual above. Here we are going to walk through an “Article” the most common node on this site.

Adding text to a Node

Adding a Location to this Node

Side content Markup Snippets

Two of the most common sidebar content is the “On The Menu” for Cooling Your Jets and “The List” for Destinations. Use the snippets below to ensure the proper markup and styling

On The Menu

<div class="on-the-menu">
<h3>ON THE MENU</h3>
Enter ingredients here
One line after
Another!
</div>

The List

<div class="the-list">
<p>THE GALAVANTE LIST</p>
<p><strong>Stay</strong></p>
<ul>
<li>item</li>
<li>item</li>
<li>item</li>
</ul>

<p><strong>Eat</strong></p>
<ul>
<li>item</li>
<li>item</li>
<li>item</li>

</ul>

<p><strong>Drink</strong></p>
<ul>
<li>item</li>
<li>item</li>
<li>item</li>
</ul>

<p><strong>Shop</strong></p>
<ul>
<li>item</li>
<li>item</li>
<li>item</li>
</ul>

<p><strong>See</strong></p>
<ul>
<li>item</li>
<li>item</li>
<li>item</li>
</ul>
</div>

Nodequeue Node Sorting

Some content on this site requires a manual sort. We use the Drupal module “Nodqueue” to do this:

Editing, adding and removing items from the Queue

Adding a Newsletter Node

At the time of this writing, this site use the Constant Contact service to keep newsletters. While the Constant Contact module did not have the functionality that we needed, we just decided to use a regular content type for it.