For new USERS the main problem in Concrete5 - Is the JS conflicts

Permalink 1 user found helpful
The convert html to C5 its really easy and intuitive. The problem: Its really really easy to break the ui or to create a lots of bugs with other framework (Not all users use Bootstrap. and also in bootstrap u can find not official versions - "rtl" for example).

I really love this CMS. but i think a lot of new users "leave" this CMS because when you take foundation6, materilazeCSS, uiKIT and a lot of other nice CSS frameworks (that comes with JS and components) its always "BREAK" and you need hours to fix all the bugs.

Or you have a html Theme from the markets - with popular JS libraries - and again break.

The main problem is with: All the famous sticky components (scroll spy, sticky-nav) . Also modals (that have z), and off-Canvas (popular mobile-nav).

This is a really really important issue - but u have 1-2 pages of docs and ZERO video tuts for this (in "converte html to Concrete5" official video - you have 1-2 minutes about this).

I talk in general - C5 is not only for JS expert that know to get inside code and fix bugs. or to 100% understand the consept of assets.

View Replies:
JohntheFish replied on at Permalink Reply
Not a complete solution to your problem, but this howto helps with the css part.
siton replied on at Permalink Reply
Thanks, but I dont want to add selectors to all of my CSS - and add more and more un-semantic html tags and wrappers.

I think this solution could work but is weird - and again new user need hours of search for finding this trick (and not all users know less / sass)
siton replied on at Permalink Reply 1 Attachment
The Core UI need to work great with The Popular CSS frameworks components and JS (at least 4-5) without the need of change so much

Foundation 5, 6

Look at the pic i added - For example in this Pinegrow - Html Editor - You have check box (active-deactive assets) to tell the Editor your framework (simple ui) - and its come like C5 with Default - Better Consept
OKDnet replied on at Permalink Reply
Your point is a good one.
Not only that, I like the concept of a Library/Plugin Manager for the Core UI, all controlled via a GUI.

If I'm correctly getting your point and how that application in the screenshot works, I envision handling the core UI via multiple frameworks, each doing the same thing, but done by whichever one is selected. It would probably be a fairly large endeavor to make that happen, but arguably worth it?
siton replied on at Permalink Reply
I dont know what is the specific solution - but i think the "ASSET" model by hard code - its hard for non-developers (and also developers ask a lot in the forums about this).

Its Easy to see all the core assets in a list in the Core UI - and check - unCheck things like Pinegrow Consept

Even Without any functionality - only list for view by (name-version-link)- will help the users:
- jQuery - v1.11.3 (link)
- jQuery UI - v1.11.4 (link)
- (link to the libary link:
- more assets....
MrKDilkington replied on at Permalink Reply

I recommend reading JohntheFish's tutorial on scoping your CSS. When using a CMS, there will be a lot of CSS involved, the concrete5 interface, your theme, add-ons etc. Without scoping your CSS, it will be global and affect things like the interface. Scoping your CSS when using a CMS, or combining CSS from different sources, is highly recommended.

When creating a concrete5 theme, a wrapper div is required. This wrapper div will automatically be given the class "ccm-page". This provides you with a class to scope your CSS with. Allowing you to target just your theme and blocks within it.

Scoping does not require Less or Sass, but it is time consuming without it.

This is covered in the documentation:

The Elemental theme uses Bootstrap 3 and there are marketplace themes using Foundation 5.

Have you read the documentation on assets?