This Partial is only for presenting some information. You will not see anything in preview mode and you should remove the Partial before publishing. In some Foundation project templates you will find some more information Partials, you also should remove them before publishing.

• Jack - Joe Workman
• Target - Joe Workman
• FontAwesome - Joe Workman
• MagicGellan2 - BigWhiteDuck
• Geo - Doobox

Creating a website using templates can be a better way to a reasonable outcome within a short time. My project templates can be your starting point on the way to a fully functional and impressive website - a website your page visitors will like and which meet its target.

My Foundation project templates are preconfigured. You can focus on the content and you only have to do some individual customizing - you paste or write your text, insert your images and you only have to enter the login details of your FTP server. After a really short time you can publish a fully functional website. Using templates saves time and money and will help to get in touch with a challenging webdesign framework.

My templates function on a desktop computer but also look good on mobile devices. They had been checked on desktop systems, on iOS and on Android. But they do not work with older versions of the Internet Explorer because the Foundation framework doesn’t support this. The Internet Explorer will be forwarded to a special error page (“Legacy Browser“).

My templates are optimized for search engines: They come with a preconfigured SEO Helper stack and use structured data.

The Foundation framework was created by ZURB. Joe Workman brought this framework to the RapidWeaver platform. When you make your first steps in web designing, Foundation may not be easy to understand but my templates can be a doorway to this advanced and forward looking system.

You find a lot of information on Joe Workman’s tutorial page: JW Doc Portal

Header image by Pexels.com

This stack is for basic settings of your page. It is essential for Foundation pages.

If use use the Site Styles as a partial you can transfer settings you made in one page to other pages.


Language Settings:

Make sure that the language settings for your country are made.


Color Settings:

Text Colors are used for text elements and Element Colors are used for special elements. Swatches are primarily used for objects with two colors, like a button, first is primary color, second is secondary color. So if you set a swatch to red and blue, then choose a button, the color of the button is red and the text of the button is blue. Colors in swatches are used in different ways based in the context. When applied to fonts then the first color is used. When applied to a container like a panel, then the background. A button uses both.

I you need a color outside of the Site Styles, there's often a 'Custom Style' checkbox/option which you can use.


Font Settings:

In Foundation, you can use some preconfigured fonts but you also can use web fonts.

Google Fonts are the easiest way to use web fonts you are offered about 1000 fonts. Go to the Google Fonts site and select a special font name. The font name you write into the Site Styles setting, separated for title, slogan, subtitles (H1 - h&) and text (P). Note that you can the weight of the font, i.e. 300, 400. 700, etc, but some of the Google fonts will only be offered with a font weight of 400. Using a font weight that is not supported can cause issues.

This Partial is only for presenting some information. You will not see anything in preview mode and you should remove the Partial before publishing. In some Foundation project templates you will find some more information Partials, you also should remove them before publishing.

Here you can make your settings for better SEO.

Description: A page description is essential. Make sure that the description is individual for each page.

Browser Title: Additionally you should configure a browser title in Page Inspector > General Settings. Make sure that the title is individual for each page.

Page Speed: You can use this for loading scripts at the end of page loading but you should check the functionality of your page before publishing. For SEO tacking it might better not to use Page Speed

Robots: There are two ways to setup a robots declaration: You can make a declaration for each single page but you also can write a robots.txt file for the root directory of your server. What is better you should decide on a case-by-case basis

Keep in mind that there are further SEO setting in Page Inspector > Meta Tags & HTML Code, these are a little bit different. Here you should at least setup a language tag and an expires tag what is not possible in the SEO Helper stack.

This Partial is only for presenting some information. You will not see anything in preview mode and you should remove the Partial before publishing. In some Foundation project templates you will find some more information Partials, you also should remove them before publishing.

Structure Stacks:

For SEO reasons the content of your page is organized by Structure Stacks. This has nothing to do with the Structured Meta Data in the SEO Helper Stack but is for better machine readability by crawlers or reading devices.


Columns:

Websites (especially responsive websites) are based on a column grid. Basically you should organize your content stack in a column system. Otherwise content will be displayed side wide.


Foundation stacks and 3rd party stacks:

The Foundation suite offers a lot of stack solutions for a large range of tasks. These Foundation stacks will harmonize and you will avoid conflicts when you use only these stacks. But it will be possible to use any 3rd party stack (I have never seen a stack that cannot be used in Foundation but theoretically conflicts are possible).

For better performance do not make the mistake to use to much different stacks. You will lose the track and the performance of your site will suffer.

This Partial is only for presenting some information. You will not see anything in preview mode and you should remove the Partial before publishing. In some Foundation project templates you will find some more information Partials, you also should remove them before publishing.

Text:

If you want to format text, you should use the options of Page Inspector > Page (= stacks settings). Only in exceptional cases you can format text in a stack.

If you want to choose another font for a single stack you should use special stacks solutions.


Images:

You can drag images into the area most of the image stacks offer but you can also warehouse images. Images should be the correct pixel values for the container of the web page they are embedded. The file size should be not too large because a large file size will affect the performance of your page.

You can use JPG and TIFF, for SVG you need special image stacks, e.g. GraphicStack from stacks4stacks.


Videos:

There are a lot of ways to embed videos into a web page. Please note that a video must be embedded in different file formats because the different browsers need different video formats.

This Partial is only for presenting some information. You will not see anything in preview mode and you should remove the Partial before publishing. In some Foundation project templates you will find some more information Partials, you also should remove them before publishing.