Branding Editor at a Glance

The Branding Editor enables editing and previewing Slate branding while keeping current branding files unchanged. As you create and maintain a consistent brand identity across all of your Slate pages, you can test new branding ideas before you implement them in production.

Use the Branding Editor to:

• Change your logo, colors, or fonts
• Update your header and footer designs
• Add new branding elements to your pages
• Test different branding layouts
• Create custom branding for specific portals or pages

To access this tool:

To edit Slate branding in the Branding Editor:

In-Depth

The key in the following image corresponds with each item in the list:

1. Files: This menu displays any files located in the dev folder of Database > Files (formerly File Editor).

   Files in the Branding Editor.

   Corresponding files in dev.

   To delete a file, click the    to the right of the file name. Click OK in the system dialog to confirm deletion.

   

2. New: Creates a new empty file. A prompt appears to enter a file name. Click Create to create a new blank file and save it to the dev folder.

   

   Only files with the following file extensions will be editable in this interface:

   • • .css
     • .xslt
     • .html

3. Save: Saves changes to the current file.

4. Preview: Opens a new tab to display the entered URL with styles from the build files in the dev folder of Files applied. 

   Required fields:

   • URL: Enter a Slate page to display. For example:
     • /register

     • /register/{add a form url} (See example images below)

     • https://demo-slate.technolutions.net/portal/status

   • Preview as: Enter the name of a record you'd like to impersonate to view the page. 

     

   When you click Preview, a new tab opens displaying the URL you entered. A banner indicates you are impersonating your selected record in Development Mode, meaning dev styles are being applied.

   Any subsequent pages opened from within the preview will also be in Development Mode until you click the Dismiss link. For example, if a form is opened, it will also display with dev branding.

   

5. Upload: Select an existing local file to upload to the dev folder to be edited.

   

     Note:

   You may not overwrite an existing file via upload. Attempting to upload a file with the same name as a file already in the dev directory will cause an error message to appear. Delete the existing file by clicking   prior to uploading a new version with the same name. 

   

     

6. Import Current: Copies all files currently in the share folder in Files to the dev folder for editing.

   Important!

   This will overwrite the files that currently exist in the dev folder, and any edits will be lost.

   

7. Publish Changes: Copies all the files in the dev folder and writes them to the shared folder in Files, overwriting any existing files with the same names. The dev files are not removed.

   

8. Exit: Returns to Database.