Anton Berezin
According to the [spike](https://github.com/Kotlin/dokka/issues/3423) for decomposing styles.css we need to break down styles into separate components to enhance maintainability of styles, simplify development and adding UI components from design
According to the [spike](https://github.com/Kotlin/dokka/issues/3423) for decomposing styles.css we need to add some processing of styles from plugin-base. **Now:** * plain css styles from `dokka-subprojects/plugin-base/src/main/resources/dokka/styles` are just copied to the resources...
Fixes: #3460 #3461 #3462 The UI component is just a couple of js and css files which are conntected to the markup by bem, if possible The assets (ts and...
It'd be helpful to create some UI screenshot tests to be able to automatically find possible regressions. A [demo project](https://github.com/Kotlin/dokka/issues/3468) could be used to run these test against it
Provided with microdata markup dokka's html pages could gain several improvements: * better indexing by search engines and possibly for AI — seems rather useful and could help users find...
According to the [spike](https://github.com/Kotlin/dokka/issues/3423) for decomposing styles.css we want to introduce some linting for css/scss source files including in order to avoid errors and enforce the convention for css selectors...
According to the https://github.com/Kotlin/dokka/issues/3423 for decomposing styles.css after [adding processing of styles](https://github.com/Kotlin/dokka/issues/3460) it'd be good for a page loading optimisation to minify resulting css files
After update of [Stdlib API Reference pages](https://kotlinlang.org/api/latest/jvm/stdlib/) we received feedback that "Since @version" block draws too much attention, probably it would be better to restyle it [Example page](https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/)  [KTL-1488](https://youtrack.jetbrains.com/issue/KTL-1488/Dokka-restyle-Since-version-block-now-it-draws-too-much-attention)