Rails

Create a Stacks page in RapidWeaver, then add the Rails stack. You'll notice Rail Items on the left, and Rail Sections on the right, add more items and sections as needed, they'll automatically number and link together. Once you fill in item titles and content - you're up and running!

Go beyond basic setup by adding Font Awesome to your Rail Item titles. Rail Items can also link to other site pages, or an external URL. Other controls include, Rail Item width, alignment, easing animations, borders, unique separators, generous color controls, and more.

You can even add other stacks above and below Rails - like a footer stack for a finished site look. Again, the best part is - a Rails layout can be used in virtually all your favorite RapidWeaver themes!

1. Rails does not hide content like an accordion or tab based container. Search engines have trouble indexing hidden content. Rails streamlines one page content design and adds a navigational list to swiftly move between sections. Keeping all content visible on a webpage is excellent for SEO (Search Engine Optimization), and allows content access with simple scroll down and swipe gestures.

2. Rails can only scroll down if the content exceeds below the screen. You might setup a Rails layout for the first time, and find the navigation is not scrolling or moving between sections. This is normal, and is due to your page content being shorter than your screen. Once page content exceeds the past the screen, Rails can then scroll to access lower page sections. There's even an "Extra Bottom" setting in Rails to help aid the scrolling effect.

3. Rails does not change the natural behavior of scrolling or swiping. Some websites "sense" when a user scrolls or swipes, then manually transitions to more content - it's a very controlled experience. In short, I hate this method, and will never create a product that hijacks scrolling.

4. Sometimes a completely one page website is not practical. If you feel a product or topic should be given it's own separate page - your probably right! It's perfectly fine to mix one-page content design into a site with multiple pages, this is a standard practice for Apple, Audi, and Ford websites - just to name a few.

5. Rail Items can link to Sections, other site pages, or an external URL. It's recommended to place links to other pages - at the end (or bottom) of the Rails Item list for visual clarity.

Only one (1) Rails stack layout can be used per Stacks page. Rails does not support IE8 or below. Rails has been compatibility tested with all built-in, and select 3rd party, RapidWeaver themes. Themes with sticky navigation should not present an issue, Rails has independent offset controls to always keep content accessible. After testing, we'd call Rails "highly compatible" with other themes, with a few key exceptions.

⚠️ Rail Items should be limited to 8 items or less, to prevent cropping of lower navigational items on narrow height screens.

🚨 Rails is not compatible with themes where... main content is inside a fixed positioned container, or with themes that animate the outer main content container. These cases are rare for a theme, but if concerned, you can ask the theme developer.

Rails has 3 main stack settings: Rails, Items, and Sections. The "Rails" settings control the overall one page layout. "Item" and "Section" settings, provide unique control over each Rail Item and Rail Section.