Plugins
When the website has to do something,not just say something.
Plugins turn a castomUI project into a working system: campaigns sent to the people in your data, records matched by rules, a member community moderated from one dashboard. They are installed from a catalogue, configured with a form, and they work on the same datasets your pages already use.
Catalogue,
settings form,
installed instance.
The plugin catalogue lists what can be added to a project. Installing one opens its settings form, generated like every other form in castomUI, so configuring a plugin means filling in fields rather than editing a file.
What you install appears under installed plugins, where each instance keeps its own settings. The dashboard a plugin brings — for starting a campaign, running a match or moderating users — opens as a window in the workspace, beside the preview, like everything else.
The important part is where the data lives. Plugins work on datasets: the members, contacts or records a plugin handles are the same records your dataset pages publish, in MongoDB or MySQL, or in a database you connected as an external source.
- ✓Mailing systemInstalled · Dataset: newsletter subscribers
- ✓Users handling systemInstalled · Dataset: members
- +Matching systemIn the catalogue · Install opens its settings form
- +Eclicks PROIn the catalogue · Connects to your Eclicks account
Invented dataset namesEach instance keeps its own settings
In the catalogue
Four plugins,
four jobs.
Mailing system
Bulk e-mail campaigns driven by datasets. The recipients are records you already hold, and campaigns are started from the plugin's dashboard.
Because the list is a dataset, there is no export to a second tool and no second copy of your contacts to fall out of date.
Eclicks PRO
A connection to Eclicks, covering its contacts, groups, campaigns and templates.
For teams whose e-mail marketing already lives in Eclicks, it brings that work alongside the website instead of asking anybody to move it.
Matching system
Matches users or records to each other by rules you set, and starts a matching run from its dashboard.
The shape suits anything that pairs one list with another: members with members, candidates with offers, requests with the people who can answer them.
Users handling system
Moderation for a member community, gathered in one dashboard: the users, their profiles, the images they upload, the reports about them and the numbers that describe all of it.
Described in full below, because communities are where websites most often need a person with tools.
The right tool for the job,
already in the tin.
Moderating a member community.
A site with members is a site with moderation, whether anybody planned for it or not. The Users handling system gives that work a proper place.
Browse users and open any profile. Look through the profile gallery to see the community the way its members do. See the testers in their own list. Review uploaded images and remove the ones that should not be there.
Abuse reports collect what members flag about each other, and statistics show how the community is doing. On any account you can block, activate or verify it, send a warning, or send a message.
- RReport · profile imageFlagged by another member · image opened for review
- ✓ActionImage removed · warning sent to the account
- RReport · messagesFlagged by another member · account under review
- !ActionAccount blocked · message sent explaining why
- VNew accountDetails checked · verified
Synthetic example, no real usersBlock · Activate · Verify · Warn · Message
Why plugins sit on datasets.
A website builder that sends e-mail usually keeps its own list, separate from the site's content and from the business's records. Within a year there are three lists, and none of them agrees with the others.
castomUI avoids that by having one kind of data. A dataset has a structure you define with typed fields, records you edit through a generated form, and views that decide what is shown. Pages connect to views to publish records; plugins work on the same records to act on them. When a record changes, the page that publishes it and the plugin that acts on it are looking at the same change, because there was only ever one copy.
On communities: every one of them eventually produces a member who reads the terms more carefully than the people who wrote them. The abuse reports tab is for the day that happens.
Questions
The ones people ask about plugins.
Do I need a dataset before installing a plugin?
Plugins work on datasets, so the data they handle — subscribers, members, records to match — lives in one. You can create the dataset in castomUI or connect an existing MongoDB or MySQL database as an external source.
Can I use my existing database?
Yes. External sources connect MongoDB and MySQL, both also through castomoConnector, and OlgroupPanel, with an address, login and key.
How do I configure a plugin?
Installing it opens a settings form. The installed instance keeps those settings and can be changed later from the list of installed plugins.
Is Eclicks PRO the same as the Mailing system?
No. The Mailing system sends campaigns from your datasets inside castomUI; Eclicks PRO connects to an Eclicks account and its contacts, groups, campaigns and templates.
Every window,
one website.
Open the editor and arrange them the way the job needs.
Open castomUI See pricing