Problem/Motivation
We keep this issue for throwing ideas and discussion about version 3.x.
Ideas for 3.x
- Use dropdown CSS classes in navbab only when really needed - when dropdown menus are turned on. Goal is to bring more separation in our CSS components for navigation and stop overriding dropdown rules when second level is horizontal.
- Try to have page regions (other then main content) region that are more paragraphs layout friendly. This targets mostly header and footer regions - the idea is to be able to use paragraphs there instead of blocks.
- Removing on theme-options.yml should allow us to use https://www.npmjs.com/package/gulp-cached or similar solution to speed up sass:dev task when developing CSS.
- Automated tests implementation and test coverage.
- Use CSS variables
Switch all icons from Fontawesome to Bootstrap Icons.Use https://github.com/tancredi/fantasticon for SVG to font generation.Convert all margins and paddings and other sizes to rem/em so we can control them over root font-size. This will allow us to responsivly change elements size and space between them. Idea is to have a theme that automatically change it size for big/huge screens.Fluid typography - idea from https://css-tricks.com/snippets/css/fluid-typography/- Use Bootstrap responsive font sizes and spacing units based on browser viewport dimension. This replace two previous points.
- Bootstrap components implementation with the help of components module.
- Consider mixing utilities and semantically clean approach in HTML and CSS.
- Bootstrap 5 does not require jQuery any more. Try to remove as much as possible jQuery from our custom JS code.
- [LOW prio] Some kind of pattern generator for static site, https://patternlab.io/docs/ or https://fractal.build/guide/
Comments
Comment #2
pivica commented