Removed primary theme variant (primary - fully styled theme for drupal), because we don't use it / we don't support it / there is much better alternatives for the usage if no design expected on the project (like drupal's themes Claro, or Olivero, or Gin, or other). For little modifications (per project) we can easily install new theme with the help of our theme-generator alongside another base theme and provide minimal fixes if Claro / Olivero / Gin / other defaults are not enough.
Changed versions of all still-alive packages to 2.0.0-alpha.0. Actually all still-alive packages were updated at this PR: they are all improved with all modern techniques i know to make developing process simpler and faster. Target is to merge this PR, then update all packages on npm, test widely everything again and if it's fine - then change versions on 2.0.0 and enjoy to use kaizen.
Packages with versions lower than 2.0.0 can not be upgraded till 2.0.0. New kaizen is supposed to be used on new projects only.
⚠⚠⚠ Minor updates :]
Improved parsing of breakpoints for javascript usage.
Reworked @skilld/kaizen-core package. Kicked things which we are not using / makes no sense to have. Added several components (helpers) which are necessary to have on every project.
Added drupal's once() to be used in component's javascript.
Added core/once dependency to the base library
Rework of componentName.stories.js to have all the latest techniques
Updated globals.stories.js file
Added support of Drupal 10 for kaizen
Set base theme to false (instead of old classy)
Added .storybook/manager.js
Updated README.md
To be known for frontender
Added three helpers into @skilld/kaizen-core:
root-variables - littler script which puts two css variables into html tag with viewport width and viewport height calculations. It's useful for Safari browser on iOS devices where default min-height: 100vh; and min-width: 100vw can work unexpected. Here script helps.
Remains to be done
Provide screenshot.png in @skilld/kaizen-tg, to have screenshot on drupal's appearance page. It can be done in the follow-up, so it's not really blocking this PR.
Deep review of this PR from all of you. Share your eyes / opinions / feedbacks about what should be done else.
Merge PR
Update on npm
Well test of all these
... new task to fix bugs ?
... release of 2.0.0
Offtop
kaizen's logotype change? Like Kaizen 2.0, i don't know. You suggest )
❗❗❗Major updates :
2.0.0-alpha.0
. Actually all still-alive packages were updated at this PR: they are all improved with all modern techniques i know to make developing process simpler and faster. Target is to merge this PR, then update all packages on npm, test widely everything again and if it's fine - then change versions on2.0.0
and enjoy to use kaizen.⚠⚠⚠ Minor updates :]
@skilld/kaizen-core
package. Kicked things which we are not using / makes no sense to have. Added several components (helpers) which are necessary to have on every project.once()
to be used in component's javascript.core/once
dependency to thebase
librarycomponentName.stories.js
to have all the latest techniquesglobals.stories.js
file.storybook/manager.js
README.md
To be known for frontender Added three helpers into
@skilld/kaizen-core
:entity-fake-link
focus-visible
root-variables
entity-fake-link
- we had it before, but now it was moved to@skilld/kaizen-core
package. It is script for simulating link on the wrapper. For example when you want to have a whole teaser clickable, instead of only title as link. Check sources how it works https://github.com/skilld-labs/kaizen/blob/kaizen-updates/packages/kaizen-core/helpers/entity-fake-link/h-entity-fake-link.js#L42focus-visible
- helper which improves visual experience for css's:focus
& keeps accessibility, more info here: https://www.npmjs.com/package/focus-visibleroot-variables
- littler script which puts two css variables intohtml
tag with viewport width and viewport height calculations. It's useful for Safari browser on iOS devices where defaultmin-height: 100vh;
andmin-width: 100vw
can work unexpected. Here script helps.Remains to be done
screenshot.png
in@skilld/kaizen-tg
, to have screenshot on drupal's appearance page. It can be done in the follow-up, so it's not really blocking this PR.Offtop kaizen's logotype change? Like Kaizen 2.0, i don't know. You suggest )