Open tzi opened 9 years ago
PR: #7787
do we consider as API everything documented in this page?
I do not really have a huge problem with considering everything API but would prefer not to. Eg we have a PHP & JS API for notifications so developers do not really need to know the markup for notifications. Not having it API would just leave us more flexibility in changing things in the future as we will want to change things in the future again for sure. Eg maybe we want to use another UI framework (based on AngularJS, eg https://material.angularjs.org/latest/#/demo/material.components.autocomplete only an example) and there notifications etc are made completely different. It's rather a random example though. I'm ok with it as long as we're careful what we put on that page.
Could this issue be closed for 2.14.0? if not, let's move it to 3.0.0 and write here the next step / decision.
This issue isn't done, I'm moving it to 3.0.
we now have a "Demo page" listing CSS styles that are "Api" so the remaining step is to advertise this publicly on developer.piwik.org
Hi! Is this page public yet?
Nope, not yet. Need to find a way to make it public somehow. Currently the page needs some admin access + enabled development mode
Hi piwik team!
As discussed in #7390, it could be urseful to have a CSS style guide for the developers.
The purpose of this minisite is to document our CSS code base, especially the reusable components:
It could start with a simple page, and be improved step by step. There is also some tools to do it like Style Guide Boilerplate, Pattern Primer or Module Gallery.
Cheers, Thomas.