Overview
Last Updated: 2023-10-29 01:59:16
For example, you've created a simple website consisting of five web pages for your fishing hobby. Later you want a blog and perhaps even forums for hobbyist to signup to and participate in. This can be achieved using plugins.
Plugins consist of three parts, the admin ( your administrative portal ), the client ( your website ) and the API ( extension to your HTTP API access ). If you know you are not developing your own software to interface with your site it's good practice not to install the API part.
During installation, you will be asked which parts of the plugin you want. Some plugins require both the admin and client but others give your the option of either which can drastically change the behavior of your website.
Each plugin comes with it's own set of website endpoints. This is for integrating the feature when designing web pages. The installation comes with predefined templates which bootstrap the experience. You can modify these templates manually or within the designer. The endpoints become more important when you're replacing and designing one from scratch. Read the documentation to learn more about website end points ( not to be confusing with the template API ).
Note: Most plugins do not increase your subscription costs but some do. Plugins that perform financial transactions have an additional cost.
Note: Plugins are not installed through your administrative portal, you must login to your fliddo account.
Note: Sometimes plugins go through drastic changes and their options become deprecated. This is rare but in the event that this should happen, your website pages/templates will not be updated. It will be your responsibility to either import the new templates or manually change your existing ones to be complaint.
A role is an access granter or can be viewed also as content restriction. Since roles are heavily integrated most plugins have the option to attached them to the dynamic content you create. Once attached, a customer/visitor will require the specific role to access a specific page.
Creating a role requires that you first decide which site it applies to, your administrative portal or website. Then give it a name with an optional description for your reference.
Note: Roles created for your administrative portal are specific to your portal, however the same role name and description can be used to create a role for your website. They are not the same!
For example, lets say you create an administrative account and also configure it to access both your administrative portal and website. You apply an admin role called "SPECIAL CONTENT" to the account and create a blog article with a client side role also called "SPECIAL CONTENT". That administrative account will require the client side role to gain access to the content.
It's best practice to give your roles a unique name across both your websites.
There are many things you can achieve with roles. Here are a few examples
- Have limited/timed access to products for members with silver/gold subscriptions by combining the Shop and Subscription plugins using roles.
- Setup exclusive content for members with silver/gold subscriptions combining the Blog plugin using roles.
- Manage staff access to your administrative portal and limiting access to specific areas with the Staff plugin using roles.