(2019-02-17, 01:10:09)Oleg06 Wrote: Is it possible to do the transliteration of the components?
https://prnt.sc/mlxcqr

• attach more common CSS styles to classes instead of #ids or nested tags, so plugin devs don't need to re-style everything (the .text class is also not self-explanatory)
  
• Make the default width something like 1280px instead of 960px, no one uses < 1024px screens anymore (I might add a PR for this if it is sensible enough)
  

(2019-02-20, 10:05:16)Tyblitz Wrote:

• ... no one uses < 1024px screens anymore...
  

(2019-02-24, 10:10:49)GORF Wrote: I would like to suggest a plugin droplet or tag registration system. When a plugin requires the user to insert a droplet or tag on to a page, all of those could be readily selectable from a list.

Example - there is a Gallery plugin and a Calendar plugin installed.

Using the Gallery, you create galleries called Wedding, Dogs, House Projects.
This generates tags like gallery_wedding, gallery_dogs, gallery_house_projects.

Using the Calendar, you create event calendars called Monthly Meetings, Special Events, Parties.
This generates tags like calendar_monthly_meetings, calendar_special_events, calendar_parties.

Each plugin would register those tags to a common database.
When editing a page, you would be able to select from a drop-down list of registered tags to use on that page:

Usable Tags:
Calendar Plugin
- calendar_monthly_meetings
- calendar_parties
- calendar_special_events
GaleryPlugin
- gallery_dogs
- gallery_house_projects
- gallery_wedding

Drag/Drop or Highlight/Add the selected tag on to the page. This would insert the tag on to the page like (%calendar_parties%) .

Someone with less coding ability could more easily add plugin components to pages with less error.