-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Allow external usage of individual components. #1
base: master
Are you sure you want to change the base?
Conversation
…components styles.
@thet You raise some ideas and questions that are so big that I cannot possibly answer them here, nor can I oversee the consequences. Do you want to set up a workshop of an afternoon or perhaps longer to discuss? |
The CSS bundle is work in progress. Whenever I have time I do a little bit. Recently I've made some improvements again and I hooked up another project to the centralised bundle to make it more robust. The fact that it's not ready is also the reason that I don't want to include CSS yet with the download on the patterns site. |
Hm... I think we need at least some CSS. |
We haven’t had any CSS on the site so far but we are in dear need of the new site and the single universal bundle. Let’s not the basic needs because we also want something extra as a next step.
… Op 8 apr. 2021 om 20:57 heeft Johannes Raggam ***@***.***> het volgende geschreven:
Hm... I think we need at least some CSS.
But I can just JavaScript-import the CSS for external libraries like the date-picker, slick-slider, tooltips and so on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
This is a proof of concept and work in progress.
The idea is to allow individual components to be usable outside this repository and not need to build/import the whole CSS bundle.
I want to individually use the CSS here in individual patterns and only if they are loaded by importing these files in JavaScript. For example like in this commit: Patternslib/Patterns@2cde595
Note this is optional and these JavaScript imports can be easily turned off (as we will be the case for ploneintranet.prototype and others without any further changes in these integration packages).
For this to achieve I have to make some adaptions.
Due to a number of open and debatable questions it's probably faster to reach the goal of a downloadable Patternslib bundle if we just build the whole CSS and offer it for download. Which is probably huge, but we can improve later and eventually build on the ideas outlined above.
Some questions to @cornae:
Related: