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

Nice doc with Nav :) #148

Merged
merged 1 commit into from
Jul 18, 2023
Merged

Nice doc with Nav :) #148

merged 1 commit into from
Jul 18, 2023

Conversation

ia3andy
Copy link
Contributor

@ia3andy ia3andy commented Jul 18, 2023

Inspired by other extensions like:
image

@gastaldi I didn't find a way to test the nav locally

@ia3andy ia3andy changed the title Nice doc :) Nice doc with Nav :) Jul 18, 2023
@ia3andy ia3andy force-pushed the doc branch 2 times, most recently from 190f751 to d3eb7a9 Compare July 18, 2023 09:57
Copy link
Contributor

@FroMage FroMage left a comment

Choose a reason for hiding this comment

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

So, what exactly did you do to index? Just split it in two? The diffs don't show me what you did.

include::./includes/attributes.adoc[]
:config-file: application.properties

* xref:index.adoc[Getting started]
Copy link
Contributor

Choose a reason for hiding this comment

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

Can't we generate this TOC? It's bound to be forgotten/out of sync, no?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@gastaldi ? Could generate it from the == of all the pages?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it should be fine as H2 titles don't change everyday, but better have it generated if possible yeah

Copy link
Member

@gastaldi gastaldi Jul 18, 2023

Choose a reason for hiding this comment

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

Maybe there is an Asciidoc macro or something that will generate the TOC based on the file. I know there is this: https://docs.asciidoctor.org/asciidoc/latest/toc/ but it doesn't seem to work for XREF links

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

So, what exactly did you do to index? Just split it in two? The diffs don't show me what you did.

I:

  • splitted
  • added titles on each pages
  • added manual fragments [#...]
  • Created the Nav Manually

@FroMage
Copy link
Contributor

FroMage commented Jul 18, 2023

Why manual fragments instead of the auto-generated ones?

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

Why manual fragments instead of the auto-generated ones?

So they don't change if the title changes as they are referenced

@FroMage
Copy link
Contributor

FroMage commented Jul 18, 2023

OK, very good point :)

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

@FroMage did you approve?

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

(we can always switch to auto-generated if that become something)

@gastaldi
Copy link
Member

To test the nav locally I think you'd need to run Antora to generate the website by changing the Antora playbook to point to your repository/branch

@FroMage
Copy link
Contributor

FroMage commented Jul 18, 2023

To test the nav locally I think you'd need to run Antora to generate the website by changing the Antora playbook to point to your repository/branch

Actually it's worse than this. Now my generated index.html page contains nothing and I can't navigate and see the rest of the docs locally before I push anything.

How do I test my docs locally now?

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

To test the nav locally I think you'd need to run Antora to generate the website by changing the Antora playbook to point to your repository/branch

Actually it's worse than this. Now my generated index.html page contains nothing and I can't navigate and see the rest of the docs locally before I push anything.

How do I test my docs locally now?

I thought I broke something but yeah I think we need to have some nav generated locally

It seems to be nice:
https://docs.quarkiverse.io/quarkus-renarde/dev/index.html

@FroMage
Copy link
Contributor

FroMage commented Jul 18, 2023

Yeah, it looks nice, on the surface, BUT… now I have two navs: one at the left which is missing deeper levels and is not generated, and one at the right which is missing higher levels but is generated.

This is really bad UI. How can we fix this?

@gastaldi
Copy link
Member

Yeah, I agree. We should somehow adapt the local generation to use Antora and its layout (as it's built in quarkiverse-docs)

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

@gastaldi @FroMage

I don't think it's BAD UI, people tend to see things differently. Still I think we should have a common experience, let's continue the discussion there where @holly-cummins has already started some comparison with other docs:
quarkiverse/quarkiverse-docs#102 (comment)

@ia3andy
Copy link
Contributor Author

ia3andy commented Jul 18, 2023

@gastaldi for some reason the config reference is not working, I think it wasn't already before my change any thoughts?

@gastaldi
Copy link
Member

@ia3andy I browsed the sources and didn't find any interface with @ConfigMapping or @ConfigRoot, what do you mean?

@FroMage
Copy link
Contributor

FroMage commented Jul 19, 2023

I seem to have also lost the favicon I recently added :(

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