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.
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.
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.
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.
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.