Site Designer V5 build 3532 is available for download.

The latest release received the following changes:

• The Text Editor font control was refreshed.
• The app now auto-generates a "custom\_fonts" folder.
• Under app Preferences, you can enable the option to Preload fonts for GDPR regulations.
• Added custom fonts alert wording review.

Site Designer V5 build 3536 is available for download.

• This new release features an easy way to position your slider precisely. Simply click the two vertical dots on the far right of the toolbar to access the controls. Enter your desired location, and the slider will instantly move to that spot.
• A shared folder can be completely copied to an export/publish folder.
• Added a shortcut to display slider position control.

Site Designer V5 build 3541 is available for download.

• Changed the Toggle Breakpoint Wording for single breakpoint to make it easier to understand
• Added a shortcut to change the displayed unit.
• Improve generated sitemap.xml and robots.txt files with URL of domain.
• Updated the app's sitemap.xml generation

Big news! We're delighted to unveil our newest build, Responsive Site Designer version 5.1, packed with updates to supercharge your SEO efforts, enhanced Page Manager functionality, and introduce a sleek new Light Mode for a fresh design experience!

With Light Mode, you can enjoy designing websites with a sleek and modern interface that reduces eye strain and enhances readability. Whether you're working late into the night or simply prefer a brighter workspace, our new Light Mode is designed to cater to your preferences.



Switching to Light Mode is easy! Simply go to the Preferences in the app and select "Light Mode" to activate the new design. You can switch back to Dark Mode at any time, giving you the flexibility to choose the mode that best suits your needs.

Here is a breakdown of what is new:

SEO Controls & Page Manager

• Added the ability to set "No index" and “No Follow” meta tag.
• We have included a character counter for the Page Title and Page Description controls.
• Improved language detection algorithm.
• Added Page Title Control description and Page Control Description.

Bug Fixes

• Hide Set Slider Position Controls in Device View Mode.
• Updated the workflow of the Device View action to hide them when entering Device View Mode, and show them again exiting Device View Mode.

The new Site Designer 5.1 (build 3567) is now live. In this latest release you will find the following updates:

• Introduced multi-level menu controls, with an option to specify which control activates the new menu feature.
• Implemented support for new Color Schemes in Native Areas.
• Updated the Light UI based on user feedback.
• Added logic to manage the Light Color Scheme in the Native UI.
• Enhanced Light UI contrast by darkening the general font.
• Increased tip base font weight for improved legibility.
• Fixed UI issues in the Code Editor Settings dialog.
• Adjusted Light Color Scheme UI elements: Cancel button, drop down arrows, and spinners.
• Introduced Scheme-based background color for tips.
• In the Page Manager, increased font weight (Light Color Scheme only) for better contrast.
• Updated sub-panel tip colors in the Light Color Scheme, while keeping them unchanged in the Dark Color Scheme.
• Added Color Scheme-based zoom-in/out icons in Templates, Components, and Resources dialogs.
• Ensured the default application color scheme is correctly set.

New Components!
Today we have also released new navigation menu components. Check out the 5 multi-level navigation menu components tailored for each Site Designer CSS Framework.



These ready-made menus come with drop down options, providing ample space to link additional content. Easily customize them to match your style. Download them for free here: https://components.coffeecup.com/multi-level-menus.html

Enjoy the new Site Designer 5.1 (build 3599). In this latest release you will find the following updates:

• Added support for Open Graph meta tags.
  
  Open Graph meta tags are used to control how URLs are displayed when shared on social media. For example, without Open Graph meta tags, the link for Wikipedia looks like this:
  https://www.wikipedia.org/
  
  With Open Graph meta tags, the link for Wikipedia looks like this:
  
  
  
  The link is displayed along with a title, description and image. The meta tags are added to the page <head> section of the web page.
  
  A new section, “Open Graph Settings”, has been added to the Page Manager. Here’s an example showing how it might be filled out for a page advertising Site Designer.
  
  
  
  Note that if “Online Image” is selected, it must be a complete URL, not relative.
  
  If a local image is selected, it will be converted to a complete URL on export. If a domain was specified in the settings page, it will be used to generate the full URL. Otherwise, the constant
  “REPLACE_WITH_YOUR_SERVER_PATH/” will be prepended to generate the full URL.
  
• Open Preview from a custom path
  
  Site Designer has recently added more coding capabilities. In many cases, the effects of these coding capabilities cannot be observed directly in the browser preview because some files need to be compiled and due to security issues.
  
  Site Designer now supports opening the browser preview in a local server directory. This eliminates the need to export the project first and then copy it to a server folder before launching a browser.
  
  To use the new custom path preview feature, go to Settings and enter the local path in the field “Custom Local Preview Path”
  
  
  In this example, the custom preview path is set to “C:\tmp\testing”
  
  When you’re ready to preview, select “Preview On”-> “Custom Preview Path”. The preview will open in the custom path specified.
  
  
  
  Note that PHP files will not show up on export to the custom preview path. This limitation will be removed in a future release. If you already have PHP files on your local disk, they can be used with your preview.
  
• Elements tree nested nodes indent
  
  The nesting level indent has been increased in the element node tree to make it easier to see the nested nodes. (The increased indent only applies to levels > 3)
  
  Before and After Comparison:
  
  
• Google Map Element Improvements
  
  The Google map element has been updated to support setting the language and region codes.
  
  
  
• Improvement to component importing. Site Designer no longer asks user to choose a category for EVERY component to be imported without displaying the name of the component.
  
  Previously, when a user wanted to import several components at once into Site Designer from the Components Dialog, the user would be asked to choose a category for each component.
  
  There was no option to add all selected components to one category.
  
  Site Designer has been updated to allow the selection of a category when importing several components. There is no longer a need to select “done” after each imported component.
  
• Predefined lists of values and descriptions for attributes
  
  This task was implemented in preparation for the upcoming CMS release.
  
• Set Slider Position Tip
  
  Added a tool tip to explain how the control works.
  
• Added Instructions to create a Coffeecup site on S-Drive Settings Publish Tab
  
  Previously, if a user was logged in and didn’t have any sites created, an empty box would appear with no action or explanation describing how to create a new site.
  
  Updated Site Designer – added a “?” button to the right of the Publish dialog. When clicked it will open the SD User Guide in the Publish & Export section.
  
  
  
• Background video elements tip
  
  Added a tooltip to explain how the Background Video Element works.
  
  
  
• Improve wording for Components Style Conflicts
  
  When adding a new component to the project and a styles conflict occurs, the previous wording for the conflict notification was:
  
  “The component you are adding contains selectors that are used on this page with different styles rules.
  
  To avoid conflicts they will be appended. That means that [project_framework] classes might need to be re-added to create the original component appearance.”
  The wording has been improved: