Roadmap of migrating kaizen -> into new caesar theme generator

[koskinpark]

Required for alpha release:

• [ ] Naming of the new theme generator. (caesar or some other)
• [ ] Ability to generate theme by different ways:
• • [ ] Generate theme using php & drupal command generate-theme https://www.drupal.org/node/3206389
• • [ ] Generate theme using npx
• • [ ] Generate theme using docker container (probably npx, but called from docker)
• • [ ] Should we release a new contrib starterkit theme on d.org -> store theme generator on git.drupalcode.org ? or skilld's github ?
• [x] Replacement of webpack by vite
• [x] Storybook v7
• [ ] Re-think the naming of sub-folders in theme
• [ ] Rework component generator (kaizen-cg) to follow new concept of doing components.
• • [ ] Review component-name.js file inners for component generator
• • [ ] Review component-name.yml file inners for component generator
• • [ ] Review component-name.twig file inners for component generator
• • [ ] Review component-name.stories.js file inners for component generator
• [ ] Define a list of all basic components (texts, form element's components, page layout maybe, something else?)
• [ ] Code all basic components, defined in (7)
• [ ] Write detailed README of how to use theme generator and component generator
• [ ] Define & code a list of drupal's breakpoints
• [x] Add svg-sprite generator
• [x] Add favicon generator
• [x] Update prettier, stylelint, eslint, browserlist configs to follow latest drupal core
• [ ] Review themename.theme file. What's required to be inside by default?
• [ ] In which folder(s) to build assets
• [ ] Define where npm libraries should live / how should be used & apply solution
• [ ] How to define & attach drupal libraries for patterns / no patterns.
• [x] Review postcss config & kick/add plugins which we still need/no need
• [ ] Keeping compiled assets in git, but withthout external libs sources
• [x] Add support of yml in storybook with UI Patterns based contents
• [x] Add support of most of drupal's regular twig functions in storybook
• [x] Rework kaizen-breakpoints package to something more simple -> to be able to use drupal's breakpoints in css and js
• [ ] Define what CI requires from our theme generator & update in SDC
• [ ] Review of global scripts attached
• [ ] Build test page to test easily a whole caesar's functionalities
• [ ] Provide concept of creation all image style configs and responsive image groups in storybook / re-use those configs in storybook to build images ?

Potential features which can be included in alpha release

• [ ] Define coding-standards of writing css variables
• [ ] Add image-optimizer scripts, kinda https://squoosh.app/
• [ ] Convert all images, attached from css -> to base64 format ?

Post-release features:

• [ ] Ability to simply share components between projects ?

[andypost]

Why new name? The kaizen-tg already doing some of tasks, caezar is good for base theme but maybe we can ressurect zen?

[iberdinsky-skilld]

Step by step roadmap

Prepare

• [x] Replacement of webpack by vite
• [x] Storybook v7
• [x] Add svg-sprite generator
• [x] Add favicon generator
• [x] Update prettier, stylelint, eslint, browserlist configs to follow latest drupal core
• [x] Review postcss config & kick/add plugins which we still need/no need
• [x] Add support of yml in storybook with UI Patterns based contents
• [x] Add support of most of drupal's regular twig functions in storybook
• [x] Rework kaizen-breakpoints package to something more simple -> to be able to use drupal's breakpoints in css and js
• [x] Provide concept of creation all image style configs and responsive image groups in storybook / re-use those configs in storybook to build images
• [ ] Generate dummy page with components based on new approach. (most simplest styles/no pixel perfect/no hovers etc).
• [ ] Adapt components from SB to Drupal using different adaptations technics.

Decisions

• [ ] Define & code a list of drupal's breakpoints
• [ ] Review themename.theme file. What's required to be inside by default?
• [ ] In which folder(s) to build assets
• [ ] Define where npm libraries should live / how should be used & apply solution
• [ ] How to define & attach drupal libraries for patterns / no patterns.
• [ ] Keeping compiled assets in git, but withthout external libs sources
• [ ] Define what CI requires from our theme generator & update in SDC
• [ ] Review of global scripts attached
• [ ] Re-think the naming of sub-folders in theme
• • [ ] Review component-name.js file inners for component generator
• • [ ] Review component-name.yml file inners for component generator
• • [ ] Review component-name.twig file inners for component generator
• • [ ] Review component-name.stories.js file inners for component generator
• [ ] Define a list of all basic components (texts, form element's components, page layout maybe, something else?)
• [ ] Code all basic components, defined in (7)
• [ ] Naming of the new theme generator. (caesar or some other)

Coding

• [ ] Rework component generator (kaizen-cg) to follow new concept of doing components.
• [ ] Ability to generate theme by different ways:
• • [ ] Generate theme using php & drupal command generate-theme https://www.drupal.org/node/3206389
• • [ ] Generate theme using npx
• • [ ] Generate theme using docker container (probably npx, but called from docker)
• • [ ] Should we release a new contrib starterkit theme on d.org -> store theme generator on git.drupalcode.org ? or skilld's github ?
• [ ] Write detailed README of how to use theme generator and component generator
• [ ] Build test page to test easily a whole caesar's functionalities

Potential features which can be included in alpha release

• [ ] Define coding-standards of writing css variables
• [ ] Add image-optimizer scripts, kinda https://squoosh.app/
• [ ] Convert all images, attached from css -> to base64 format ?

Post-release features:

• [ ] Ability to simply share components between projects