[jira] [Commented] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053461#comment-17053461 ] Aashna Jena commented on CAMEL-13902: - Hi! Can I take up this issue? I'm looking at all the links given the comments above and I'd love to make my first contribution to the Camel website > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: camel-projects.png > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel-projects-2.png, camel-projects.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057102#comment-17057102 ] Aashna Jena commented on CAMEL-14581: - Hi [~zregvart], The Projects menu has many submenus, and each submenu was leading to pages with very limited content like [this Camel K Page|https://camel.apache.org/projects/camel-k/] or this [Camel Quarkus page|https://camel.apache.org/projects/camel-quarkus/]. I removed the submenus and created a webpage for Projects (refer to the screenshots below). I added all the projects with short descriptions and links to their documentation/manuals. I also made sure that the content is displayed similarly for all projects, because earlier some submenus were leading to very little content and the Spring Boot Starters submenu was leading directly to its manual. I have made a new _index.md file in /content/projects/ and added a /layouts/projects/ folder which contains a projects.html file, so that we can change the layout if necessary. Additionally, we can delete all the extra .md files in /content/projects (camel-k.md, camel-quarkus.md, camel-kafka-connector.md) because I've included their content in _index.md. I can put a PR for this as soon as you approve of these screenshots! Thanks! !camel-projects.png! !camel-projects-2.png! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel-projects-2.png, camel-projects.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: camel-projects-2.png > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel-projects-2.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14689) Update contributing guide
[ https://issues.apache.org/jira/browse/CAMEL-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057031#comment-17057031 ] Aashna Jena commented on CAMEL-14689: - Hey [~zregvart], I have raised [this PR]([https://github.com/apache/camel/pull/3624)] against this issue. > Update contributing guide > - > > Key: CAMEL-14689 > URL: https://issues.apache.org/jira/browse/CAMEL-14689 > Project: Camel > Issue Type: Improvement > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Time Spent: 10m > Remaining Estimate: 0h > > I noticed that in the [contributing > guide|https://camel.apache.org/manual/latest/contributing.html] we mention > Subversion. We should go over [the > document|https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/pages/contributing.adoc] > and update it to reflect the current practices. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057105#comment-17057105 ] Aashna Jena commented on CAMEL-14581: - I'm very new to the Antora and Hugo framework, so please let me know if I'm doing something the wrong way. I have many more ideas for improving the usability of the website! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel-projects-2.png, camel-projects.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14689) Update contributing guide
[ https://issues.apache.org/jira/browse/CAMEL-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057031#comment-17057031 ] Aashna Jena edited comment on CAMEL-14689 at 3/11/20, 2:05 PM: --- Hey [~zregvart], I have raised [this PR|https://github.com/apache/camel/pull/3624] against this issue. was (Author: aashnajena): Hey [~zregvart], I have raised [this PR]([https://github.com/apache/camel/pull/3624)] against this issue. > Update contributing guide > - > > Key: CAMEL-14689 > URL: https://issues.apache.org/jira/browse/CAMEL-14689 > Project: Camel > Issue Type: Improvement > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Time Spent: 10m > Remaining Estimate: 0h > > I noticed that in the [contributing > guide|https://camel.apache.org/manual/latest/contributing.html] we mention > Subversion. We should go over [the > document|https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/pages/contributing.adoc] > and update it to reflect the current practices. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14695) Better menus in mobile version
[ https://issues.apache.org/jira/browse/CAMEL-14695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058153#comment-17058153 ] Aashna Jena commented on CAMEL-14695: - Hey [~zregvart], I see that some of the changes I suggested are already being made in those PRs. I think I'll wait for them to get merged, and then add these following things : - submenus as drop-downs from main-menu - odd-even colouring - colour the nav-bar differently (use the website's signature colours) Since the search-bar is already being discussed, and moving the search bar into the menu will make sure that the camel sign is fully visible, I think those two issues will be solved by the current PRs. I'll make a PR for styling the menu which will add above-mentioned features. Does that sound fine? > Better menus in mobile version > -- > > Key: CAMEL-14695 > URL: https://issues.apache.org/jira/browse/CAMEL-14695 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel_sign_cut.jpeg > > > The menus we have in the mobile version are a bit cluttered and difficult to > use. Let's see if we can do better. This issue was raised by [~Aemie] in > CAMEL-14581. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14700) Improve colour contrast
[ https://issues.apache.org/jira/browse/CAMEL-14700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058165#comment-17058165 ] Aashna Jena commented on CAMEL-14700: - Hey, here are the things I wanted to point out : - when the user selects some text, the background of the highlighted text is so close to white, that one can hardly notice it. - when the user opens a drop-down from the main menu and hovers over a sub-menu, it gets thinly underlined in orange, I think it would help if we could change the background colour on hover to improve colour contrast - put an outline around the search bar to make it stand out - (not sure about this, please suggest) should we change the colour of the nav-bar? The footer of each page is in grey, so it's easily distinguishable. But there exists only a thin line to separate the nav-bar and the webpage content (except the main landing page - where there's a gradient shading) > Improve colour contrast > --- > > Key: CAMEL-14700 > URL: https://issues.apache.org/jira/browse/CAMEL-14700 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: Camel_website.png, camel_webpage.JPG > > > We could get better usability for visually impaired folk by increasing the > colour contrast on the website. I've run some tools (Accessibility inspector > in Firefox) and there were some issues identified colour contrast of 2.69 > which doesn't meet the WACG standards as explained > [here|https://developer.mozilla.org/en-US/docs/Web/Accessibility/Understanding_WCAG/Perceivable/Color_contrast]. > [~aashnajena] also shared some ideas in [a comment > here|https://issues.apache.org/jira/browse/CAMEL-14581?focusedCommentId=17057194=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17057194]. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643 ] Aashna Jena commented on CAMEL-13902: - Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com] I am able to display the option "API Documentation" in the menu now (see image). Can you which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file? Or should it direct to a webpage like /manual/latest/getting-started.html etc? Also, please tell me what should be the content of api.md !camel_website.png! . Where s > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643 ] Aashna Jena edited comment on CAMEL-13902 at 3/6/20, 6:44 PM: -- Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/] I am able to display the option "API Documentation" in the menu now (see image). Can you tell me which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file (this is how building.md is displayed in public/docs/building/index.html)? Or should it direct to a webpage like /manual/latest/getting-started.html etc? I also need some idea about what should be the content of this file. The Documentation tab in the navbar has 10 links in the drop-down as of now. Each page has several more links, which is a little confusing for the user. Should we think of reorganising this after we add API documentation? was (Author: aashnajena): Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/] I am able to display the option "API Documentation" in the menu now (see image). Can you tell me which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file (this is how building.md is displayed in public/docs/building/index.html)? Or should it direct to a webpage like /manual/latest/getting-started.html etc? Also, please tell me what should be the content of api.md > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643 ] Aashna Jena edited comment on CAMEL-13902 at 3/6/20, 6:33 PM: -- Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/] I am able to display the option "API Documentation" in the menu now (see image). Can you tell me which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file (this is how building.md is displayed in public/docs/building/index.html)? Or should it direct to a webpage like /manual/latest/getting-started.html etc? Also, please tell me what should be the content of api.md was (Author: aashnajena): Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/] I am able to display the option "API Documentation" in the menu now (see image). Can you tell me which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file? Or should it direct to a webpage like /manual/latest/getting-started.html etc? Also, please tell me what should be the content of api.md !camel_website.png! . Where s > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053643#comment-17053643 ] Aashna Jena edited comment on CAMEL-13902 at 3/6/20, 5:55 PM: -- Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com/] I am able to display the option "API Documentation" in the menu now (see image). Can you tell me which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file? Or should it direct to a webpage like /manual/latest/getting-started.html etc? Also, please tell me what should be the content of api.md !camel_website.png! . Where s was (Author: aashnajena): Hi Zoran, I have added a block similar to [https://github.com/apache/camel-website/blob/22bb87f8127ae3a95c1b581433aded691d34333d/config.toml#L59-L64|http://example.com] I am able to display the option "API Documentation" in the menu now (see image). Can you which webpage this link should navigate to? And what should be the content of that webpage? Your comment above says that this menu option should point to api.md file. Should this menu option direct to the GitHub page with the api.md file? Or should it direct to a webpage like /manual/latest/getting-started.html etc? Also, please tell me what should be the content of api.md !camel_website.png! . Where s > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13881) Article containers right margin is larger than left margin
[ https://issues.apache.org/jira/browse/CAMEL-13881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052425#comment-17052425 ] Aashna Jena commented on CAMEL-13881: - I came across this issue on Apache's Outreachy landing page. Can anybody help me on how to get started? I was able to build and run the website locally. > Article containers right margin is larger than left margin > -- > > Key: CAMEL-13881 > URL: https://issues.apache.org/jira/browse/CAMEL-13881 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Antonin Stefanutti >Priority: Minor > Labels: help-wanted > Attachments: Screenshot 2019-08-20 at 10.51.48.png > > > The right margin of the article containers is larger than the left margin. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13888) New web site: open foreign links in new window (tab)
[ https://issues.apache.org/jira/browse/CAMEL-13888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17052424#comment-17052424 ] Aashna Jena commented on CAMEL-13888: - I came across this issue on Apache's Outreachy landing page. Can anybody help me on how to get started? I was able to build and run the website locally. > New web site: open foreign links in new window (tab) > > > Key: CAMEL-13888 > URL: https://issues.apache.org/jira/browse/CAMEL-13888 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Dmitry Volodin >Priority: Minor > Labels: help-wanted > > It can be discussing, but would be nice to open all foreign links as new > windows (tabs) for better usability while working with site, as some foreign > resources not working correctly with return back to the original site page. > Thank you. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053995#comment-17053995
]
Aashna Jena commented on CAMEL-14674:
-
Hey Zoran!
Please look at the screenshot below. Does this look fine to you? I have added
some padding, bottom margin and widened the table to align with the text (this
would make sure that all tables in blogs will look the same).
Please let me know how can improve this further. Thanks!
!css_table.png!
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule
> - Apache Camel.png, css_table.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053984#comment-17053984
]
Aashna Jena commented on CAMEL-14674:
-
Hey! I am taking a look into this issue. I am trying to
* get odd/even distinction in the table
* centre align the table and the text
* improve the padding
I'll post a screenshot as soon as I'm able to get some good results!
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule
> - Apache Camel.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aashna Jena updated CAMEL-14674:
Attachment: css_table.png
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule
> - Apache Camel.png, css_table.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054010#comment-17054010
]
Aashna Jena commented on CAMEL-14674:
-
Hey,
I thought it would be much better if we colour the headers differently and give
them a little extra padding so that the headings stand out. The rest of the
table can be coloured in an odd-even manner. Please review the screenshot and
give me feedback!
!css_table_update.png!
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule
> - Apache Camel.png, css_table.png, css_table_update.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aashna Jena updated CAMEL-14674:
Attachment: css_table_update.png
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule
> - Apache Camel.png, css_table.png, css_table_update.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054010#comment-17054010
]
Aashna Jena edited comment on CAMEL-14674 at 3/7/20, 11:56 AM:
---
Hey,
I thought it would be much better if we colour the headers differently and give
them a little extra padding so that the headings stand out. The rest of the
table can be coloured in an odd-even manner. I picked colours to match the
website theme. Please review the screenshot and give me feedback!
!css_table_update.png!
was (Author: aashnajena):
Hey,
I thought it would be much better if we colour the headers differently and give
them a little extra padding so that the headings stand out. The rest of the
table can be coloured in an odd-even manner. Please review the screenshot and
give me feedback!
!css_table_update.png!
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot_2020-03-06 Apache Camel 2020 Release Schedule
> - Apache Camel.png, css_table.png, css_table_update.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14676) Make the swoosh animation a bit more apparent
[ https://issues.apache.org/jira/browse/CAMEL-14676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054098#comment-17054098 ] Aashna Jena commented on CAMEL-14676: - Hey! It's true, I've hosted the website locally and I must have seen the landing page at least 10-12 times but I never realised that the wavy lines in the background were animated. Can you tell me where exactly can I find the code for this animation? I was thinking if we make a deeper contrast between the changing colours, the animation will become more apparent. Even if I try to look closely, right now I cannot figure what exactly the direction of of the animation is > Make the swoosh animation a bit more apparent > - > > Key: CAMEL-14676 > URL: https://issues.apache.org/jira/browse/CAMEL-14676 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel issue 2.png, camel issue.png, > image-2020-03-07-20-03-06-730.png > > > I often need to point out to folk that the swoosh wavy lines at the top of > the Camel website, currently behind the _Camel 3.1 is here! what's new_ text > is animated. > I would be interested in seeing if folk think that the animation is needed, > and if it is, how can it be improved. > For example, to make it more apparent it could be animated more vigorously > when the visitor first arrives on the front page, and less vigorously on next > visits. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054434#comment-17054434
]
Aashna Jena commented on CAMEL-14674:
-
Hi [~zregvart], I'm waiting for your review on the screenshot above to put in a
pull request! Please allow me to take up this issue, since I was the first one
to take it up and work on it. Thanks!
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot from 2020-03-08 14-12-18.png, Screenshot from
> 2020-03-08 14-12-18.png, Screenshot_2020-03-06 Apache Camel 2020 Release
> Schedule - Apache Camel.png, css_table.png, css_table_update.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054876#comment-17054876
]
Aashna Jena commented on CAMEL-14674:
-
Hi! I have made a pull request for this and have mentioned all the changes I
have made. Please review it as soon as possible. Thanks!
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot from 2020-03-08 14-12-18.png, Screenshot from
> 2020-03-08 14-12-18.png, Screenshot_2020-03-06 Apache Camel 2020 Release
> Schedule - Apache Camel.png, css_table.png, css_table_update.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054957#comment-17054957 ] Aashna Jena edited comment on CAMEL-13902 at 3/9/20, 1:32 PM: -- [~zregvart] Sounds great! For now, I'll add an "API documentation" under the "Documentation" menu and point it to [https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/index.html |http://example.com]/] After that I'll start working on issue-14581 and propose some ideas for reorganisation. Is that okay? was (Author: aashnajena): [~zregvart] Sounds great! For now, I'll add an "API documentation" under the "Documentation" menu and point it to [[https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/index.html |http://example.com]|https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/index.html] After that I'll start working on issue-14581 and propose some ideas for reorganisation. Is that okay? > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14674) Nicer table design for the blog post
[
https://issues.apache.org/jira/browse/CAMEL-14674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054862#comment-17054862
]
Aashna Jena commented on CAMEL-14674:
-
Hi Zoran, can you please tell if the screenshot I have shared is fine? I have
made changes to the .blog class and have used muted colors. I'm making a pull
request for the same.
> Nicer table design for the blog post
>
>
> Key: CAMEL-14674
> URL: https://issues.apache.org/jira/browse/CAMEL-14674
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Minor
> Labels: help-wanted
> Attachments: Screenshot from 2020-03-08 14-12-18.png, Screenshot from
> 2020-03-08 14-12-18.png, Screenshot_2020-03-06 Apache Camel 2020 Release
> Schedule - Apache Camel.png, css_table.png, css_table_update.png
>
>
> We recently published a blog post that featured a HTML table. See how
> [https://camel.apache.org/blog/LTS-Release-Schedule/] looks currently:
> !Screenshot_2020-03-06 Apache Camel 2020 Release Schedule - Apache Camel.png!
> The design of the table could be a bit nicer, for example it could be
> centered had nicer padding and odd/even row distinction.
> The changes would need to go to [antora-ui-camel/src/css/blog.css] and be
> scoped to the blog section via CSS {{.blog}} class to prevent possible
> collisions with the Antora generated documentation and CSS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-13902) Publish links to JavaDoc on the website
[ https://issues.apache.org/jira/browse/CAMEL-13902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17054957#comment-17054957 ] Aashna Jena commented on CAMEL-13902: - [~zregvart] Sounds great! For now, I'll add an "API documentation" under the "Documentation" menu and point it to [[https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/index.html |http://example.com]|https://www.javadoc.io/doc/org.apache.camel/camel-api/latest/index.html] After that I'll start working on issue-14581 and propose some ideas for reorganisation. Is that okay? > Publish links to JavaDoc on the website > --- > > Key: CAMEL-13902 > URL: https://issues.apache.org/jira/browse/CAMEL-13902 > Project: Camel > Issue Type: Task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > We can utilize javadoc.io to publish the JavaDoc for: > * camel-api > * camel-support > * camel-util -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14689) Update contributing guide
[ https://issues.apache.org/jira/browse/CAMEL-14689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056044#comment-17056044 ] Aashna Jena commented on CAMEL-14689: - Hey [~zregvart] , should I be editing the /manual/latest/contributing.html file to correct the information on [contributing guide|https://camel.apache.org/manual/latest/contributing.html] page? > Update contributing guide > - > > Key: CAMEL-14689 > URL: https://issues.apache.org/jira/browse/CAMEL-14689 > Project: Camel > Issue Type: Improvement > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > I noticed that in the [contributing > guide|https://camel.apache.org/manual/latest/contributing.html] we mention > Subversion. We should go over [the > document|https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/pages/contributing.adoc] > and update it to reflect the current practices. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059479#comment-17059479 ] Aashna Jena commented on CAMEL-13812: - Hey [~zregvart] can I start working on this? I think this is going to be a big task - given how much content the user manual has. I'll post a draft solution here asap! > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057105#comment-17057105 ] Aashna Jena edited comment on CAMEL-14581 at 3/11/20, 4:32 PM: --- I'm very new to the Antora and Hugo framework, so please let me know if I'm doing something the wrong way. I have many more ideas for improving the usability of the website! Please let me know if this reorganisation of sub-menus helps, because in the mobile version, when you open the menu, all the sub-menus are displayed automatically, and it looks quite cluttered (refer screenshot). Also, can we try to only show the menus (and display the submenus when user clicks on the main menu) for the mobile version? I think that will improve the user experience by quite a margin. !camel_mobile_menu.jpeg! was (Author: aashnajena): I'm very new to the Antora and Hugo framework, so please let me know if I'm doing something the wrong way. I have many more ideas for improving the usability of the website! Please let me know if this reorganisation of sub-menus helps, because in the mobile version, when you open the menu, all the sub-menus are displayed automatically, and it looks quite cluttered (refer screenshot). Also, can we try to only show the menus (and display the submenus when user clicks on the main menu) for the mobile version? I think that will improve the user experience by quite a margin. > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057105#comment-17057105 ] Aashna Jena edited comment on CAMEL-14581 at 3/11/20, 4:31 PM: --- I'm very new to the Antora and Hugo framework, so please let me know if I'm doing something the wrong way. I have many more ideas for improving the usability of the website! Please let me know if this reorganisation of sub-menus helps, because in the mobile version, when you open the menu, all the sub-menus are displayed automatically, and it looks quite cluttered (refer screenshot). Also, can we try to only show the menus (and display the submenus when user clicks on the main menu) for the mobile version? I think that will improve the user experience by quite a margin. was (Author: aashnajena): I'm very new to the Antora and Hugo framework, so please let me know if I'm doing something the wrong way. I have many more ideas for improving the usability of the website! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: camel_mobile_menu.jpeg > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057169#comment-17057169 ] Aashna Jena commented on CAMEL-13780: - Hey [~zregvart], can I work on this? Are we talking about the antora-ui-camel/docs/modules/ROOT/nav.adoc here? Can you please list out the issue in a little more detail - I am not able to understand what needs updating here. Thanks! > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057194#comment-17057194 ] Aashna Jena commented on CAMEL-14581: - [~zregvart] since you mentioned accessibility issues related to colour contrast, I have been looking at the website thoroughly for the last few days and have identified 2-3 key areas where this issue might be rooted at. Can I go ahead and make a separate issue/subtask for this? I already have 2-3 changes in mind. > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14695) Better menus in mobile version
[ https://issues.apache.org/jira/browse/CAMEL-14695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057264#comment-17057264 ] Aashna Jena commented on CAMEL-14695: - In fact, I just noticed a couple more things. The camel sign is getting cut on the vertical screen(see screenshot) due to the search bar. Can we have a menu similar to docs.couchbase.com? In addition to the suggestions mentioned above, can we do these : - the menu covers the full screen - the search bar can be part of this menu, it's cluttering the navbar - nav-bar (and menu icon) be differently coloured to stand out on the screen (similar to how it is on the desktop website - orange-white contrast) > Better menus in mobile version > -- > > Key: CAMEL-14695 > URL: https://issues.apache.org/jira/browse/CAMEL-14695 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > The menus we have in the mobile version are a bit cluttered and difficult to > use. Let's see if we can do better. This issue was raised by [~Aemie] in > CAMEL-14581. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14695) Better menus in mobile version
[ https://issues.apache.org/jira/browse/CAMEL-14695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057228#comment-17057228 ] Aashna Jena commented on CAMEL-14695: - Hey [~avgupt], Can you please post some screenshots of what changes you have made? I'm not able to understand what you did from your comment and your PR. I had a few things in mind to improve the mobile menu and I don't want to overlap with you. - Colour odd-even menu items differently for better contrast and readability - Have drop downs on the main menu items so that the sub-menus are not displayed all the time (currently due to too many sub-menus, the menu looks very cluttered) - Style the menu - increase font-size and widen it a little to cover more screen area - I feel that right-aligned menus are a bit more intuitive. This is debatable, what are your thoughts about this [~zregvart] ? > Better menus in mobile version > -- > > Key: CAMEL-14695 > URL: https://issues.apache.org/jira/browse/CAMEL-14695 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > The menus we have in the mobile version are a bit cluttered and difficult to > use. Let's see if we can do better. This issue was raised by [~Aemie] in > CAMEL-14581. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14695) Better menus in mobile version
[ https://issues.apache.org/jira/browse/CAMEL-14695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057264#comment-17057264 ] Aashna Jena edited comment on CAMEL-14695 at 3/11/20, 5:46 PM: --- In fact, I just noticed a couple more things. The camel sign is getting cut on the vertical screen(see screenshot) due to the search bar. Can we have a menu similar to docs.couchbase.com? In addition to the suggestions mentioned above, can we do these : - the menu covers the full screen - the search bar can be part of this menu, it's cluttering the navbar - nav-bar (and menu icon) be differently coloured to stand out on the screen (similar to how it is on the desktop website - orange-white contrast) !camel_sign_cut.jpeg! was (Author: aashnajena): In fact, I just noticed a couple more things. The camel sign is getting cut on the vertical screen(see screenshot) due to the search bar. Can we have a menu similar to docs.couchbase.com? In addition to the suggestions mentioned above, can we do these : - the menu covers the full screen - the search bar can be part of this menu, it's cluttering the navbar - nav-bar (and menu icon) be differently coloured to stand out on the screen (similar to how it is on the desktop website - orange-white contrast) > Better menus in mobile version > -- > > Key: CAMEL-14695 > URL: https://issues.apache.org/jira/browse/CAMEL-14695 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel_sign_cut.jpeg > > > The menus we have in the mobile version are a bit cluttered and difficult to > use. Let's see if we can do better. This issue was raised by [~Aemie] in > CAMEL-14581. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14695) Better menus in mobile version
[ https://issues.apache.org/jira/browse/CAMEL-14695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14695: Attachment: camel_sign_cut.jpeg > Better menus in mobile version > -- > > Key: CAMEL-14695 > URL: https://issues.apache.org/jira/browse/CAMEL-14695 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel_sign_cut.jpeg > > > The menus we have in the mobile version are a bit cluttered and difficult to > use. Let's see if we can do better. This issue was raised by [~Aemie] in > CAMEL-14581. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14695) Better menus in mobile version
[ https://issues.apache.org/jira/browse/CAMEL-14695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057264#comment-17057264 ] Aashna Jena edited comment on CAMEL-14695 at 3/11/20, 5:46 PM: --- In fact, I just noticed a couple more things. The camel sign is getting cut on the vertical screen(see screenshot) due to the search bar. Can we have a menu similar to docs.couchbase.com? In addition to the suggestions mentioned above, can we do these : - the menu covers the full screen - the search bar can be part of this menu, it's cluttering the navbar - nav-bar (and menu icon) be differently coloured to stand out on the screen (similar to how it is on the desktop website - orange-white contrast) was (Author: aashnajena): In fact, I just noticed a couple more things. The camel sign is getting cut on the vertical screen(see screenshot) due to the search bar. Can we have a menu similar to docs.couchbase.com? In addition to the suggestions mentioned above, can we do these : - the menu covers the full screen - the search bar can be part of this menu, it's cluttering the navbar - nav-bar (and menu icon) be differently coloured to stand out on the screen (similar to how it is on the desktop website - orange-white contrast) > Better menus in mobile version > -- > > Key: CAMEL-14695 > URL: https://issues.apache.org/jira/browse/CAMEL-14695 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: camel_sign_cut.jpeg > > > The menus we have in the mobile version are a bit cluttered and difficult to > use. Let's see if we can do better. This issue was raised by [~Aemie] in > CAMEL-14581. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14866) camel website - Show on component table the supportLevel
[ https://issues.apache.org/jira/browse/CAMEL-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17078259#comment-17078259 ] Aashna Jena commented on CAMEL-14866: - Hello! Can I take this up? The complexity of the issue is not mentioned, and I'm fairly new, but I'd like to give it a try! > camel website - Show on component table the supportLevel > > > Key: CAMEL-14866 > URL: https://issues.apache.org/jira/browse/CAMEL-14866 > Project: Camel > Issue Type: New Feature > Components: website >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.3.0 > > Attachments: Screenshot 2020-04-08 at 11.46.06.png > > > We now have in the camel-catalog a supportLevel that can be > - Experimental > - Preview > - Stable > We should find a way to show this in the component table. For example could > be something like they do at quarkus with a square box for Preview and > Experimental and a tool tip. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059722#comment-17059722 ] Aashna Jena commented on CAMEL-14581: - [~zregvart] I think having sub-menus (or just links in the header) under "About" and "Community" makes sense, since the sub-menu topics are fairly disjoint. But for Documentation and Projects, we should do away with the submenu and have separate webpages because : 1) They already have too many sub-menus 2) The sub-menu list will keep expanding with time - as new projects and documentations keep are added to Camel. I think this is a strong reason to maintain a page with links to sub-topics rather than having drop-down menus, especially taking the future scope for expansion into account. > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > Time Spent: 10m > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058964#comment-17058964 ] Aashna Jena commented on CAMEL-14581: - Thanks [~zregvart]. I have opened a PR for reorganizing the sub-menus of Projects Tab. I think the documentation tab would really benefit from some reorganization as well. I'm working on it! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: docs_menu.png > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: docs_menu.png > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059010#comment-17059010 ] Aashna Jena commented on CAMEL-14581: - Hey, I've tried to make the documentation menu easier to read. Is this in lines with what is expected? !docs_menu.png! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059042#comment-17059042 ] Aashna Jena commented on CAMEL-14581: - The sub menu list was too long for the documentation menu, that's why I am trying to avoid it. The page is not too long, it only has the three headings shown above. Also, this way things become a bit more hierarchical, hence easier to read. Maybe I can try to keep this hierarchy by adding sub-sub-menus which open to the right of each option on the sub-menu list. Let's see what [~zregvart] has to say about this! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > Time Spent: 10m > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17060303#comment-17060303 ] Aashna Jena commented on CAMEL-13780: - Hi, let me get this straight. I should look at all the links present in [this wiki page|https://cwiki.apache.org/confluence/display/CAMEL/Dozer+Type+Conversion] and [this manual|https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/pages/index.adoc#user-guide]. I should find out which of these links are not present in [the new manual|https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/nav.adoc] and add those links here? > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068436#comment-17068436 ] Aashna Jena commented on CAMEL-13780: - Okay thank you! I'll work on this. > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14772) website - Add section to display the 6 camel projects with logos
[ https://issues.apache.org/jira/browse/CAMEL-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17068435#comment-17068435 ] Aashna Jena commented on CAMEL-14772: - Hi! Can I help on this? > website - Add section to display the 6 camel projects with logos > > > Key: CAMEL-14772 > URL: https://issues.apache.org/jira/browse/CAMEL-14772 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: front-page.png > > > We should take this tweet with screenshot, and put on the front page to > better highlight the Camel projects we have > https://twitter.com/ApacheCamel/status/1242074457050624000 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069297#comment-17069297 ] Aashna Jena edited comment on CAMEL-13780 at 3/28/20, 8:00 AM: --- Do you want me to add pages like these into `*nav.adoc*`? These are linked from `*index.adoc*` but not present in *nav.adoc*. I'm assuming that I don't need to migrate the `components::*.adoc` files, those are already present under components. Am I right? --- xref:camel-jar-dependencies.adoc xref:camel-boot.adoc xref:components::cdi.adoc xref:configuring-route-startup-ordering-and-autostartup.adoc xref:graceful-shutdown.adoc xref:error-handling-in-camel.adoc xref:using-propertyplaceholder.adoc -- was (Author: aashnajena): Do you want me to add pages like these into `*nav.adoc*`? These are linked from `*index.adoc*` but not present in *nav.adoc*. I'm assuming that I don't need to migrate the `components::*.adoc` files, those are already present under components. Am I right? --- xref:camel-jar-dependencies.adoc xref:camel-boot.adoc xref:components::cdi.adoc xref:configuring-route-startup-ordering-and-autostartup.adoc xref:graceful-shutdown.adoc xref:error-handling-in-camel.adoc xref:using-propertyplaceholder.adoc -- > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069297#comment-17069297 ] Aashna Jena edited comment on CAMEL-13780 at 3/28/20, 8:03 AM: --- Do you want me to add pages like these into `*nav.adoc*`? These are linked from `*index.adoc*` but not present in *nav.adoc*. I'm assuming that I don't need to migrate the `components::*.adoc` files, those are already present under components. Am I right? --- xref:books.adoc xref:examples.adoc xref:camel-jar-dependencies.adoc xref:camel-boot.adoc xref:components::cdi.adoc xref:configuring-route-startup-ordering-and-autostartup.adoc xref:graceful-shutdown.adoc xref:error-handling-in-camel.adoc xref:using-propertyplaceholder.adoc -- was (Author: aashnajena): Do you want me to add pages like these into `*nav.adoc*`? These are linked from `*index.adoc*` but not present in *nav.adoc*. I'm assuming that I don't need to migrate the `components::*.adoc` files, those are already present under components. Am I right? --- xref:camel-jar-dependencies.adoc xref:camel-boot.adoc xref:components::cdi.adoc xref:configuring-route-startup-ordering-and-autostartup.adoc xref:graceful-shutdown.adoc xref:error-handling-in-camel.adoc xref:using-propertyplaceholder.adoc -- > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17069297#comment-17069297 ] Aashna Jena commented on CAMEL-13780: - Do you want me to add pages like these into `*nav.adoc*`? These are linked from `*index.adoc*` but not present in *nav.adoc*. I'm assuming that I don't need to migrate the `components::*.adoc` files, those are already present under components. Am I right? --- xref:camel-jar-dependencies.adoc xref:camel-boot.adoc xref:components::cdi.adoc xref:configuring-route-startup-ordering-and-autostartup.adoc xref:graceful-shutdown.adoc xref:error-handling-in-camel.adoc xref:using-propertyplaceholder.adoc -- > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14283) camel-website - Cleanup the EIP menu
[ https://issues.apache.org/jira/browse/CAMEL-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070231#comment-17070231 ] Aashna Jena commented on CAMEL-14283: - Hi! Has this issue been resolved? If not, can I take it up? > camel-website - Cleanup the EIP menu > > > Key: CAMEL-14283 > URL: https://issues.apache.org/jira/browse/CAMEL-14283 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > > The menu on the left hand side has both EIPs form the book and patterns in > the Camel DSL. > It would be good to list the EIPs from the book, and then have a separator > and then list all the patterns in the Camel routes > Today its a bit mixed up > https://camel.apache.org/manual/latest/enterprise-integration-patterns.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070262#comment-17070262 ] Aashna Jena commented on CAMEL-13780: - Hi, similar to the https://camel.apache.org/manual/latest/exception-clause.html page you mentioned above, I found lots of pages which aren't linked from the menu. Some of these are (there are about 60 like these) : https://camel.apache.org/manual/latest/backlog-tracer.html https://camel.apache.org/manual/latest/advanced-configuration-of-camelcontext-using-spring.html https://camel.apache.org/manual/latest/camel-embedded-maven-goal.html https://camel.apache.org/manual/latest/graceful-shutdown.html However, some pages are not directly linked from the menu, but have links to them from other pages. For example, https://camel.apache.org/manual/latest/bam-example.html cannot be accessed from the menu, but https://camel.apache.org/manual/latest/bam.html page gives a link to it. Is the goal that all pages should be on the menu? Or do I specifically need to look for pages which aren't linked from other pages as well? > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-13780: Comment: was deleted (was: Do you want me to add pages like these into `*nav.adoc*`? These are linked from `*index.adoc*` but not present in *nav.adoc*. I'm assuming that I don't need to migrate the `components::*.adoc` files, those are already present under components. Am I right? --- xref:books.adoc xref:examples.adoc xref:camel-jar-dependencies.adoc xref:camel-boot.adoc xref:components::cdi.adoc xref:configuring-route-startup-ordering-and-autostartup.adoc xref:graceful-shutdown.adoc xref:error-handling-in-camel.adoc xref:using-propertyplaceholder.adoc --) > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071793#comment-17071793 ] Aashna Jena commented on CAMEL-13780: - thanks :) I will make the necessary changes in `user-manual/modules/ROOT/nav.adoc`. > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071960#comment-17071960 ] Aashna Jena commented on CAMEL-13780: - Pull request is [here|https://github.com/apache/camel/pull/3699] > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071960#comment-17071960 ] Aashna Jena edited comment on CAMEL-13780 at 3/31/20, 5:38 PM: --- Pull request is [here|https://github.com/apache/camel/pull/3699]. I put this in the master branch, do I need to do the same for other branches? was (Author: aashnajena): Pull request is [here|https://github.com/apache/camel/pull/3699] > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070521#comment-17070521 ] Aashna Jena commented on CAMEL-13812: - Hi, I have made this pull request for splitting FAQ into a separate component. Here is the PR for [Camel Repository|https://github.com/apache/camel/pull/3691] and for [Camel-Website|https://github.com/apache/camel-website/pull/289] > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070853#comment-17070853 ] Aashna Jena commented on CAMEL-13812: - Hi, here is how I am proceeding with it : 1) move the FAQ folder from `user-manual/modules/ROOT/pages` to `user-manual/modules/` 2) remove all xref links to faq files from `user-manual/modules/ROOT/nav.adoc` and add just the link to the new FAQ module 3) make a new nav.adoc in `user-manual/modules/FAQ` and add the xref links here. Change the links according to the new relative location of files and add `modules/FAQ/nav.adoc` in `user-manual/antora.yml` Am I proceeding correctly? After this, I should check all files in FAQ module to see where links need to be changed according to their new relative position. I see there are two images in the `user-manual/modules/FAQ/pages/images` folder now, but I'm not able to find where these images are being used. Can you help me with this, and please tell me what else needs to be done? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070812#comment-17070812 ] Aashna Jena commented on CAMEL-13812: - I see. Yes this is exactly how I was testing the changes on the website, thank you for confirming :) Please allow me to make FAQ into a separate module and improve on my quality of commits. Thanks for elaborating! > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070853#comment-17070853 ] Aashna Jena edited comment on CAMEL-13812 at 3/30/20, 10:12 AM: Hi, here is how I am proceeding with it : 1) move the FAQ folder from `user-manual/modules/ROOT/pages` to `user-manual/modules/` 2) remove all xref links to faq files from `user-manual/modules/ROOT/nav.adoc` and add just the link to the new FAQ module 3) make a new nav.adoc in `user-manual/modules/FAQ` and add the xref links here. Change the links according to the new relative location of files and add `modules/FAQ/nav.adoc` in `user-manual/antora.yml` Am I proceeding correctly? After this, I should check all files in FAQ module to see where links need to be changed according to their new relative position. I see there are two images in the `user-manual/modules/FAQ/pages/images` folder now, but I'm not able to find where these images are being used. Can you help me with this, and please tell me what else needs to be done? was (Author: aashnajena): Hi, here is how I am proceeding with it : 1) move the FAQ folder from `user-manual/modules/ROOT/pages` to `user-manual/modules/` 2) remove all xref links to faq files from `user-manual/modules/ROOT/nav.adoc` and add just the link to the new FAQ module 3) make a new nav.adoc in `user-manual/modules/FAQ` and add the xref links here. Change the links according to the new relative location of files and add `modules/FAQ/nav.adoc` in `user-manual/antora.yml` Am I proceeding correctly? After this, I should check all files in FAQ module to see where links need to be changed according to their new relative position. I see there are two images in the `user-manual/modules/FAQ/pages/images` folder now, but I'm not able to find where these images are being used. Can you help me with this, and please tell me what else needs to be done? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070853#comment-17070853 ] Aashna Jena edited comment on CAMEL-13812 at 3/30/20, 10:31 AM: Hi, here is how I am proceeding with it : 1) move the FAQ folder from `user-manual/modules/ROOT/pages` to `user-manual/modules/` 2) remove all xref links to faq files from `user-manual/modules/ROOT/nav.adoc` 3) make a new nav.adoc in `user-manual/modules/FAQ` and add the xref links here. Change the links according to the new relative location of files and add `modules/FAQ/nav.adoc` in `user-manual/antora.yml` If I do this, the FAQ menu is appended after the "references" part in the user-manual menu. I don't think that's intended. Isn't it better to have a link to the FAQ/index.html page from the user-manual menu and have an independent menu for FAQ? OR if the full FAQ menu to be a part of the user-manual menu, please direct me on how to make it render at the right place. After this, I should check all files in FAQ module to see where links need to be changed according to their new relative position. I see there are two images in the `user-manual/modules/FAQ/pages/images` folder now, but I'm not able to find where these images are being used. Can you help me with this, and please tell me what else needs to be done? was (Author: aashnajena): Hi, here is how I am proceeding with it : 1) move the FAQ folder from `user-manual/modules/ROOT/pages` to `user-manual/modules/` 2) remove all xref links to faq files from `user-manual/modules/ROOT/nav.adoc` and add just the link to the new FAQ module 3) make a new nav.adoc in `user-manual/modules/FAQ` and add the xref links here. Change the links according to the new relative location of files and add `modules/FAQ/nav.adoc` in `user-manual/antora.yml` Am I proceeding correctly? After this, I should check all files in FAQ module to see where links need to be changed according to their new relative position. I see there are two images in the `user-manual/modules/FAQ/pages/images` folder now, but I'm not able to find where these images are being used. Can you help me with this, and please tell me what else needs to be done? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070903#comment-17070903 ] Aashna Jena commented on CAMEL-13812: - Is this how you expect the menu to look like? !faq-module.png! Right now, I have split FAQ into a separate module. To achieve this order in the menu, I split ROOT/nav.adoc into ROOT/nav.adoc and ROOT/references.adoc and the user-manual/antora.yml file has order : ROOT/nav.adoc FAQ/nav.adoc ROOT/references.adoc Since antora.yml is a component descriptor file as given in the [documentation|https://docs.antora.org/antora/2.0/component-descriptor/], I don't think we can have an independent menu for a module. Is this way okay for you? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, faq-module.png, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071079#comment-17071079 ] Aashna Jena edited comment on CAMEL-13812 at 3/30/20, 3:47 PM: --- Hey, thanks for the detailed response! I believe I have already made all the xref changes you mentioned above in my Pull Request. There are files outside docs/ also with xref links to FAQ, I have changed those as well. And yes, I checked for alternate formats as well. Basically, I checked for anything with a "faq/" in the URL. I have put a PR for master right now, once you get the time to review it and suggest changes, I'll be happy to do the same for other branches :) was (Author: aashnajena): Hey, thanks for the detailed response! I believe I have already made all the xref changes you mentioned in my Pull Request. There are files outside docs/ also with xref links to FAQ, I have changed those as well. And yes, I checked for alternate formats as well. Basically, I checked for anything with a "faq/" in the URL. I have put a PR for master right now, once you get the time to review it and suggest changes, I'll be happy to do the same for other branches :) > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, faq-module.png, > getting-started-with-apache-camel.docx > > Time Spent: 20m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071079#comment-17071079 ] Aashna Jena commented on CAMEL-13812: - Hey, thanks for the detailed response! I believe I have already made all the xref changes you mentioned in my Pull Request. There are files outside docs/ also with xref links to FAQ, I have changed those as well. And yes, I checked for alternate formats as well. Basically, I checked for anything with a "faq/" in the URL. I have put a PR for master right now, once you get the time to review it and suggest changes, I'll be happy to do the same for other branches :) > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, faq-module.png, > getting-started-with-apache-camel.docx > > Time Spent: 20m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-13812: Attachment: faq-module.png > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, faq-module.png, > getting-started-with-apache-camel.docx > > Time Spent: 10m > Remaining Estimate: 0h > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070262#comment-17070262 ] Aashna Jena edited comment on CAMEL-13780 at 3/29/20, 1:43 PM: --- Hi, similar to the https://camel.apache.org/manual/latest/exception-clause.html page you mentioned above, I found lots of pages which aren't linked from the menu. Some of these are (there are about 60 like these) : https://camel.apache.org/manual/latest/backlog-tracer.html https://camel.apache.org/manual/latest/advanced-configuration-of-camelcontext-using-spring.html https://camel.apache.org/manual/latest/camel-embedded-maven-goal.html https://camel.apache.org/manual/latest/graceful-shutdown.html However, some pages are not directly linked from the menu, but have links to them from other pages. For example, https://camel.apache.org/manual/latest/bam-example.html cannot be accessed from the menu, but https://camel.apache.org/manual/latest/bam.html page gives a link to it. Is the goal that all pages should be on the menu? Or do I specifically need to look for pages which aren't linked from other pages as well? In my opinion, user should be able to open every page from the menu, not have to go to another page to look for something. What's your take? was (Author: aashnajena): Hi, similar to the https://camel.apache.org/manual/latest/exception-clause.html page you mentioned above, I found lots of pages which aren't linked from the menu. Some of these are (there are about 60 like these) : https://camel.apache.org/manual/latest/backlog-tracer.html https://camel.apache.org/manual/latest/advanced-configuration-of-camelcontext-using-spring.html https://camel.apache.org/manual/latest/camel-embedded-maven-goal.html https://camel.apache.org/manual/latest/graceful-shutdown.html However, some pages are not directly linked from the menu, but have links to them from other pages. For example, https://camel.apache.org/manual/latest/bam-example.html cannot be accessed from the menu, but https://camel.apache.org/manual/latest/bam.html page gives a link to it. Is the goal that all pages should be on the menu? Or do I specifically need to look for pages which aren't linked from other pages as well? > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070349#comment-17070349 ] Aashna Jena commented on CAMEL-13812: - Hi, I want to split the FAQ part into a separate module. What I'm thinking in that User Manual should have a menu-item called FAQ, which should open a page with (1) FAQ introduction, (2) How to find your query and (3) list of all FAQs. I want this to be a separate module, with a nav-faq.adoc of its own. I also think it makes sense to have a quick look-up search box here, similar to components page. If I understand correctly, I'm going to have to make changes to the current [nav.adoc|https://github.com/apache/camel/blob/master/docs/user-manual/modules/ROOT/nav.adoc] and create a new nav-faq.adoc and migrate the xref links. These changes will get made in the camel repo, how do I test it on the website? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17059722#comment-17059722 ] Aashna Jena edited comment on CAMEL-14581 at 4/1/20, 7:14 PM: -- [~zregvart] I think having sub-menus (or just links in the header) under "About" and "Community" makes sense, since the sub-menu topics are fairly disjoint. But for Documentation and Projects, we should do away with the submenu and have separate webpages because : 1) They already have too many sub-menus 2) The sub-menu list will keep expanding with time - as new projects and documentations keep getting added to Camel. I think this is a strong reason to maintain a page with links to sub-topics rather than having drop-down menus, especially taking the future scope for expansion into account. was (Author: aashnajena): [~zregvart] I think having sub-menus (or just links in the header) under "About" and "Community" makes sense, since the sub-menu topics are fairly disjoint. But for Documentation and Projects, we should do away with the submenu and have separate webpages because : 1) They already have too many sub-menus 2) The sub-menu list will keep expanding with time - as new projects and documentations keep are added to Camel. I think this is a strong reason to maintain a page with links to sub-topics rather than having drop-down menus, especially taking the future scope for expansion into account. > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: search.png > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png, > search.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14581: Attachment: suggestions.png > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png, > search.png, suggestions.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073028#comment-17073028 ] Aashna Jena edited comment on CAMEL-14581 at 4/1/20, 5:55 PM: -- [~zregvart] I find the behaviour of the search bar a little odd. Generally, when user start typing a query, the drop-down gives options for word-completion. Example, typing "Qu" should give Quarkus, Questions etc. and when the user selects an option or hits enter, they are directed to a separate page with the search results, so that they can browse through all relevant links. https://www.apache.org/ does something similar. I feel this makes the user experience better. If you agree, I can make a sub-task for this and work on it. If not so, I still think the search result box can be presented better (We should highlight the word that matches the search and need some hover effect for each link) and I want to work on it. Please let me know your take on this. Thank you! was (Author: aashnajena): [~zregvart] I find the behaviour of the search bar a little odd. Generally, when user start typing a query, the drop-down gives options for word-completion. Example, typing "Qu" should give Quarkus, Questions etc. and when the user selects an option or hits enter, they are directed to a separate page with the search results, so that they can browse through all relevant links. I strongly feel this makes the user experience better. If you agree, I can make a sub-task for this and work on it. If not so, I still think the search result box can be presented better and I want to work on it. Please let me know your take on this. Thank you! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073028#comment-17073028 ] Aashna Jena edited comment on CAMEL-14581 at 4/1/20, 5:56 PM: -- [~zregvart] I find the behaviour of the search bar a little odd. Generally, when user start typing a query, the drop-down gives options for word-completion. Example, typing "Qu" should give Quarkus, Questions etc. and when the user selects an option or hits enter, they are directed to a separate page with the search results, so that they can browse through all relevant links. https://www.apache.org/ does something similar. I feel this makes the user experience better. If you agree, I can make a sub-task for this and work on it. If not so, I still think the search result box can be presented better (We should highlight the word that matches the search and need some hover effect for each link. I like how JIRA presents the search results!) and I want to work on it. Please let me know your take on this. Thank you! was (Author: aashnajena): [~zregvart] I find the behaviour of the search bar a little odd. Generally, when user start typing a query, the drop-down gives options for word-completion. Example, typing "Qu" should give Quarkus, Questions etc. and when the user selects an option or hits enter, they are directed to a separate page with the search results, so that they can browse through all relevant links. https://www.apache.org/ does something similar. I feel this makes the user experience better. If you agree, I can make a sub-task for this and work on it. If not so, I still think the search result box can be presented better (We should highlight the word that matches the search and need some hover effect for each link) and I want to work on it. Please let me know your take on this. Thank you! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13804) website - Add page which lists which components supports which runtimes
[ https://issues.apache.org/jira/browse/CAMEL-13804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073117#comment-17073117 ] Aashna Jena commented on CAMEL-13804: - Hi, is this issue still open? I'd like to take it up if no one's working on it yet! > website - Add page which lists which components supports which runtimes > --- > > Key: CAMEL-13804 > URL: https://issues.apache.org/jira/browse/CAMEL-13804 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted > Fix For: 3.3.0 > > > With CAMEL-13803 we should have a catalog that knows which component support > which runtimes. > Then we can make a page with a table of each component with a matrix with [x] > for which they support -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073184#comment-17073184 ] Aashna Jena commented on CAMEL-14581: - I mean to say that : currently, when we search for something in the search bar and hit "enter", the results (all matching links) are shown in a dropdown box like this : !search.png! Do you think that we should show word-completion suggestions while user is typing search query like this : !suggestions.png! and then have a separate page for displaying search results? > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png, > search.png, suggestions.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17073028#comment-17073028 ] Aashna Jena commented on CAMEL-14581: - [~zregvart] I find the behaviour of the search bar a little odd. Generally, when user start typing a query, the drop-down gives options for word-completion. Example, typing "Qu" should give Quarkus, Questions etc. and when the user selects an option or hits enter, they are directed to a separate page with the search results, so that they can browse through all relevant links. I strongly feel this makes the user experience better. If you agree, I can make a sub-task for this and work on it. If not so, I still think the search result box can be presented better and I want to work on it. Please let me know your take on this. Thank you! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Attachments: appache, camel-projects-2.png, > camel-projects.png, camel_mobile_menu.jpeg, docs_menu.png, docs_menu.png > > Time Spent: 1h > Remaining Estimate: 0h > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14567) camel-website - Sidebar menu tidy up names
[ https://issues.apache.org/jira/browse/CAMEL-14567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17061987#comment-17061987 ] Aashna Jena commented on CAMEL-14567: - Hi! Does this issue still persist? I think some part of it has already been done. If I'm mistaken and there are more tasks to be done, can I please take this up? :) > camel-website - Sidebar menu tidy up names > -- > > Key: CAMEL-14567 > URL: https://issues.apache.org/jira/browse/CAMEL-14567 > Project: Camel > Issue Type: Test >Reporter: Claus Ibsen >Priority: Major > Labels: help-wanted, website > > Apache Camel extensions for Quarkus > Apache Camel K > Apache Camel Kafka Connector > Camel Spring Boot Starters > Component reference > User manual > Make this into > Camel Components > Camel Kafka Connectors > Camel Quarkus Extensions > Camel Spring Boot Starters > User manual -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062356#comment-17062356 ] Aashna Jena edited comment on CAMEL-13780 at 3/19/20, 8:03 AM: --- Yes [~Aemie], I have already started working on this issue. Can you please take up another one, so that we don't have any conflicting PRs? Thanks! I've been asked to wait for some structural changes to be merged before I start working on this issue :) was (Author: aashnajena): Yes [~Aemie], I have already started working on this issue. Can you please take up another one, so that we don't have any conflicting PRs? Thanks! > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13780) Cleanup nav.adoc in Antora modules
[ https://issues.apache.org/jira/browse/CAMEL-13780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17062356#comment-17062356 ] Aashna Jena commented on CAMEL-13780: - Yes [~Aemie], I have already started working on this issue. Can you please take up another one, so that we don't have any conflicting PRs? Thanks! > Cleanup nav.adoc in Antora modules > -- > > Key: CAMEL-13780 > URL: https://issues.apache.org/jira/browse/CAMEL-13780 > Project: Camel > Issue Type: Sub-task > Components: documentation >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.2.0 > > > The nav.adoc files in user-manual and component reference could use updating. > There are documents missing from them and content could be grouped in topics. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17063836#comment-17063836 ] Aashna Jena commented on CAMEL-13812: - I like the idea. Shall we start working on this? > Split up user manual > > > Key: CAMEL-13812 > URL: https://issues.apache.org/jira/browse/CAMEL-13812 > Project: Camel > Issue Type: Sub-task > Components: documentation, website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > Fix For: 3.x > > Attachments: FAQ landing-page.docx, > getting-started-with-apache-camel.docx > > > I think we would benefit from splitting up the user manual into even smaller > Antora modules: > * FAQ > * Getting started > * User manual > Perhaps (not sure), Architecture. I think grouping of pages would help as we > could have a landing (index) page for each module. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055284#comment-17055284 ] Aashna Jena commented on CAMEL-14581: - Hey, will it be beneficial if we can remove the sub-menus, especially from Documentation and Projects menu, and create a webpage where we have links to all the sub-menu items, with 1-2 lines of description of what to expect from each page? Some of the pages on the website (Projects>Camel K, Camel Quarkus etc) have very less content on them anyway. If we can make a Projects page with all the sub-menus as subheadings, we can put the short content as descriptions, and the links can help the user direct to different pages. Can you also give me some idea about what we mean by accessibility here? Should we re-read the content to make sure it's user-friendly? Also, in the navbar, the search box and social media icons aren't aligned with the menu items. Is that intentional? I think we should either keep them on the extreme top right, or keep them aligned with the menu items. Also, a boundary around the search box might look better :) please let me know if any of these suggestions make sense to you and I'll proceed with coding them out! > Website usability improvements > -- > > Key: CAMEL-14581 > URL: https://issues.apache.org/jira/browse/CAMEL-14581 > Project: Camel > Issue Type: Sub-task > Components: website >Reporter: Zoran Regvart >Priority: Major > Labels: help-wanted > > The current Apache Camel website can use some help with the usability. I've > identified the following areas that could improve: > * simpler top level navigation: currently we have Blog, Projects, > Documentation, Community, Download, About; some of these also have sub-menu > items. I think we could benefit from a simpler organization and perhaps get > rid of sub-menus and serve pages with content regarding each section (e.g. > documentation page could have pointers to different kinds of documentation we > currently have on the sub-menu) > * accessibility (readability/contrast/...): we should run audits and make > sure that the website is accessible > * rework menus on low resolution: make sure that the menus are large enough > and readable on lower resolution -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14994) camel website - Projects page can we add logos
[ https://issues.apache.org/jira/browse/CAMEL-14994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14994: Attachment: screenshot-1.png > camel website - Projects page can we add logos > -- > > Key: CAMEL-14994 > URL: https://issues.apache.org/jira/browse/CAMEL-14994 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Attachments: projects-desgin.png > > > The page > https://camel.apache.org/projects/ > List the projects (we should btw add Camel itself IMHO). > So basically can we add the logos that we have on the front page, and list > them with same caption too. This would make it more appealing as today its a > bit dull. And if you go to the front page you have to scroll down to see > those projects and logos, so some users may miss seeing that. > Also order them so its > - camel > - camel k > - camel kafka > - camel spring boot > - camel quarkus > - camel karaf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14994) camel website - Projects page can we add logos
[ https://issues.apache.org/jira/browse/CAMEL-14994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14994: Attachment: (was: screenshot-1.png) > camel website - Projects page can we add logos > -- > > Key: CAMEL-14994 > URL: https://issues.apache.org/jira/browse/CAMEL-14994 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Attachments: projects-desgin.png > > > The page > https://camel.apache.org/projects/ > List the projects (we should btw add Camel itself IMHO). > So basically can we add the logos that we have on the front page, and list > them with same caption too. This would make it more appealing as today its a > bit dull. And if you go to the front page you have to scroll down to see > those projects and logos, so some users may miss seeing that. > Also order them so its > - camel > - camel k > - camel kafka > - camel spring boot > - camel quarkus > - camel karaf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14994) camel website - Projects page can we add logos
[ https://issues.apache.org/jira/browse/CAMEL-14994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-14994: Attachment: projects-desgin.png > camel website - Projects page can we add logos > -- > > Key: CAMEL-14994 > URL: https://issues.apache.org/jira/browse/CAMEL-14994 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Attachments: projects-desgin.png > > > The page > https://camel.apache.org/projects/ > List the projects (we should btw add Camel itself IMHO). > So basically can we add the logos that we have on the front page, and list > them with same caption too. This would make it more appealing as today its a > bit dull. And if you go to the front page you have to scroll down to see > those projects and logos, so some users may miss seeing that. > Also order them so its > - camel > - camel k > - camel kafka > - camel spring boot > - camel quarkus > - camel karaf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14994) camel website - Projects page can we add logos
[ https://issues.apache.org/jira/browse/CAMEL-14994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113987#comment-17113987 ] Aashna Jena commented on CAMEL-14994: - This is what I felt looks best. First I tried to have images on the left and text on the right, but since our logos are more wide than tall, it looks odd. Let me know what improvements we can make on this. One thought : do we need to have text explaining the icons for mailing list, documentation and github code? !projects-desgin.png! > camel website - Projects page can we add logos > -- > > Key: CAMEL-14994 > URL: https://issues.apache.org/jira/browse/CAMEL-14994 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Attachments: projects-desgin.png > > > The page > https://camel.apache.org/projects/ > List the projects (we should btw add Camel itself IMHO). > So basically can we add the logos that we have on the front page, and list > them with same caption too. This would make it more appealing as today its a > bit dull. And if you go to the front page you have to scroll down to see > those projects and logos, so some users may miss seeing that. > Also order them so its > - camel > - camel k > - camel kafka > - camel spring boot > - camel quarkus > - camel karaf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-14994) camel website - Projects page can we add logos
[ https://issues.apache.org/jira/browse/CAMEL-14994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113987#comment-17113987 ] Aashna Jena edited comment on CAMEL-14994 at 5/22/20, 1:26 PM: --- This is what I felt looks best. First I tried to have images on the left and text on the right, but since our logos are more wide than tall, it looks odd. Let me know what improvements we can make on this. One thought : do we need to have text explaining the icons for mailing list, documentation and github code? For smaller screens, we can shift to one column instead of two. !projects-desgin.png! was (Author: aashnajena): This is what I felt looks best. First I tried to have images on the left and text on the right, but since our logos are more wide than tall, it looks odd. Let me know what improvements we can make on this. One thought : do we need to have text explaining the icons for mailing list, documentation and github code? !projects-desgin.png! > camel website - Projects page can we add logos > -- > > Key: CAMEL-14994 > URL: https://issues.apache.org/jira/browse/CAMEL-14994 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Claus Ibsen >Priority: Major > Attachments: projects-desgin.png > > > The page > https://camel.apache.org/projects/ > List the projects (we should btw add Camel itself IMHO). > So basically can we add the logos that we have on the front page, and list > them with same caption too. This would make it more appealing as today its a > bit dull. And if you go to the front page you have to scroll down to see > those projects and logos, so some users may miss seeing that. > Also order them so its > - camel > - camel k > - camel kafka > - camel spring boot > - camel quarkus > - camel karaf -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14952) Better search on the website
[
https://issues.apache.org/jira/browse/CAMEL-14952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17098308#comment-17098308
]
Aashna Jena commented on CAMEL-14952:
-
As you mentioned, we need to start by thinking about what we want to present in
the search UI, because the index will be built according to that. Are we
thinking of including Algolia's default UI? Or do we prefer to keep the
customized UI that we have created?
> Better search on the website
>
>
> Key: CAMEL-14952
> URL: https://issues.apache.org/jira/browse/CAMEL-14952
> Project: Camel
> Issue Type: Improvement
> Components: website
>Reporter: Zoran Regvart
>Priority: Major
>
> We use [Algolia|http://algolia.com/] for the search functionality on the
> website using their [free plan|https://www.algolia.com/for-open-source/] for
> Open Source projects. The index is built by Algolia's crawler using the
> [DocSearch|https://docsearch.algolia.com/].
> When this was done we built our own UI on top of Algolia JavaScript API, as
> one if requirements is that clients use Algolia's JavaScript clients. We did
> not use Algolia UI as at that point it was rather large JavaScript dependency
> to add and it would slow down the loading of the website.
> We also have some [initial
> work|https://github.com/apache/camel-website/pull/74] on creating our own
> Algolia index at build time.
> The current search doesn't seem to index the whole website, some results
> don't appear in the search, looks like most of the content from Antora is not
> indexed: trying to search for {{removeHeader}}, the [FAQ
> entry|https://camel.apache.org/manual/latest/faq/how-to-avoid-sending-some-or-all-message-headers.html]
> is not found. There's also a list of failed searches on the Algolia
> dashboard we can use to benchmark the search.
> What we need is to build the search index over the whole content. Approach
> taken in [#74|https://github.com/apache/camel-website/pull/74] is good start
> for Hugo generated content. We need to expand that to Antora built content as
> well.
> This search index would be built at the website build time and would include
> both Hugo and Algolia content in the same file or possibly in several files
> if we use multi-index search. More on how indexes are built can be seen in
> the [Algolia
> documentation|https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/].
> We need to figure out what data to send and how to integrate this with
> Antora, for Hugo we have a good idea from
> [#74|https://github.com/apache/camel-website/pull/74], importantly the
> structure needs to be the same. One good source of inspiration on building
> the index for Antora content is in the [Lunr.js
> integration|https://github.com/Mogztter/antora-lunr].
> We need to build the index with the search UI in mind, i.e. the index needs
> to contain the data we wish to present in the UI as well as enough content
> for Algolia to be able to use the content to perform search. So starting with
> a mockup of what we wish to present/utilize in the search UI and deriving the
> data structure for the index from that would be a good start.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CAMEL-15392) Provide a modified neat card layout for community & docs
[ https://issues.apache.org/jira/browse/CAMEL-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179348#comment-17179348 ] Aashna Jena commented on CAMEL-15392: - You can't really argue about the vertical spcae. I've implemented this and it actually used less vertical space than the card layout. In the cards, we have to specify explicit height of the descriptions, hence we have a lot of extra between descriptions and links, which is not the case here. As for personal choice, I think we should wait for others to comment as well. Before the card layout, it was just a bunch of text, so I don't think it's fair to say that we're moving back. The reason for including 1 project in a row is to have 3 buttons in a row, not 6, because they split at >1270px as well I don't mind including icons, they feel a little redundant in this case because they are just increasing the width of the button + we haven't used icons in buttons anywhere else on the website. We can definitely include them if everyone agrees. > Provide a modified neat card layout for community & docs > > > Key: CAMEL-15392 > URL: https://issues.apache.org/jira/browse/CAMEL-15392 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Attachments: Screenshot from 2020-08-18 02-49-07.png, Screenshot from > 2020-08-18 02-52-37.png, button-community-badges.png, > button-link-docs-sub-project.png, camel-core-button-card.png, > community-design-card.png, contributing-design-card.png > > > The card layout design for the documentation and community page seemed plain > compared to the other pages of the website. Thus, included rounded background > over the links for the pages and rounded border over the section to provide > the card-like layout. This will fit with the new design for the front page. I > have created a PR regarding it with a minimal design approach however I came > up with a few more designs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15392) Provide a modified neat card layout for community & docs
[ https://issues.apache.org/jira/browse/CAMEL-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-15392: Attachment: Screenshot from 2020-08-18 02-52-37.png > Provide a modified neat card layout for community & docs > > > Key: CAMEL-15392 > URL: https://issues.apache.org/jira/browse/CAMEL-15392 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Attachments: Screenshot from 2020-08-18 02-49-07.png, Screenshot from > 2020-08-18 02-52-37.png, button-community-badges.png, > button-link-docs-sub-project.png, camel-core-button-card.png, > community-design-card.png, contributing-design-card.png > > > The card layout design for the documentation and community page seemed plain > compared to the other pages of the website. Thus, included rounded background > over the links for the pages and rounded border over the section to provide > the card-like layout. This will fit with the new design for the front page. I > have created a PR regarding it with a minimal design approach however I came > up with a few more designs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15392) Provide a modified neat card layout for community & docs
[ https://issues.apache.org/jira/browse/CAMEL-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179233#comment-17179233 ] Aashna Jena commented on CAMEL-15392: - I still think that 6 orange buttons in a row look too much, especially because they are splitting even at my normal view. !Screenshot from 2020-08-18 02-49-07.png! Since the idea is to move closer to design of the front page, I think we can move away from the box design and have something like this : !Screenshot from 2020-08-18 02-52-37.png! I like this better because we can easily fit 3 links, it's similar to the front page design and there isn't too much orange. Also since we have odd number of projects, we have a big leftover space on the right of Camel Karaf in the current layout which looks odd to me. [~zregvart] [~delawen] [~Aemie] [~davsclaus] what do you think? > Provide a modified neat card layout for community & docs > > > Key: CAMEL-15392 > URL: https://issues.apache.org/jira/browse/CAMEL-15392 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Attachments: Screenshot from 2020-08-18 02-49-07.png, Screenshot from > 2020-08-18 02-52-37.png, button-community-badges.png, > button-link-docs-sub-project.png, camel-core-button-card.png, > community-design-card.png, contributing-design-card.png > > > The card layout design for the documentation and community page seemed plain > compared to the other pages of the website. Thus, included rounded background > over the links for the pages and rounded border over the section to provide > the card-like layout. This will fit with the new design for the front page. I > have created a PR regarding it with a minimal design approach however I came > up with a few more designs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15392) Provide a modified neat card layout for community & docs
[ https://issues.apache.org/jira/browse/CAMEL-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-15392: Attachment: Screenshot from 2020-08-18 02-49-07.png > Provide a modified neat card layout for community & docs > > > Key: CAMEL-15392 > URL: https://issues.apache.org/jira/browse/CAMEL-15392 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Attachments: Screenshot from 2020-08-18 02-49-07.png, > button-community-badges.png, button-link-docs-sub-project.png, > camel-core-button-card.png, community-design-card.png, > contributing-design-card.png > > > The card layout design for the documentation and community page seemed plain > compared to the other pages of the website. Thus, included rounded background > over the links for the pages and rounded border over the section to provide > the card-like layout. This will fit with the new design for the front page. I > have created a PR regarding it with a minimal design approach however I came > up with a few more designs. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15296) Create sitemap for Camel website
[ https://issues.apache.org/jira/browse/CAMEL-15296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17178074#comment-17178074 ] Aashna Jena commented on CAMEL-15296: - [~zregvart] does this look fine? Should we be including more links? !Screenshot from 2020-08-15 03-10-53.png! > Create sitemap for Camel website > > > Key: CAMEL-15296 > URL: https://issues.apache.org/jira/browse/CAMEL-15296 > Project: Camel > Issue Type: New Feature > Components: website >Reporter: Aashna Jena >Priority: Minor > Labels: outreachy2020 > Attachments: Screenshot from 2020-08-15 02-58-11.png, Screenshot from > 2020-08-15 03-09-58.png, Screenshot from 2020-08-15 03-10-53.png, > components-sitemap.png, hugo-sitemap-with-blog-categories.png, > user-manual-sitemap.png > > > Create a page with links to all documentation pages on the website. Automate > this process and organise the links category wise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15296) Create sitemap for Camel website
[ https://issues.apache.org/jira/browse/CAMEL-15296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-15296: Attachment: Screenshot from 2020-08-15 02-58-11.png > Create sitemap for Camel website > > > Key: CAMEL-15296 > URL: https://issues.apache.org/jira/browse/CAMEL-15296 > Project: Camel > Issue Type: New Feature > Components: website >Reporter: Aashna Jena >Priority: Minor > Labels: outreachy2020 > Attachments: Screenshot from 2020-08-15 02-58-11.png, > components-sitemap.png, hugo-sitemap-with-blog-categories.png, > user-manual-sitemap.png > > > Create a page with links to all documentation pages on the website. Automate > this process and organise the links category wise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15296) Create sitemap for Camel website
[ https://issues.apache.org/jira/browse/CAMEL-15296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-15296: Attachment: Screenshot from 2020-08-15 03-09-58.png > Create sitemap for Camel website > > > Key: CAMEL-15296 > URL: https://issues.apache.org/jira/browse/CAMEL-15296 > Project: Camel > Issue Type: New Feature > Components: website >Reporter: Aashna Jena >Priority: Minor > Labels: outreachy2020 > Attachments: Screenshot from 2020-08-15 02-58-11.png, Screenshot from > 2020-08-15 03-09-58.png, components-sitemap.png, > hugo-sitemap-with-blog-categories.png, user-manual-sitemap.png > > > Create a page with links to all documentation pages on the website. Automate > this process and organise the links category wise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-15296) Create sitemap for Camel website
[ https://issues.apache.org/jira/browse/CAMEL-15296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-15296: Attachment: Screenshot from 2020-08-15 03-10-53.png > Create sitemap for Camel website > > > Key: CAMEL-15296 > URL: https://issues.apache.org/jira/browse/CAMEL-15296 > Project: Camel > Issue Type: New Feature > Components: website >Reporter: Aashna Jena >Priority: Minor > Labels: outreachy2020 > Attachments: Screenshot from 2020-08-15 02-58-11.png, Screenshot from > 2020-08-15 03-09-58.png, Screenshot from 2020-08-15 03-10-53.png, > components-sitemap.png, hugo-sitemap-with-blog-categories.png, > user-manual-sitemap.png > > > Create a page with links to all documentation pages on the website. Automate > this process and organise the links category wise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14958) Suggestion on search bar within smaller screen width.
[ https://issues.apache.org/jira/browse/CAMEL-14958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17116507#comment-17116507 ] Aashna Jena commented on CAMEL-14958: - I agree that we should have the search option on smaller screens. [~Aemie] this would also mean that we have to adjust the search result styling for smaller screens. Another thought : If we open up a search bar below the header instead of overwriting it, would that look too cluttered? > Suggestion on search bar within smaller screen width. > - > > Key: CAMEL-14958 > URL: https://issues.apache.org/jira/browse/CAMEL-14958 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aemie >Priority: Major > Labels: outreachy2020, suggestions > Attachments: image-2020-05-25-18-16-52-529.png, > searchbar-outreachy.jpeg > > > Within the small width screen, the setting is to only display the social icon > button as of now. However, I thought it would be a good idea to include the > search icon alongside the social button icons. On click of the social button > icons, we could include animation, for instance, a fade-in effect of the > search bar occupying the entire navbar. The user can do the search as > required. On the left side of the search bar, there will be back arrow, which > on click would give us the original navbar look with a fade-out effect. > > The representation would look similar to the diagram as shown. > !image-2020-05-25-18-16-52-529.png|width=326,height=166! > Before I start working on this, I would like an opinion about this idea. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-15140) Improve Main Menu for Mobile Screens
Aashna Jena created CAMEL-15140: --- Summary: Improve Main Menu for Mobile Screens Key: CAMEL-15140 URL: https://issues.apache.org/jira/browse/CAMEL-15140 Project: Camel Issue Type: Improvement Components: website Reporter: Aashna Jena Our current menu for mobile screens is a list of text items with a small drop-down arrow, which don't really make for a good touch target. I like how the facebook app displays menu items - they take up the full screen and each menu item has an icon and text enclosed in a box-like structure. I also like Amazon app's menu, where sub-menus replace the menu space instead of opening up as drop-downs. I can post some mock-ups if we are open to changing the design of the menu on mobile screens -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-15140) Improve Main Menu for Mobile Screens
[ https://issues.apache.org/jira/browse/CAMEL-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17120311#comment-17120311 ] Aashna Jena commented on CAMEL-15140: - Color separated or boundary separated menu items can also make a good touch target. We don't necessarily need to have the full screen covered for the menu, we can cover less also. We can have big icons, clear text and convert this to our orange-white color scheme !screenshot-1.png! > Improve Main Menu for Mobile Screens > > > Key: CAMEL-15140 > URL: https://issues.apache.org/jira/browse/CAMEL-15140 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aashna Jena >Priority: Major > Labels: outreachy2020 > Attachments: screenshot-1.png > > > Our current menu for mobile screens is a list of text items with a small > drop-down arrow, which don't really make for a good touch target. I like how > the facebook app displays menu items - they take up the full screen and each > menu item has an icon and text enclosed in a box-like structure. I also like > Amazon app's menu, where sub-menus replace the menu space instead of opening > up as drop-downs. I can post some mock-ups if we are open to changing the > design of the menu on mobile screens -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Issue Comment Deleted] (CAMEL-15140) Improve Main Menu for Mobile Screens
[ https://issues.apache.org/jira/browse/CAMEL-15140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aashna Jena updated CAMEL-15140: Comment: was deleted (was: Color separated or boundary separated menu items can also make a good touch target. We don't necessarily need to have the full screen covered for the menu, we can cover less also. We can have big icons, clear text and convert this to our orange-white color scheme !screenshot-1.png!) > Improve Main Menu for Mobile Screens > > > Key: CAMEL-15140 > URL: https://issues.apache.org/jira/browse/CAMEL-15140 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Aashna Jena >Priority: Major > Labels: outreachy2020 > Attachments: screenshot-1.png > > > Our current menu for mobile screens is a list of text items with a small > drop-down arrow, which don't really make for a good touch target. I like how > the facebook app displays menu items - they take up the full screen and each > menu item has an icon and text enclosed in a box-like structure. I also like > Amazon app's menu, where sub-menus replace the menu space instead of opening > up as drop-downs. I can post some mock-ups if we are open to changing the > design of the menu on mobile screens -- This message was sent by Atlassian Jira (v8.3.4#803005)
