Like Page Safe the login information is not really individualized (as with Sitelok) but for the right situations that’s perfectly fine. It also, like Page Safe, has basic password protection. It’s a great stack and may meet your needs. It allows my students and me to share various documents with one another. I use Repository all the time for my course websites. That’s something you may want to consider. But I had completely forgotten about Jannis’ wonderful Repository stack. Let’s pretend that you are self-creating spoken audio MP3s that you want to share with some professional collewagues but not others. Cartloom may be best for your needs but I don’t think it was clear to any of us that you wanted to sell items. When you mention Cartloom then you are entering purchasing considerations. I guess I’m not clear what you are trying to do. Otherwise hand-type code to access assets/resources.If you are only dealing with 20 people total, not just for this usage but for future possible usages at same domain, then “yes” Sitelok is probably overkill. 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)%. Concrete CMS (formerly concrete5) was an Open Source Content Management System that can be used by teams.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |