The front/landing page of the website, the first page you see when entering the website.

Often includes:

• Callout banner

• Main navigation menu + banner book button

• Jumbotron row

• Multicolumn Row (with various content)

• Activity grid

• Featured activity row

• Image buttons

• Link gallery

• Testimonials

• About Section

• Footer

The All Activities Page is where you can find all the activities listed on the website. We use the activity grid to showcase all the activities available on the website. There can be multiple All Activities pages categorized in different pages depending on the structure, for example seasonal activities, locations, etc.

Often includes:

• Callout banner

• Main navigation menu + banner book button

• Jumbotron row

• Activity grid

• Footer

When we import the items from the dashboard, the items are created on the single activity pages. The layout differs from the foundational pages. In some cases it is also possible to get a custom layout, but we would always recommend using the original layout.

Example

Often includes:

• Callout banner

• Main navigation menu + banner book button

• Header image

• Quick Details

• Description

• Sectioned content

• Related Activities

• Footer

• Pricing table:

  • Slideshow images/video

  • Book button

  • Pricing

  • Calendar

A page to show frequently asked questions.

Often includes:

• Callout banner

• Main navigation menu + banner book button

• Jumbotron row

• Sectioned content

• Footer

A page to show information about the company, for example about the employees, founding story, etc.

Often includes:

• Callout banner

• Main navigation menu + banner book button

• Jumbotron row

• Multicolumn Row (with various content)

• Cards

• Footer

The contact page usually consists of a contact form and the contact information block.

Often includes:

• Callout banner

• Main navigation menu + banner book button

• Jumbotron row

• Multicolumn Row (with various content)

• Contact form

• Contact information

• Footer

If the client wants a Callout Banner, it’s always at the top of the website. It shows 1-2 short sentences and most clients use it to announce new activities or coupons.

The main navigation menu shows the different pages within a website. It can also have a search option, translation globe and a banner book now button, and the logo.

The jumbotron row is showing the main header and is usually the first thing someone sees when they enter a page. It can show only one picture, a slideshow or a video. Please note that videos can only be displayed on the desktop, not the mobile version of the website.

An activity grid shows the different kinds of activities the company has to offer. Most of the time it highlights the most popular activities. The content (pictures, summary, taxonomies, from pricing) are directly connected and edited on the specific activity page.

Featured activities are activities that the clients want to highlight on a page. The information is again pulled from the activity page. There are two different design options.

This is the primary building row in FH Sites. These rows include 1-4 columns, where each column might contain any of the various content blocks that are available to use (including images, text/copy, buttons, links, etc.)

Image buttons are a way to link to other pages with a grid. You can for example link certain pages that show different activity categories (e.g. “Jeep Tours” and “Canyoneering”). They can also be used to link to external websites (for example featured articles).

Link Galleries are perfect for showcasing images that link to another page or website. They are also great for showing logos (like for example “Our Partners”).

Cards are a way of using preset content for information about for example different boat rentals, team members etc. They are usually used for “About Us” pages.

A lot of companies want to have their Tripadvisor or Google Reviews displayed on their website. For this we use the testimonial option. Please note that these are not links to the review pages. Most of the time we link their Tripadvisor or Google Reviews in the footer.

Clients use this option to tell their customers about their company. Most of the time we use additional photos and a CTA in the form of a button.

The footer should be at the bottom on every page. It’s a small summary of the website’s content. It shows the companies contact information, links to their social media, their logo, a CTA and quick links.

The sectioned content is commonly used on the FAQ page or on the single activity pages. It for example shows popular questions and answers in a “folded section”.

The contact form is a commonly used way for the customers to be able to contact the company. We can create different forms for one page.

The contact information is directly pulled from the Company Settings in the backend. Usually shows the phone number, email address, location, social proof/media links and a Google maps

The header image is the picture in the background. You can see it at the top of the single activity page.

The pricing table is found on the right side of the single activity page. The pricing table includes:

Slideshow Image

The slideshow images are the thumbnail sized images on the pricing table on the right side of the page. The placement and the size can’t be changed. If the client wants these pictures to be bigger, we can add a slideshow underneath the description on the left side instead.

Book Button

The Book Button on Single activity Pages usually leads to the lightframe of the item connected to this specific page. The button is customizable and can lead to other items, flows, etc.

Pricing

The pricing should reflect all the prices and customer types from the dashboard. Prices are not synchronized with the Dashboard, we have to add and edit the price manually. It doesn’t automatically pull the prices from the dashboard if changes were made, so a new ticket needs to be submitted each time something was changed in the dashboard (this also applies to the rest of the activity page).

Calendar

The calendar pulls all the activities from the dashboard. It is hardcoded, which means that LSS can’t change the text or colors.

The Quick Details section shows the most important information about the activity. They are either added manually or pulled from the taxonomies. Taxonomies can include things like duration, location, capacity etc.

The description text shows the details about the activity. It’s on the left side of the activity page.

The related activity section shows other activities the client wants to highlight on the single activity page.

Please have a look at this help page for more details regarding communication and interacting with the LSS team

1. Don’t promise a client features or timelines without first speaking with an LSS Team Member! You can simply say “I’m forwarding this to our Sites Team! they’ll be in touch to collect more information and get a solution in place.”

2. Using the macro “LSS internal request macro” is very helpful. The macro makes it easier for Support and LSS to remember to include all the relevant information that we need to handle a request!

3. Outline the overall goal of the ticket first

4. Always include the website URL and any relevant page URLs in the ticket.

5. If it’s changing or adding content on the site, it includes links to the specific pages the requests relate to and/or it includes the location of the change. We love annotated screenshots!

6. If it’s changing or adding an image, the image must be attached, and where this image is being added or replaced with.

7. If adding a new page, all content must be provided for the page.

8. The more detail you can get out of the client and summarize for us, the better!

9. If a new item is being added, please include the Item ID # and the Dashboard Shortname. Please make sure the client has reviewed the Item in the Dashboard and approved it before sending it to the LSS team to be added to their site!

10. If there are multiple requests, it’s laid out in relevant groupings.

11. If you’ve been working with a specific LSS agent on a ticket, assign the ticket directly to them. Otherwise, assign the ticket to the FH Sites Group (not the FareHarbor Websites User).

12. Follow the escalation/prioritization guidelines outlined in the “Escalating Tickets for Prioritization” section.

13. We love our peeps in Dashboard support, thank you for all you do!

1. Always create a new ticket with the updates concerning LSS. Do not just assign the original ticket to Sites and leave an internal note. The tickets should be kept separate between the teams!

2. In the Requester field: assign the clients contact email that should be used.

3. In the Assignee field: assign to FH Sites (not FH websites) or specific LSS agent (if necessary)

4. Add a relevant Subject

5. Write the request in Internal notes

6. Assign the ticket as New

7. Done!

For LSS to be able to import items from the Dashboard to a FHS the item needs to be bookable. An item can not be imported if it is still in Private mode. Make sure that either the Support agent or the client has made the item bookable before sending the request to Sites.

On Close: To the left, under “Custom Fields” there is a tab called FHS – Status. Next to this field, if the status is set to Live, this means that the client has a live FareHarbor website!

Directly on the website: You can also check directly on the website to see if the website is on a FHS or not. Simply scroll down to the bottom of the site to find the FareHarbor Footer that is connected to all the FHS:

No. FareHarbor employees are not supposed to make changes to websites that are not managed by FareHarbor. Some clients might ask us about these favors, but this is not a part of our responsibilities or expertise.

Affiliate links. When sending a ticket to Sites asking us to add affiliate items to the FHS, please attach the link for the affiliate item, not just the name of the item/dashboard, etc.

No. The Sites department only communicates via email (zendesk). We do not communicate via calls. If the client is requesting to speak to the Sites department on the phone, please refer to Support or Account Managers (or other departments that handle calls).

Please make sure to get all the important information written in the new ticket assigned to Sites. This goes for all tickets, do not only refer to a call/original ticket, but always write the whole request in the new ticket assigned to us.

The highest access allowed for clients to access their FHS is Admin. This level has certain limitations, such as not being able to use scripts, More information here

No. Changes made in the Dashboard will not show on the FHS, only in the Lightframe. Whenever a change is made in the Dashboard that will show in the Lightframe, it should also be changed on the FHS to match the new updates. Please include all the changes that are made that need to match the site, such as item name change, customer types, availability, prices, etc.

The Sites team can currently communicate with clients in English, Spanish, German, Swedish, Dutch. This might change depending on the Sites department team. Always check before telling a client.

We don’t support installing plugins on FH Sites. This has multiple reasons, for example site speed, security and maintenance. However, if the plugin can be installed via JavaScript it is possible. We always add these scripts in our Global Footer or in Rich text.

For some integrations (e.g. Google Analytics, Meta Pixels, Smartwaiver, Freshworks Web Chats) we can easily add them just with their ID or token.

One of the most common miss assumptions from clients is that changes made in the Dashboard will also show on their FHS. It is always good to remind clients on FHS that make their own changes in their Dashboard to send a ticket and tell us to also make changes on their website to match these.