[jira] [Work logged] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?focusedWorklogId=412818=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412818 ] ASF GitHub Bot logged work on CAMEL-14581: -- Author: ASF GitHub Bot Created on: 31/Mar/20 03:50 Start Date: 31/Mar/20 03:50 Worklog Time Spent: 10m Work Description: AemieJ commented on pull request #294: CAMEL-14581: improve accessibility ratio through color contrast under blog section URL: https://github.com/apache/camel-website/pull/294 * After running audit, it was observed that the accessibility factor under the blog section was decreasing due to various factors, one of them including the **color contrast**. * For the case of **color contrast**, I have made all required changes to get the right **COLOR CONTRAST RATIO** while keeping in mind the aesthetic and presentability of the pages under the blog section. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412818) Time Spent: 50m (was: 40m) > 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: 50m > 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] [Work logged] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?focusedWorklogId=412817=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412817 ] ASF GitHub Bot logged work on CAMEL-14581: -- Author: ASF GitHub Bot Created on: 31/Mar/20 03:49 Start Date: 31/Mar/20 03:49 Worklog Time Spent: 10m Work Description: AemieJ commented on pull request #228: CAMEL-14581: Improve the accessibility factor under the blog section URL: https://github.com/apache/camel-website/pull/228 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412817) Time Spent: 40m (was: 0.5h) > 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: 40m > 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] [Resolved] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-14581. --- Resolution: Fixed Thanks to [~aashnajena] for pull requests for 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: 0.5h > 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] [Work logged] (CAMEL-14581) Website usability improvements
[ https://issues.apache.org/jira/browse/CAMEL-14581?focusedWorklogId=412563=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412563 ] ASF GitHub Bot logged work on CAMEL-14581: -- Author: ASF GitHub Bot Created on: 30/Mar/20 20:51 Start Date: 30/Mar/20 20:51 Worklog Time Spent: 10m Work Description: zregvart commented on pull request #216: [CAMEL-14581] Remove sub-menus for documentation and Reorganize Documentation menu URL: https://github.com/apache/camel-website/pull/216 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412563) Time Spent: 0.5h (was: 20m) > 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: 0.5h > 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] [Work logged] (CAMEL-14700) Improve colour contrast
[ https://issues.apache.org/jira/browse/CAMEL-14700?focusedWorklogId=412561=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412561 ] ASF GitHub Bot logged work on CAMEL-14700: -- Author: ASF GitHub Bot Created on: 30/Mar/20 20:49 Start Date: 30/Mar/20 20:49 Worklog Time Spent: 10m Work Description: zregvart commented on pull request #207: [CAMEL-14700] Improve colour contrast URL: https://github.com/apache/camel-website/pull/207 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412561) Time Spent: 20m (was: 10m) > 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, > image-2020-03-13-22-51-53-783.png > > Time Spent: 20m > Remaining Estimate: 0h > > 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-14812) camel-karaf - We should not maintain versions in its root pom.xml
[ https://issues.apache.org/jira/browse/CAMEL-14812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071242#comment-17071242 ] Andrea Cosentino commented on CAMEL-14812: -- Same problem for camel-spring-boot, less, but always the same. > camel-karaf - We should not maintain versions in its root pom.xml > - > > Key: CAMEL-14812 > URL: https://issues.apache.org/jira/browse/CAMEL-14812 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.3.0 > > > We should not duplicate versions in parent/pom.xml and then also in > camel-karaf root pom. > camel-karaf should use the versions from camel/parent instead and then if > needed overlay with its own bundle versions. > Today we have duplicates and this means we would get out of sync -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14812) camel-karaf - We should not maintain versions in its root pom.xml
Claus Ibsen created CAMEL-14812: --- Summary: camel-karaf - We should not maintain versions in its root pom.xml Key: CAMEL-14812 URL: https://issues.apache.org/jira/browse/CAMEL-14812 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Fix For: 3.3.0 We should not duplicate versions in parent/pom.xml and then also in camel-karaf root pom. camel-karaf should use the versions from camel/parent instead and then if needed overlay with its own bundle versions. Today we have duplicates and this means we would get out of sync -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?focusedWorklogId=412434=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412434 ] ASF GitHub Bot logged work on CAMEL-13812: -- Author: ASF GitHub Bot Created on: 30/Mar/20 16:58 Start Date: 30/Mar/20 16:58 Worklog Time Spent: 10m Work Description: aashnajena commented on pull request #289: [CAMEL-13812] Split FAQ into separate page URL: https://github.com/apache/camel-website/pull/289 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412434) Time Spent: 0.5h (was: 20m) > 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: 0.5h > 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] [Commented] (CAMEL-13812) Split up user manual
[
https://issues.apache.org/jira/browse/CAMEL-13812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17071062#comment-17071062
]
David Jencks commented on CAMEL-13812:
--
This basically looks good to me.
I think your arrangement of nav files is fine.
I would name the module 'faq' rather than 'FAQ'. 'ROOT' is uppercased because
it is special in that the module name is removed from the final path: all other
module names are normally lowercase as they do appear in the url. The effect
of this is that the path for faq pages won't change.
A full xref to a faq page used to look like:
{noformat}
xref:latest@manual::faq/faqpage.adoc[title]
{noformat}
Depending on the location, the 'latest@manual' might be omitted.
These will need to be located and converted to
{noformat}
xref:latest@manual:faq:faqpage.adoc[title]
{noformat}
xrefs from one faq page to another should not need updating, unless they have
more in them than needed.
I'm pretty sure, although I didn't look, that there are such xrefs in the rest
of the user manual and in component pages in every version. If this is
correct, you'll need PRs for master, 2.x, and 3.0.x.
Asciidoc supports quite a few xref formats although I always use `xref:...`
There may be `<<...>>` and possibly some sort of `[...]` format as well. I've
generally been converting alternate formats to `xref:` for interpage links when
I find them. I think these may be leftover from conversion to asciidoc.
> 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] [Work logged] (CAMEL-13812) Split up user manual
[ https://issues.apache.org/jira/browse/CAMEL-13812?focusedWorklogId=412386=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412386 ] ASF GitHub Bot logged work on CAMEL-13812: -- Author: ASF GitHub Bot Created on: 30/Mar/20 15:19 Start Date: 30/Mar/20 15:19 Worklog Time Spent: 10m Work Description: aashnajena commented on pull request #3693: [CAMEL-13812] Split FAQ into separate module under user-manual URL: https://github.com/apache/camel/pull/3693 - Created a separate module for FAQ under docs/user-manual/modules. - Added nav.doc for FAQ, and moved all related pages in docs/user-manual/modules/FAQ/pages. - Replaced links to and from the FAQ module in the entire camel repository. I'm not sure how to run link checker locally. I hope these changes make more sense. I have made them in accordance with @djencks's comments on the [JIRA issue](https://issues.apache.org/jira/browse/CAMEL-13812) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412386) Time Spent: 20m (was: 10m) > 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] [Resolved] (CAMEL-14811) Remove JMX Connector configuration
[ https://issues.apache.org/jira/browse/CAMEL-14811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh resolved CAMEL-14811. - Resolution: Fixed > Remove JMX Connector configuration > -- > > Key: CAMEL-14811 > URL: https://issues.apache.org/jira/browse/CAMEL-14811 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For 3.2.0, we should remove the JMX Connector configuration in > camel-management. Creating our own registry is not properly secure and > doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14811) Remove JMX Connector configuration
[ https://issues.apache.org/jira/browse/CAMEL-14811?focusedWorklogId=412385=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412385 ] ASF GitHub Bot logged work on CAMEL-14811: -- Author: ASF GitHub Bot Created on: 30/Mar/20 15:11 Start Date: 30/Mar/20 15:11 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #3692: CAMEL-14811 - Remove JMX Connector configuration URL: https://github.com/apache/camel/pull/3692 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412385) Time Spent: 20m (was: 10m) > Remove JMX Connector configuration > -- > > Key: CAMEL-14811 > URL: https://issues.apache.org/jira/browse/CAMEL-14811 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > For 3.2.0, we should remove the JMX Connector configuration in > camel-management. Creating our own registry is not properly secure and > doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14745) Navbar hamburger doesn't fit within the visible screen.
[ https://issues.apache.org/jira/browse/CAMEL-14745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-14745. --- Resolution: Fixed Thanks to [~Aemie] for the pull request > Navbar hamburger doesn't fit within the visible screen. > > > Key: CAMEL-14745 > URL: https://issues.apache.org/jira/browse/CAMEL-14745 > Project: Camel > Issue Type: Bug >Reporter: Aemie >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > For particular webpages, within a smaller screen width, due to a few links or > tables or text, the entire webpage doesn't fit within the screen. > > I have created the PR for the following pages as it is resolved: > * frontpage > * support page > * downloads > * GSOC page > * Contributing page > * Apache CAMEL 2020 Release Schedule page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14745) Navbar hamburger doesn't fit within the visible screen.
[ https://issues.apache.org/jira/browse/CAMEL-14745?focusedWorklogId=412333=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412333 ] ASF GitHub Bot logged work on CAMEL-14745: -- Author: ASF GitHub Bot Created on: 30/Mar/20 13:25 Start Date: 30/Mar/20 13:25 Worklog Time Spent: 10m Work Description: zregvart commented on pull request #274: CAMEL-14745: make changes to create a responsive mobile design URL: https://github.com/apache/camel-website/pull/274 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412333) Time Spent: 40m (was: 0.5h) > Navbar hamburger doesn't fit within the visible screen. > > > Key: CAMEL-14745 > URL: https://issues.apache.org/jira/browse/CAMEL-14745 > Project: Camel > Issue Type: Bug >Reporter: Aemie >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > For particular webpages, within a smaller screen width, due to a few links or > tables or text, the entire webpage doesn't fit within the screen. > > I have created the PR for the following pages as it is resolved: > * frontpage > * support page > * downloads > * GSOC page > * Contributing page > * Apache CAMEL 2020 Release Schedule page -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14742) Prevent JMX rebinding
[ https://issues.apache.org/jira/browse/CAMEL-14742?focusedWorklogId=412311=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412311 ] ASF GitHub Bot logged work on CAMEL-14742: -- Author: ASF GitHub Bot Created on: 30/Mar/20 12:34 Start Date: 30/Mar/20 12:34 Worklog Time Spent: 10m Work Description: davsclaus commented on pull request #3651: CAMEL-14742 - Prevent JMX rebinding URL: https://github.com/apache/camel/pull/3651 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412311) Time Spent: 20m (was: 10m) > Prevent JMX rebinding > - > > Key: CAMEL-14742 > URL: https://issues.apache.org/jira/browse/CAMEL-14742 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.0.2, 2.25.1, 3.2.0, 3.1.1 > > Time Spent: 20m > Remaining Estimate: 0h > > This task is to prevent JMX rebinding. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14655) Create camel-azure-storage-queue component based on SDKv12
[ https://issues.apache.org/jira/browse/CAMEL-14655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14655: Fix Version/s: (was: 3.2.0) 3.3.0 > Create camel-azure-storage-queue component based on SDKv12 > -- > > Key: CAMEL-14655 > URL: https://issues.apache.org/jira/browse/CAMEL-14655 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.1.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.3.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14511) Allow to generate component/endpoint fluent DSL with camel-package-maven-plugin:generate-component goal
[ https://issues.apache.org/jira/browse/CAMEL-14511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14511: Fix Version/s: (was: 3.2.0) 3.3.0 > Allow to generate component/endpoint fluent DSL with > camel-package-maven-plugin:generate-component goal > --- > > Key: CAMEL-14511 > URL: https://issues.apache.org/jira/browse/CAMEL-14511 > Project: Camel > Issue Type: Improvement > Components: tooling >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 3.3.0 > > > CAMEL-14503 introduces camel-package-maven-plugin:generate-component which > should be used by external component but it does not allow to generate fluent > component/endpoint DSLs. > Fluent DSLs generated cannot be part of an aggregate class like > EndpointRouteBuilder but should be possible to use at lest static methods. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14600) Auto configure component/dataformat/languages when they are initialized
[
https://issues.apache.org/jira/browse/CAMEL-14600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-14600:
Fix Version/s: (was: 3.2.0)
3.3.0
> Auto configure component/dataformat/languages when they are initialized
> ---
>
> Key: CAMEL-14600
> URL: https://issues.apache.org/jira/browse/CAMEL-14600
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
>Reporter: Luca Burgazzoli
>Priority: Major
> Fix For: 3.3.0
>
>
> As today the auto configuration of components is delegated to the runtime so
> as example, spring-boot auto configure components with the help of some
> CamelXYZAutoConfiguration classes, whereas the camel-main scans properties
> for those that starts with camel.component and configure the related
> components.
> I wonder if we can have a single point where component, dataformat, language
> & co auto-configuration take place regardless of the runtime camel runs on.
> As example for components, the auto configuration could happen when they are
> initialized like:
> - search for component-configurer (it is done already)
> - use the component-configurer - if any - to initialize the component
> The component-configurer generator could also be enhanced not only to apply
> given properties but also to look them up from the camel context with a
> method like:
> {code:java}
> public boolean configure(CamelContext camelContext, String componentName);
> {code}
>
> The advantage of such implementation would be that:
> - component are consistent configured across runtimes (i.e. at the moment
> spring boot starters have an option to provide customizers to let use tune
> component configurations)
> - with auto generated code we could reduce the need to create intermediate
> objects on camel-main
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CAMEL-14654) Create camel-azure-storage-blob component based on SDKv12
[ https://issues.apache.org/jira/browse/CAMEL-14654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-14654: Fix Version/s: (was: 3.2.0) 3.3.0 > Create camel-azure-storage-blob component based on SDKv12 > - > > Key: CAMEL-14654 > URL: https://issues.apache.org/jira/browse/CAMEL-14654 > Project: Camel > Issue Type: New Feature > Components: camel-azure >Affects Versions: 3.1.0 >Reporter: Omar Al-Safi >Assignee: Omar Al-Safi >Priority: Minor > Fix For: 3.3.0 > > > Per title -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14787) camel-zookeeper-master - Test fails on CI
[ https://issues.apache.org/jira/browse/CAMEL-14787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14787. - Resolution: Fixed > camel-zookeeper-master - Test fails on CI > - > > Key: CAMEL-14787 > URL: https://issues.apache.org/jira/browse/CAMEL-14787 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.2.0 > > > But they work locally on my osx > https://builds.apache.org/job/Camel/job/master/lastCompletedBuild/testReport/org.apache.camel.component.zookeepermaster.group/GroupTest/testOrder/ -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14798) Separate Avro dataformat out of camel-avro component
[ https://issues.apache.org/jira/browse/CAMEL-14798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-14798. - Resolution: Fixed > Separate Avro dataformat out of camel-avro component > > > Key: CAMEL-14798 > URL: https://issues.apache.org/jira/browse/CAMEL-14798 > Project: Camel > Issue Type: Improvement > Components: camel-avro >Reporter: Matej Melko >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Currently camel-avro consist of two parts, avro dataformat and camel-avro > component used for RPC. Separation could help to support avro at least > partially as a native camel-quarkus extension. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14811) Remove JMX Connector configuration
[ https://issues.apache.org/jira/browse/CAMEL-14811?focusedWorklogId=412284=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412284 ] ASF GitHub Bot logged work on CAMEL-14811: -- Author: ASF GitHub Bot Created on: 30/Mar/20 12:17 Start Date: 30/Mar/20 12:17 Worklog Time Spent: 10m Work Description: coheigea commented on pull request #3692: CAMEL-14811 - Remove JMX Connector configuration URL: https://github.com/apache/camel/pull/3692 For 3.2.0, we should remove the JMX Connector configuration in camel-management. Creating our own registry is not properly secure and doesn't buy us anything extra over just using the default JVM JMX Settings. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412284) Remaining Estimate: 0h Time Spent: 10m > Remove JMX Connector configuration > -- > > Key: CAMEL-14811 > URL: https://issues.apache.org/jira/browse/CAMEL-14811 > Project: Camel > Issue Type: Improvement >Reporter: Colm O hEigeartaigh >Assignee: Colm O hEigeartaigh >Priority: Major > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > For 3.2.0, we should remove the JMX Connector configuration in > camel-management. Creating our own registry is not properly secure and > doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14811) Remove JMX Connector configuration
Colm O hEigeartaigh created CAMEL-14811: --- Summary: Remove JMX Connector configuration Key: CAMEL-14811 URL: https://issues.apache.org/jira/browse/CAMEL-14811 Project: Camel Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Colm O hEigeartaigh Fix For: 3.2.0 For 3.2.0, we should remove the JMX Connector configuration in camel-management. Creating our own registry is not properly secure and doesn't buy us anything extra over just using the default JVM JMX Settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14810) Dff
[ https://issues.apache.org/jira/browse/CAMEL-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-14810. -- > Dff > --- > > Key: CAMEL-14810 > URL: https://issues.apache.org/jira/browse/CAMEL-14810 > Project: Camel > Issue Type: Sub-task >Reporter: Steven Allen >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Deleted] (CAMEL-14810) Dff
[ https://issues.apache.org/jira/browse/CAMEL-14810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino deleted CAMEL-14810: - > Dff > --- > > Key: CAMEL-14810 > URL: https://issues.apache.org/jira/browse/CAMEL-14810 > Project: Camel > Issue Type: Sub-task >Reporter: Steven Allen >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14810) Dff
Steven Allen created CAMEL-14810: Summary: Dff Key: CAMEL-14810 URL: https://issues.apache.org/jira/browse/CAMEL-14810 Project: Camel Issue Type: Sub-task Reporter: Steven Allen -- 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] [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] [Updated] (CAMEL-14283) camel-website - Cleanup the EIP menu
[ https://issues.apache.org/jira/browse/CAMEL-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14283: -- Component/s: website > camel-website - Cleanup the EIP menu > > > Key: CAMEL-14283 > URL: https://issues.apache.org/jira/browse/CAMEL-14283 > Project: Camel > Issue Type: Task > Components: website >Reporter: Claus Ibsen >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > 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] [Assigned] (CAMEL-14283) camel-website - Cleanup the EIP menu
[ https://issues.apache.org/jira/browse/CAMEL-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart reassigned CAMEL-14283: - Assignee: David Jencks > 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 >Assignee: David Jencks >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] [Updated] (CAMEL-14283) camel-website - Cleanup the EIP menu
[ https://issues.apache.org/jira/browse/CAMEL-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart updated CAMEL-14283: -- Fix Version/s: 3.2.0 > 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 >Assignee: David Jencks >Priority: Major > Fix For: 3.2.0 > > > 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] [Resolved] (CAMEL-14283) camel-website - Cleanup the EIP menu
[ https://issues.apache.org/jira/browse/CAMEL-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-14283. --- Resolution: Fixed I think [~djencks] fixed this already. > 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-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=17070897#comment-17070897 ] Zoran Regvart commented on CAMEL-14567: --- [~RimshaCh] have a look at the [Antora documentation|https://docs.antora.org/antora/2.2/playbook/configure-content-sources/#current-branch] > 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 > Attachments: Screenshot_2020-03-23 Apache Camel user manual - Apache > Camel.png > > > 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] [Commented] (CAMEL-14781) Support page missing toolbar breadcrumbs
[ https://issues.apache.org/jira/browse/CAMEL-14781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070894#comment-17070894 ] Zoran Regvart commented on CAMEL-14781: --- [~siyubu] feel free to experiment, you can post mockups here first if that's easier for you to get feedback. > Support page missing toolbar breadcrumbs > > > Key: CAMEL-14781 > URL: https://issues.apache.org/jira/browse/CAMEL-14781 > Project: Camel > Issue Type: Bug > Components: website >Reporter: Solange Iyubu >Priority: Major > Attachments: no toolbar nor nav_LI.jpg, no toolbar nor nav_LI.jpg > > > While navigating on apache website I saw pages that don't have toolbars > breadcrumps such as support page from community. I am going to work on it -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (CAMEL-14803) camel-karaf - Add docs for website
[ https://issues.apache.org/jira/browse/CAMEL-14803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zoran Regvart resolved CAMEL-14803. --- Resolution: Fixed The Antora docs are built from [camel-karaf/docs|https://github.com/apache/camel-karaf/tree/master/docs] there is a link on the frontpage and on the projects page. > camel-karaf - Add docs for website > -- > > Key: CAMEL-14803 > URL: https://issues.apache.org/jira/browse/CAMEL-14803 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It would be good to have the docs setup for camel-karaf like we have for > camel-spring-boot, so we can build part for the website and have camel karaf > included there too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (CAMEL-10652) Create a component for Kafka-Stream
[ https://issues.apache.org/jira/browse/CAMEL-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070887#comment-17070887 ] Dmitry Volodin edited comment on CAMEL-10652 at 3/30/20, 11:11 AM: --- Hi [~hien711] you can choose another issue marked with gsoc2020 label or ask community for selecting some another issues for you. We have a set of free issues for selection. was (Author: dmvolod): Hi [~hien711] you can choose another issue marked with gsoc2020 label or ask community for selecting some another issues for you. > Create a component for Kafka-Stream > --- > > Key: CAMEL-10652 > URL: https://issues.apache.org/jira/browse/CAMEL-10652 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-10652) Create a component for Kafka-Stream
[ https://issues.apache.org/jira/browse/CAMEL-10652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070887#comment-17070887 ] Dmitry Volodin commented on CAMEL-10652: Hi [~hien711] you can choose another issue marked with gsoc2020 label or ask community for selecting some another issues for you. > Create a component for Kafka-Stream > --- > > Key: CAMEL-10652 > URL: https://issues.apache.org/jira/browse/CAMEL-10652 > Project: Camel > Issue Type: New Feature > Components: camel-kafka >Reporter: Andrea Cosentino >Priority: Minor > Labels: gsoc2020 > Fix For: Future > > -- 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] [Updated] (CAMEL-14809) Clear icon in the search box in navbar to clear the inner contents
[ https://issues.apache.org/jira/browse/CAMEL-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prerna Singh updated CAMEL-14809: - Description: I think we can do something like this. A clear button is displayed upon entering input in the search bar's text field. Clicking on the clear button will erase the text field. We can even do this for QuickLook up search bar. I think it will slightly increase UX. was: I think we could do something like this. A clear button is displayed upon entering input in the search bar's text field. Clicking on the clear button will erase the text field. We could even do this for QuickLook up search bar. I think it will slightly increase UX. > Clear icon in the search box in navbar to clear the inner contents > --- > > Key: CAMEL-14809 > URL: https://issues.apache.org/jira/browse/CAMEL-14809 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Prerna Singh >Priority: Minor > > I think we can do something like this. > A clear button is displayed upon entering input in the search bar's text > field. Clicking on the clear button will erase the text field. > We can even do this for QuickLook up search bar. I think it will slightly > increase UX. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CAMEL-14809) Clear icon in the search box in navbar to clear the inner contents
[ https://issues.apache.org/jira/browse/CAMEL-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prerna Singh updated CAMEL-14809: - Description: I think we can do something like this: A clear button is displayed upon entering input in the search bar's text field. Clicking on the clear button will erase the text field. We can even do this for QuickLook up search bar. I think it will slightly increase UX. was: I think we can do something like this. A clear button is displayed upon entering input in the search bar's text field. Clicking on the clear button will erase the text field. We can even do this for QuickLook up search bar. I think it will slightly increase UX. > Clear icon in the search box in navbar to clear the inner contents > --- > > Key: CAMEL-14809 > URL: https://issues.apache.org/jira/browse/CAMEL-14809 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Prerna Singh >Priority: Minor > > I think we can do something like this: > A clear button is displayed upon entering input in the search bar's text > field. Clicking on the clear button will erase the text field. > We can even do this for QuickLook up search bar. I think it will slightly > increase UX. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14809) Clear icon in the search box in navbar to clear the inner contents
[ https://issues.apache.org/jira/browse/CAMEL-14809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070858#comment-17070858 ] Prerna Singh commented on CAMEL-14809: -- [~zregvart] If this idea sounds okay, I would want to work on it. I will wait for your feedback before I start. > Clear icon in the search box in navbar to clear the inner contents > --- > > Key: CAMEL-14809 > URL: https://issues.apache.org/jira/browse/CAMEL-14809 > Project: Camel > Issue Type: Improvement > Components: website >Reporter: Prerna Singh >Priority: Minor > > I think we could do something like this. > A clear button is displayed upon entering input in the search bar's text > field. Clicking on the clear button will erase the text field. > We could even do this for QuickLook up search bar. I think it will slightly > increase UX. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (CAMEL-14809) Clear icon in the search box in navbar to clear the inner contents
Prerna Singh created CAMEL-14809: Summary: Clear icon in the search box in navbar to clear the inner contents Key: CAMEL-14809 URL: https://issues.apache.org/jira/browse/CAMEL-14809 Project: Camel Issue Type: Improvement Components: website Reporter: Prerna Singh I think we could do something like this. A clear button is displayed upon entering input in the search bar's text field. Clicking on the clear button will erase the text field. We could even do this for QuickLook up search bar. I think it will slightly increase UX. -- 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] [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-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=17070848#comment-17070848 ] JyotiAttri commented on CAMEL-14772: [~davsclaus], Thanks for help > 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-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=17070848#comment-17070848 ] JyotiAttri edited comment on CAMEL-14772 at 3/30/20, 10:01 AM: --- [~davsclaus], Thanks for the help. was (Author: jyotiattri): [~davsclaus], Thanks for help > 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] [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=17070846#comment-17070846 ] Claus Ibsen commented on CAMEL-14772: - Apache Camel https://github.com/apache/camel-website/blob/master/antora-ui-camel/src/img/logo-d.svg > 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] [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=17070844#comment-17070844 ] Claus Ibsen commented on CAMEL-14772: - The logos are from different open source projects. Apache Kafka https://svn.apache.org/repos/asf/kafka/site/logos/ Apache Karaf https://cwiki.apache.org/confluence/display/KARAF/Logo Spring Boot https://developer.ibm.com/zsystems/wp-content/uploads/sites/75/2018/05/icon-spring-boot.jpg Quarkus https://quarkus.io/blog/quarkus-has-a-new-logo/ https://github.com/quarkusio/quarkus/blob/master/docs/src/main/resources/theme/images/quarkus-logo.svg Knative https://github.com/knative/docs/tree/master/docs/images/logo > 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] [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] [Work logged] (CAMEL-14803) camel-karaf - Add docs for website
[ https://issues.apache.org/jira/browse/CAMEL-14803?focusedWorklogId=412180=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412180 ] ASF GitHub Bot logged work on CAMEL-14803: -- Author: ASF GitHub Bot Created on: 30/Mar/20 08:13 Start Date: 30/Mar/20 08:13 Worklog Time Spent: 10m Work Description: zregvart commented on pull request #1: CAMEL-14803: documentation for camel-karaf modules URL: https://github.com/apache/camel-karaf/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412180) Time Spent: 20m (was: 10m) > camel-karaf - Add docs for website > -- > > Key: CAMEL-14803 > URL: https://issues.apache.org/jira/browse/CAMEL-14803 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It would be good to have the docs setup for camel-karaf like we have for > camel-spring-boot, so we can build part for the website and have camel karaf > included there too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Work logged] (CAMEL-14803) camel-karaf - Add docs for website
[ https://issues.apache.org/jira/browse/CAMEL-14803?focusedWorklogId=412175=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-412175 ] ASF GitHub Bot logged work on CAMEL-14803: -- Author: ASF GitHub Bot Created on: 30/Mar/20 08:03 Start Date: 30/Mar/20 08:03 Worklog Time Spent: 10m Work Description: zregvart commented on pull request #1: CAMEL-14803: documentation for camel-karaf modules URL: https://github.com/apache/camel-karaf/pull/1 This makes sure that the documentation for modules within camel-karaf is copied over to the Antora documentation directory and that the links from components.adoc point to the documents there. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org Issue Time Tracking --- Worklog Id: (was: 412175) Remaining Estimate: 0h Time Spent: 10m > camel-karaf - Add docs for website > -- > > Key: CAMEL-14803 > URL: https://issues.apache.org/jira/browse/CAMEL-14803 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > It would be good to have the docs setup for camel-karaf like we have for > camel-spring-boot, so we can build part for the website and have camel karaf > included there too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14531) Support for OpenTelemetry
[ https://issues.apache.org/jira/browse/CAMEL-14531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070773#comment-17070773 ] Firnas Aleem commented on CAMEL-14531: -- hi, My name is Firnas, Msc student from Colombo, Sri Lanka. I am new to this Apache open source development. But I am confident that I can develop skills on this when I spend more time in future. I would like to work on this task for gsoc2020. I have just started looking in to this. can someone guide me to write proposal ? thanks. > Support for OpenTelemetry > - > > Key: CAMEL-14531 > URL: https://issues.apache.org/jira/browse/CAMEL-14531 > Project: Camel > Issue Type: New Feature >Reporter: Luca Burgazzoli >Priority: Major > Labels: gsoc2020, help-wanted, metrics, tracing > Fix For: 3.x > > > [OpenTelemetry|https://opentelemetry.io/] is becoming more and more relevant > and would be nice to support it in camel -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (CAMEL-14803) camel-karaf - Add docs for website
[ https://issues.apache.org/jira/browse/CAMEL-14803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17070730#comment-17070730 ] Claus Ibsen commented on CAMEL-14803: - Okay the maven plugin can know this if the Maven GAV groupId is org.apache.camel vs org.apache.camel.karaf > camel-karaf - Add docs for website > -- > > Key: CAMEL-14803 > URL: https://issues.apache.org/jira/browse/CAMEL-14803 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Assignee: Zoran Regvart >Priority: Major > Fix For: 3.2.0 > > > It would be good to have the docs setup for camel-karaf like we have for > camel-spring-boot, so we can build part for the website and have camel karaf > included there too. -- This message was sent by Atlassian Jira (v8.3.4#803005)
