[ 
https://issues.apache.org/jira/browse/CAMEL-15337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177364#comment-17177364
 ] 

ASF GitHub Bot commented on CAMEL-15337:
----------------------------------------

zregvart opened a new pull request #459:
URL: https://github.com/apache/camel-website/pull/459


   Based on work by @AemieJ in #446 this simplifies the implementation by
   relying on the implementation already provided by Antora.
   
   The main issue with reusing the Antora implementation was that the
   markup of rendered Asciidoc contains `<div class="sect?">` elements
   around the chapters. Hugo rendered, static, content does not have this,
   so the logic for the _on this page_ functionality needed to be adjusted
   slightly because of this.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Create toc for hugo pages
> -------------------------
>
>                 Key: CAMEL-15337
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15337
>             Project: Camel
>          Issue Type: Task
>          Components: website
>            Reporter: Aemie
>            Priority: Major
>              Labels: suggestions
>         Attachments: toc-hugo.png
>
>
> The antora UI makes use of the table of content so when a webpage has a large 
> amount of content, it makes it easier for the user to navigate. 
> I have observed this in Hugo pages such as articles that have a large amount 
> of content as well. So to improve user experience over the Hugo content as 
> well, I suggest adding the toc for the Hugo pages excluding the blog posts.
> I have added an image of how it looks. It uses the same CSS as that of antora 
> UI. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to