Developing Extensions for Plesk
  • Plesk Extensions in a Nutshell
  • Create Your First Extension
  • Plesk Extensions Basics
    • How to Create and Install Extensions
    • Choosing the PHP version
    • Encoding the Source Code
    • Distributing Extensions
    • Monetizing Extensions
      • Available Licensing Models
      • Issuing Extension Licenses with Key Administrator
      • Issuing Custom Licenses for Extensions
      • Obtaining the Online Store URL Correctly
      • Obtaining License Purchase URL
      • Obtaining License Upgrade URL
    • Extension Structure
    • Class Naming Conventions
    • Composer Support
    • Extensions Reference
      • API Stubs
    • Adjust Development Environment
  • Extensions Management Utility
  • Quick Start
    • Exercise 1. Tabs, Forms, Lists, Tools
    • Exercise 2. Task Scheduling and Dashboard Integration
    • Exercise 3. Plesk Entities and Authentication
  • Plesk Features Available for Extensions
    • Implement UI
      • Create New Page
        • Implement Form
        • Implement List
        • Implement Active List
        • Implement URL
        • Implement Localized Message
      • Add Navigation Elements
        • Add Tabs
        • Add Buttons
        • Add Small Buttons
      • Integrate to Plesk UI
        • Integrate to Home Page
        • Integrate to File Manager
        • Add Custom Buttons
        • Admin-only functionality buttons must not appear on other users’ interface pages
        • Functions available to Customers and Resellers must appear in all appropriate places
        • Use the visibility property to hide functions unavailable for domains without hosting and aliases
        • Take advantage of the description property
        • Make sure the different UI color schemes are supported
        • Availability in Power User View
        • Adjust pages by JavaScript and CSS
        • Use of global.js and global.css
        • Avoiding Collisions in Naming
        • Library Licensing
        • Include Content into Pages
        • Integrate with Plesk Service Plans
        • Permissions
        • Limits
        • Embed Custom Data into Plesk Lists
        • Embed Active List Components
        • Add Long Tasks
        • Extend Plesk Forms
        • Integrate with Plesk Navigation
      • Localize UI
      • Localizing Lists and Forms
      • Localization from any place of your code
      • Using placeholders in locale keys
    • Retrieve Data from Plesk
      • User
      • Storing and Retrieving User-specific Data
      • Domain
      • Retrieving domain information
      • Storing and Retrieving Domain-specific Data
      • Examples
      • Session
      • Examples
      • License
      • Information About Plesk
      • Custom Settings
      • Installed Extensions’ Meta Data
      • Retrieving Extensions Data
      • Controlling Extensions
    • Communicate with Plesk API
      • XML API
      • Error Handling
      • Command-Line Interface
      • Executing Utilities
      • Executing Privileged Utilities
    • Store Data of the Extension
      • The Key-Value Storage
      • Encrypting Data
      • Key-value Cleaning
      • Remarks
    • Backup and Restore Extension Data
      • Working with Custom Backup Storages
      • Authorization
      • Working with Files
      • Testing Your Extension with Custom Storage
    • Manage Files
      • Domain Files and Directories
      • Server Files and Directories
      • Working with Archive Files
    • Implement Your Own Authorization
      • Authentication Hook
      • Confirming Authentication
    • Subscribe to Plesk Events
      • handleEvent Method
      • Object Types and Actions
      • Old and New Values Combinations
      • Old and New Values Description
      • Add Custom Events
    • Integrate with System services
      • Manage Services
      • Web Server
      • Adding Custom Configuration
      • Updating Domain Configuration
      • Mail service
        • Hooking Points
        • Handler Calling Conventions
          • Command Line
          • Arguments
          • Processing Messages
        • Managing Handlers
          • Registering Mail Handlers
          • Viewing Mail Handlers
          • Removing Mail Handlers
          • Disabling/Enabling Mail Handlers
        • Implementation Notes
      • DNS
        • Third-Party DNS Services
        • Integration Script Input Parameters
        • Integrating Plesk with a Third-Party DNS
        • Verifying Successful DNS Zones’ Synchronization
        • Verifying Operations with Synchronized DNS Zones
    • Scheduling Tasks
    • Send Email Notifications
  • UI Design Guide
    • Navigation
    • Lists
    • Forms
    • Status Indicators
    • Messages
    • Modal Windows
    • Groups
    • Objects
    • Background Tasks
  • Testing Extensions
    • Configuring System for Testing
    • Installing and Uninstalling System Packages
    • Testing Interaction with External Services
  • Extension Examples
  • Troubleshooting
Developing Extensions for Plesk
  • Docs »
  • UI Design Guide »
  • Navigation

Navigation¶

Main menu¶

The main menu is located on the left side of the screen and enables navigation among the main functional sections. The structure and contents of the Main menu depends on the selected Plesk view mode: Power User and Service Provider.

Power User Service Provider
image-79803.png image-79804.png
  • Power User view is designed for the web professionals and web admins who use Plesk to manage a server for their own needs.
  • Service Provider view is designed for users who sell hosting services.

More information on the different interface view modes is available here: The Plesk GUI.

Path bar¶

The Path bar is displayed at the top of the page, above the page title.

image-79805.png

Its function is to display the exact place of this page in the hierarchy of navigational structure of Plesk. It also allows to quickly navigate to higher levels by clicking on the corresponding elements.

Note

The Path bar works differently from “breadcrumbs”, it does not represent the history of user’s navigation.

The Home element of the Path bar is unavailable in the Power User view mode.

Sometimes, the forming of the path is a little more involved. For example, if we start at the Subscriptions page and go to a page that is part of a specific subscription (e.g., File Manager), the Path bar will be extended with the name of the selected subscription following the name of the tab that contains the link to the selected page.

Example: The Path bar at the Subscriptions page.

image-79806.png

Example: The Path bar at the File Manager page for the corresponding subscription.

image-79807.png

Side bar¶

The Side bar is located on the left side of the page. Similar to tabs, the function of the Side bar is to group the content by type and to enable navigation among the groups.

image-79808.png

The Side bar must be used in the following cases:

  • The groups require description,
  • There are too many groups to use horizontal tabs to represent them,
  • The horizontal tabs are already present on the page and further grouping is required as in the example below.

image-79830.png

Internal links¶

Internal links are used to quickly direct a user to one of the product pages.

image-79831.png

Visually, the internal links are indistinguishable from external links.

Object switcher¶

The Object switcher appears immediately following a name of an object like a subscription or a customer account. It is used to switch between objects of the same type.

image-79811.png

Tabs¶

The Tabs bar appears at the top of the page, just below the page title.

image-79812.png

The tabs provide the ability to quickly switch between different sections of the same page.

Avoid using too many tabs. Do not place two rows of tabs on a page or let tabs carry over into a second line.

image-79832.png

There are other means of further organizing information on a page, like Subnav.

Use tabs strictly for navigation. Clicking a tab can only lead to displaying new information, it cannot be used to execute an action. When naming tabs, use nouns that best describe the corresponding content. Do not use verbs to name tabs.

Subnav¶

The Subnav is an auxiliary navigation element, which can serve as a second line of tabs, where necessary.

image-79814.png

Page title¶

The Page title is displayed at the top of the page and explains what kind of information and controls this page contains.

image-79815.png

The Page title may contain a link in it, which leads to a page that contains information on the corresponding object.

The Page title may also contain an Object switcher.


© Copyright Plesk

Built with Sphinx using a theme provided by Read the Docs.