Source

Stacks app beta

---

Posted by Stuart | 19 Apr 2025

---

Beta 38

Beta 38 is now available for Stacks 6 (the standalone Stacks app) and it has come a long way since the previous beta version that was made available. It is in a state now where you can go in and have a play and test out all of your favourite stacks.

Isaiah is aiming for 100% compatibility with all existing stacks so be sure to report any general issues that you find to him (via Discord or the dedicated bug tracker). If there are Source stack issues then let me know and I can check them first to see if Source or Stacks is at fault.

Advice: There is still far too much missing from Stacks 6 for you to be able to build your sites with it. For the forseeable future stick with the RW/Stacks combo for your actual web work. Do beta test Stacks though as your feedback will help drive development forward.

Source theme

Stacks 6 requires a different set up for themes so the existing Source theme will not work. Below you can find a download for a Source theme that will work in the beta.

To install it, in Stacks app: View > Show Library folder > Cmd + Up arrow > Navigate to Themes folder and move theme there

This is a very basic version and is just a crude tweak of the Base theme for now. It will not get updated in Stacks app so check back here to see if any later versions are available. Moving forward the plan is to migrate the settings from the main Source stack into the theme itself as this will allow for greater flexibility.

---

Known issues

This is just listing known issues for Source stacks. There are various general known issues that can be found elsewhere.

• Navigation stack: The Source Navigation stack will not work properly as there is currently no way for the theme to make the site's navigation structure available to any stack. Previously this was achieved by using one of RapidWeaver's macros (%navigation%) however this is not currently supported in Stacks app. There are numerous similar macros that aren't yet supported either (%logo%, %site_title% and many more). It is really only Source's Navigation stack that makes use of these things but there are various third-party stacks that depend on these things too. As 100% compatibility is being aimed for I would imagine a solution will be found for this. Failing that the Navigation stack will need to be revamped to work in Stacks app.