every Blocs Bric and Block has a common interface with typically 20 settings and a deeper 40 settings when using the powerful Class Manager. Also, I would not agree that Blocs has vastly less flexibility and the 3 links to Blocs sites I posted above, illustrate this with real examples of design layout flexibility.īlocs actually has vastly more settings than Foundation with stacks for example, but Blocs processes those settings in a much more efficient way. Not wanting to turn this into a one is better than the other, but you must have based your ideas on very early versions of Blocs App and does not reflect where Blocs is today. You can get the same preview performance in RapidWeaver if you use simpler layouts and add-ons with less options. When you have less options, things can be made faster. Otherwise hand-type code to access assets/resources.Basically, when you compare Blocs to RapidWeaver+Stacks, Blocs has vastly less flexibility in terms of layouts and options. In most cases this isn't a problem, as RapidWeaver by default > Assets section are kept separate from other pages in your RapidWeaver 4, any files you add via the Page Inspector -> Header #Pagesafe versus filesafe rapidweaver code Puts each page of your website in its own folder. Since each page can have its own assets, RapidWeaver has to For example, let's say you put several related pages into the This approach is that it can cause confusion when you restructure your This means (if youĭon't change anything) that the files you add to a page can be accessedīy referring to the "assets" folder. Keep track of which files belong to which page. Let's see this in action to make sure it's completely clear: RapidWeaver 4, the "assets" folder is renamed to pagename_assets for the pages that share the same folder. The URL on your website for that page may look like this:Īnd let's also say you made a diary of your vacation and put it here: Say you have a photos page with pictures from your recent vacation. This example, the two pages (photos.html and diary.html) share the sameįolder (vacation). This is a tremendous improvement, as it means you can access RapidWeaver 5 does away with "page assets" and instead uses "sitewide Make sense? (If not, don't worry, this has confused a lot of people.) In RapidWeaver 4, in order to keep each page'sĪssets separate, the assets folder would be renamed to photos_assets (for the photos.html page) and diary_assets (for the diary.html page). The files you add to your website from anywhere you want. To your website is also much easier - you can just drag and drop anyįiles into the Resources section of the RapidWeaver sidebar. The sitewide resources, and RapidWeaver then figures out the path to This special syntax tells RapidWeaver that you want to use a file in To make things even easier, RapidWeaver 5 allows you to access any of the files in sitewide resources by using this macro: %resource()% You canĪlso use the "Add Resources" button in the upper left of the RapidWeaver Macro? First, find out the filename for the file you want to use. Refer to a file inside that folder, just include the folder name as If you've added an entire folder to sitewide resources, and want to Insert that filename in between the parenthesis of the macro, like so: %resource(image.jpg)%. #Pagesafe versus filesafe rapidweaver code.
0 Comments
Leave a Reply. |