playing with e107 dashboard

I am still here. I did a new admin theme for the old CMS and I wanted to see how hard it is for the latest version. You can't create a new admin theme because... because it is hardcoded to the bootstrap3 name. But you don't need to. The actual theme works fine. There are just small issues when you want it worked different way...  

This is not something I would recommend for using, a better idea is to improve the core itself. This is just an example of what is possible.

Implemention of custom HTML theme/design

HTML theme - no bootstrap theme, but it looks like based on bootstrap 5

CMS - bootstrap 3 by default.

Completed under 10 hours.

https://www.flyingdoctor.co.nz/

PHP 5.3

Alex made next e107 site. With his custom theme.

https://ettinajhansen.nl/

Implemention of custom HTML theme/design

HTML theme - no bootstrap theme

CMS - bootstrap 3 by default.

Completed under 10 hours.

https://www.stephenlarsenandco.co.nz/home

The list of public repos for plugins created or maintaned in some time by Jimako

The list of public repos for plugins created or maintaned in some time by me (Jimako).  Cleaning repos, deleting duplicates. 

Possibilty to add more than one category to news - actually testing on this site

Most information is in Readme file on GitHub.  I played with this area a long time ago (it is part of efiction CMS, I have something similar in my UNNuke - topic and additional topics). As I already said - I wasn't so crazy to try this :)

My vague idea was to use e_admin and then somehow change the frontend thanks e_url addon. How naive I was. 

Attempt to describe how services should/could work in my future themes. History and actual state.

What services element is? 

Even better. Is there a difference between services and features?  

Not semantically, but in template meaning? What we know:

• they have similar content: icon, title, maybe subtitle, and description.
• service's list often has a link to a separate page. But features could be services without the link
• services are mostly cards (panels), and features are mostly lists. But it can be the opposite way too. 

So, they are the same. You can see some examples here:

https://ayroui.com/bootstrap-components/features

but in some themes, they call them services... Lately, I found that some of them are services (file is service-xxx), and some are features (file is feature-xxx) So the title is confusing - feature 20 is service 07 in real use.

So, if something is called services in the theme, you can use it for features too... and the opposite way.

To be continued :)

New version of GitSync is available on Github

Theme pack synchronization support, plugins pack synchronization support, languages pack synchronization support

AYRO UI themes is general term for any e107 theme based on AYRO UI components. For now there are Aeolus and Anthena.

Aeolus theme is based on APP template and it is finished - now it is tested, adding some stuff while working on Athena.

Athena theme is based on Startup template and it is developed now. 

Both of those themes are available on github. Changing colors is the same for all themes. This is just first step.