For the purpose of this demo project we have disabled the ability to save changes. You can play around! It won't affect the demo website.
Before publishing
Make sure you have all the necessary stacks and follow the steps to upload Speak on your server.
Necessary staks
Prepare your project file for publishing
This project file must be published in order to work. If you don't publish it first, Rapidweaver preview will not work.
Website Settings
This data is used throghout the entire website to guarantee it's functionality. Make sure you save your settings and refresh the page.
Refresh page after saving.
Website name
This value is used through the entire website for SEO purposes and funtional features where the name of your business is needed. It is also used to sign your form auto-responses.
Website URL
This value is heavily used through the entire website. Make sure the your URL you enter ends with the /
symbol.
https://yourdomain.com
Will not work
https://yourdomain.com/
Will work perfectly
Save and Refresh
Save your settings, wait for the green bar and refresh the page. You should now be able to start editing your admin area.
This step is only required for Speak Pro users, and aims at setting TCMS to generate pretty URLs for blog and projects posts.
Preview blog-post page
Preview project page
Pretty URLs will make your products and post URL look nicer removing the ?permalink= part of the link. After you tested both blog and store systems with the defaul settings, you can enable the pretty URL feature from the blog post stacks in RW.
Follow the same logic for the Projects > post page.
Other information you may need to personalize this project file.
You can edit this data at all time from the Settings tab. Once you go through this initial setup we recommend you to delete it from Rapidweaver. If you are building a website for a client, you don't want the client to easily temper with the Website Settings fields.
When editing the admin menu structure, make sure you give a unique ID to all the related Limelight iframe child stack. Use then that ID as a class for the button that you want to trigger that specific iframe. For instance, if your Limelight unique ID is home
, then assign the Custom class home
to the button in the menu sidebar that you want to trigger the home admin page.
This admin area is not restricted by password
If you have the Page Safe Stack drop one in the admin core partial, so you are sure it will be the same throughout all the admin pages, and they will be all equally protected. Make sure to select the ‘Manage Passcodes with Total CMS’ checkbox and the trick is done. You can enter a password in the password area and consider that a master password. You can than create and manage another "user" password from this admin area under Setting > Password.
This admin area is not restricted by password
If you don’t have Page Safe Stack you can follow the same process, but with the TCMS protect stack. The dowside of this is that you won’t have the CMS compatibility. You will be able to change password only within Rapidweaver.