Skip to content
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

feat: implemented new UI for Navbar and Table of Contents #3917

Merged
merged 39 commits into from
Dec 2, 2024

Conversation

berezinant
Copy link
Contributor

No description provided.

Copy link
Collaborator

@whyoleg whyoleg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
Checked mostly kt files and how it looks :)

@@ -32,7 +32,23 @@
<@header.display/>
<div id="container">
<div class="sidebar" id="leftColumn">
<div class="sidebar--inner" id="sideMenu"></div>
<div class="dropdown theme-dark_mobile" data-role="dropdown" id="toc-dropdown">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just to recheck: if users override template (e.g. for kotlinlang) everything will continue to work fine?
I mean, kotlinx.* libraries will be able to just update to Dokka 2.0.0 and everything will be fine, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I've just double checked, custom templates will still work.
However it will be needed update custom templates to align them with the changes in our templates, we'll write about it in the release notes and provide links to the templates in this PR as a reference

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!
And what will be the result if the templates will not be updated?
I mean, for now the only thing worries me here is kotlinx.* libraries because their templates are stored in kotlin-web-site repository and used by all other kotlinx libraries.

Let's imagine a case that kotlinx.coroutines will update to Dokka 2.0.0 but kotlinx.serialization will still use Dokka 1.9.20 - they will both use the same templates - how the final result will look for both libraries?

Copy link
Contributor Author

@berezinant berezinant Nov 29, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We will need to update api references for kotlinx- libraries at kotlinlang simultaneously

krutilov and others added 19 commits December 2, 2024 10:25
* feat: implemented new button states

* ktl-1608 feat: style fixes

* ktl-1608 feat: fix clear button

* fixes after rebase

---------

Co-authored-by: berezinant <[email protected]>
* feat: implemented new button states

* feat: reworked ToC appearance

* fix: moved images to assets

* fix: fix toc interactivity

* fix: fixed problem with hover on touch screens

* fix: open toc no mobile

* fix scripts loading in safari

* fix: fixed overlap of dropdown with toc on desktop

* fix: fixed closing toc on mobile

* fix: versions dropdown position

* fix: version selector position
* ktl-1727 fix: fix safari flickering

* ktl-1737 fix: fix version capitalization
@berezinant berezinant merged commit f728e3a into master Dec 2, 2024
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants