Thanks! Please check the following:
Please read carefully! All purchases are final. Refunds will not be provided under any circumstances.

System requirements
License agreement
Refund policy
Purchase process
Customer support

System requirements
All the stacks sold through this website require RapidWeaver and the Stacks plugin. They will not install or work with any other publishing platforms (like Flow, Drupal, Blocs or Wordpress).

We recommend you aim towards installing the latest version of RapidWeaver that your computer is capable of running (preferably RapidWeaver 7 or greater) and Stacks 3 or later. Both are a separate purchase if you do not own them already.

Stacks4Stacks generously provides you fully-functioning free demo versions of everything sold on this website. This enables you to fully test addons before committing to a purchase. There are no time or functionality limitations applied.

If you cannot get the free demo version to work, DO NOT proceed with purchasing the stack - because the purchased stack is unlikely to work any better for you. Please request technical assistance first.

License agreement

You may use a purchased stack an unlimited number of times in personal or commercial projects and request technical support.

We permit you to install stacks onto all computers that you own. You are permitted to make private archival backup copies (e.g. iCloud, Disk Blaze, Google Drive or Dropbox).

You may not resell, redistribute or make a stack available for download, remove copyright credits, license information, or claim the stack to be your own creation. This includes free stacks, demo stacks or paid stacks, in modified or unmodified states.

The software is provided "as is" without any implied or expressed warranty of merchantability or fitness for purpose. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise arising from, out of or in connection with the software or the use or other dealings in the software.

Refund policy
By purchasing from this website, you agree that your purchase will be available immediately via digital download and that you waive your statutory right of withdrawal.

All purchases are final. Refunds cannot be provided (we physically cannot un-download or remove stacks from your computer) under any circumstances.

You are reminded to make use of the free demo versions already provided on the website, to fully evaluate stacks for compatibility and suitability before making a purchase.

If you cannot get the free demo version to work, DO NOT proceed with purchasing the stack - because the purchased stack is unlikely to work any better for you. Please request technical assistance first.

Be certain that the stack you are buying is actually the one you want, and that you don't already own it or are confusing it with another stack of similar name or functionality.

Purchase process
The checkout system is provided by Paddle. An attempt is made to display prices in your local currency, with relevant taxes applied.

To complete your order, you must supply a valid email address. Your purchase receipt and download link will be sent to this address you supply. If you do not receive your purchase shortly after completing it, please carefully check your spam or junk mail folders.

Your purchases are available to re-download at anytime, via this secure order lookup page.

Prices shown on the website include any applicable VAT or sales tax. You will be sent a full receipt by email. Charitable and bulk discounts may be available on request. Please get in touch if you have any queries about our pricing.

Our order process is conducted by our online reseller is the Merchant of Record for all our orders. Paddle provides all customer service inquiries relating to order processing. Paddle also provides an order lookup system, commonly referred to as your Paddle Account.

Customer support
If you have questions that relate specifically to a stack, you should make contact via the contact page.

General questions can be asked on the RapidWeaver Community Forums.

I'm FloatingContent!

Lorem ipsum dolor sit amet, sapien platea morbi dolor lacus nunc, nunc ullamcorper. Felis aliquet egestas vitae, nibh ante quis quis dolor sed mauris. Erat lectus sem ut lobortis, adipiscing ligula eleifend, sodales fringilla mattis dui nullam. Ac massa aliquet.
FloatingContent is more advanced than the free Sticky stack, but doesn't contain as many triggering / toggle options as the full-blown Gateway stack does. It's a pleasantly simple stack for the majority of RapidWeaver users, with just enough settings to accomplish all the basics. The animated 'following' behaviour is a particularly nice feature of this stack and lends itself well towards the presentation of short messages.

Floating containers can present presentational display issues on smaller screens; where space can be at a tight premium. FloatingContent already has this sorted for you! Some quick options permit you to toggle-off the display of FloatingContent stacks on smaller screens (like smartphones). Alternatively, the new 'dismissible' options let users close FloatingContent; and it will remain hidden for a definable period of time, with the aid of a small and harmless tracking cookie.

As you can imagine, FloatingContent has loads of potential uses in many websites. It's an excellent value stack which you can use time and time again for either temporary messages or more permanent fixtures. A variety of basic stacks can be placed within FloatingContent. All positioning can be adjusted in the settings. Advanced users will be able to use CSS code to modify the appearance even further. FloatingContent requires Stacks 3 or above.


You can see a basic working example of FloatingContent on this webpage. When you scroll the page up and down, you will see the FloatingContent message box follows you. If you dismiss FloatingContent and reload the page, you'll see it remembers to stay hidden! To bring it back again, click this button to clear the cookie and reload the page:

Reset FloatingContent


FloatingContent is easy to get working in most webpages. In essence you can follow these steps:
  1. Once installed into Stacks and RapidWeaver, open your Stacks Library (on a Stacks page type)
  2. Drag and drop a copy of FloatingContent into the webpage
  3. Within the main FloatingContent container, drag and drop one or more basic stack types, like styled text. Padding or margins can be applied to the stacks you drop into FloatingContent
  4. Keep the FloatingContent stack selected in edit mode to access its customisable settings. Change anything else required
  5. Preview the page to see FloatingContent appear. On longer pages, it will follow you when the page is scrolled
  6. Publish or export your website when done

Always carefully test your FloatingContent stacks on different screen sizes; to ensure they do not inadvertently obscure important website content underneath (like navigation links or body content). Making FloatingContent stacks dismissible (closable) can help resolve such issues.

With some care, it may be feasible to use multiple FloatingContent stacks on the same page. However you will need to carefully test to ensure they don't clash with each other. This includes positioning on different screen sizes too. If you need to include the same FloatingContent stack on multiple webpages, you can do so by setting it as a Partial in Stacks 3.

Making FloatingContent dismissible

The idea behind this feature in FloatingContent is to let end users close the FloatingContent stack when they've finished viewing. To prevent FloatingContent reappearing immediately when the page is reloaded, a small tracking cookie is created on the users computer, when the close button is pressed. When the page loads, FloatingContent can look for this tracking cookie. Based on what FloatingContent finds, it can either hide or display the content. The tracking cookie duration is determined in 'minutes'. Obviously if you want FloatingContent to be dismissible but you want it shown each time, simply set the tracking length time to '0'.

The Font Awesome icon design and button colour can be customised within the FloatingContent settings. When the close button is enabled, it will be displayed at the top right of FloatingContent, and content within FloatingContent is pushed-down by 35px to avoid interfering with the button.

Any custom button or link with a class attribute of floatingContentClose can also be used to dismiss FloatingContent stacks, while dismissible behaviour is active in the stack settings.

Tracking cookies can be deleted at any time in the browser console. To create a link or button in a webpage to cancel tracking cookies you can use a specially coded HTML button like this:

<a href="#" class="btn btn-primary resetFloatingContent">Reset FloatingContent</a>