[GitHub] [camel-website] aashnajena opened a new pull request #370: [CAMEL-14994] Improve Projects Page

classic Classic list List threaded Threaded
30 messages Options
12
Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena opened a new pull request #370: [CAMEL-14994] Improve Projects Page

GitBox

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


   First draft for improving the projects page. I'm opening the PR so that the preview is available. Need feedback on a couple of things :
   - I've taken icons from Eva, from where icons in the "Packed with Functionality"  section (on front page) are taken. Do the outlined icons look better or the filled ones?
   - Do we need to add text explaining the icons?
   - As pointed out on the JIRA issue, the mailing list is common for all projects, so should we include that in each project box?
   - As pointed out on the JIRA issue, we should be adding links to examples. What's the best way to add those?
   - Quarkus has a separate Gitter chat. Do other projects have this too? We can add links to those.
   
   Also, in <1024 screens, the h1 headings were becoming smaller than other headings, so I removed that.
   


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena removed a comment on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox

aashnajena removed a comment on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-634297521


   > There's a comment on the [issue](https://issues.apache.org/jira/browse/CAMEL-14994) to include the examples. In addition I think we should have text labels along with icons to make the touch targets a bit bigger on smaller screens and to make the distinction between the source and example repositories clearer.
   >
   > The projects.css rules need to be scoped to `.projects` and it would be better to use semantic markup where applicable.
   
   


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena closed pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena closed pull request #370:
URL: https://github.com/apache/camel-website/pull/370


   


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-634297521






----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

zregvart commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-634286045


   There's a comment on the [issue](https://issues.apache.org/jira/browse/CAMEL-14994) to include the examples. In addition I think we should have text labels along with icons to make the touch targets a bit bigger on smaller screens and to make the distinction between the source and example repositories clearer.
   
   The projects.css rules need to be scoped to `.projects` and it would be better to use semantic markup where applicable.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] davsclaus commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

davsclaus commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-634426090


   Yeah nice with icon and a little text
   
   - Docs
   - Examples
   - Source


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-636330127


   Please review the changes. Also, are there any changes needed in the projects section on the front-page? Since all important links are on this page now, I think it would be good if we link the projects displayed on the front page to their corresponding entries on the "Projects" page.
   
   On the front page, instead of providing description+links, we can just have the logo, one-line description, and make it clickable so that it links to the projects page. I think having a link to just "documentation" on the front page makes it look like that's the only important link.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena edited a comment on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena edited a comment on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-636330127


   Please review the changes. Also, are there any changes needed in the projects section on the front-page? Since all important links are on this page now, I think it would be good if we link the projects displayed on the front page to their corresponding entries on the "Projects" page.
   
   On the front page, instead of providing description+links, we can just have the logo, one-line description, and make it clickable so that it links to the projects page. I think having a link to just "documentation" on the front page makes it look like that's the only important link.
   
   @zregvart also mentioned that we should do away with the "Camel Sub-Projects Documentation" section under the "Documentation" menu


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

zregvart commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-636673556


   What I’ve noticed Is that in the mobile version the links overlap.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-637489066


   What's the smallest width for which we need to adjust our design? Right now, the buttons get broken at <400px width, so I will fix that.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

zregvart commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-637993771


   @aashnajena I test on my phone, which has 375 points width (750 pixels), when testnih in the browser I test with Samsung Galaxy 6/9 which has 360 points (IIRC).
   
   Here are some statistics to consider:
   https://gs.statcounter.com/screen-resolution-stats/mobile/worldwide


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on a change in pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

zregvart commented on a change in pull request #370:
URL: https://github.com/apache/camel-website/pull/370#discussion_r434822637



##########
File path: antora-ui-camel/src/css/projects.css
##########
@@ -0,0 +1,94 @@
+.projects h2 {
+  text-align: center;
+}
+
+.projects .box {
+  display: inline-flex;
+  border: 1px solid var(--color-smoke-90);
+  width: 46%;
+  flex-direction: column;
+  align-items: center;
+  padding: 1rem;
+  margin: 1rem;
+}
+
+.projects .box a > img {
+  display: inline-block;
+  width: auto;
+  height: 5rem;
+}
+
+.projects .box a > img + img {
+  padding-left: 1rem;
+}
+
+.projects .box .description {
+  padding: 1rem;
+  text-align: center;
+}
+
+.projects .box .links {
+  align-items: center;
+  margin: 1.5rem 0;
+}
+
+.projects .box .links img {
+  display: inline-flex;
+  margin: 0 0.25rem;
+  width: 1rem;
+  height: 1rem;
+  vertical-align: -0.18rem;
+  filter: invert(24%) sepia(38%) saturate(1353%) hue-rotate(200deg) brightness(89%) contrast(99%);
+}
+
+.projects .box .links span {
+  padding: 0.5rem;
+  margin: 0 0.4rem;
+  border: 1px solid var(--color-gray-10);
+  border-radius: 10rem;
+  color: var(--body-font-color);
+}
+
+.projects .box .links span:hover {
+  color: var(--body-font-color);
+  border: 2px solid var(--color-gray-30);
+}
+
+.projects .box .links a:hover {
+  text-decoration: none;
+}
+
+@media screen and (max-width: 1023px) {
+  .projects .box {
+    width: 100%;
+    margin: 1rem 0;
+  }
+}
+
+@media screen and (max-width: 480px) {
+  .projects .box .links {
+    padding: 0.4rem 0;
+  }
+
+  .projects .box .links span {
+    margin: 0 0.2rem;
+    padding: 0.4rem;
+  }
+
+  .projects .box {
+    padding: 1rem 0.4rem;
+  }
+
+  .projects .box .links img {
+    height: 0.8rem;
+    width: 0.8rem;
+    vertical-align: -0.1rem;
+    margin: 0 0.2rem;

Review comment:
       This looks very odd, we should a simpler and more straightforward way to center images.

##########
File path: antora-ui-camel/src/css/projects.css
##########
@@ -0,0 +1,94 @@
+.projects h2 {
+  text-align: center;
+}
+
+.projects .box {
+  display: inline-flex;
+  border: 1px solid var(--color-smoke-90);
+  width: 46%;
+  flex-direction: column;
+  align-items: center;
+  padding: 1rem;
+  margin: 1rem;
+}
+
+.projects .box a > img {
+  display: inline-block;
+  width: auto;
+  height: 5rem;
+}
+
+.projects .box a > img + img {
+  padding-left: 1rem;
+}
+
+.projects .box .description {
+  padding: 1rem;
+  text-align: center;
+}
+
+.projects .box .links {
+  align-items: center;
+  margin: 1.5rem 0;
+}
+
+.projects .box .links img {
+  display: inline-flex;
+  margin: 0 0.25rem;
+  width: 1rem;
+  height: 1rem;
+  vertical-align: -0.18rem;
+  filter: invert(24%) sepia(38%) saturate(1353%) hue-rotate(200deg) brightness(89%) contrast(99%);

Review comment:
       This seems overly complex to change the color of a path in SVG, have a look at how we use SVGs for the social/GitHub icons and can change the color via SVG. We need the color to be managed via a variable in the vars.css.

##########
File path: content/projects/_index.md
##########
@@ -2,36 +2,140 @@
 title: Apache Camel Projects
 ---
 
+{{< div "box" >}}
+
+[![Camel](/_/img/logo-d.svg)](/manual/latest/)
+
+## Camel
+
+{{< div "description" >}}
+
+Apache Camel is the Swiss knife of integration. It is an open source integration framework that is packed with several hundred components that are used to access databases, message queues and APIs, helping you integrate with everything.
+
+{{< /div >}}
+
+{{< div "links" >}}
+
+[<span><img src="../img/icons/book-icon.svg" />Docs</span>](/manual/latest/)

Review comment:
       Can we put the images in the `img` directory, they already have the `-icon` in the name no need for a separate directory to hold them. I think we can use the absolute paths to images, i.e. `/_/img/`, as we do for the Camel logo above.

##########
File path: static/img/icons/book-icon.svg
##########
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><g data-name="Layer 2"><g data-name="book"><rect width="24" height="24" opacity="0"/><path d="M19 3H7a3 3 0 0 0-3 3v12a3 3 0 0 0 3 3h12a1 1 0 0 0 1-1V4a1 1 0 0 0-1-1zM7 5h11v10H7a3 3 0 0 0-1 .18V6a1 1 0 0 1 1-1zm0 14a1 1 0 0 1 0-2h11v2z"/></g></g></svg>

Review comment:
       Images need to be placed in the `antora-ui-camel/src/img` directory, we have a pipeline for optimizing SVGs at build time.

##########
File path: antora-ui-camel/src/css/doc.css
##########
@@ -652,11 +652,6 @@ kbd,
 }
 
 @media screen and (max-width: 1023px) and (min-width: 480px) {
-  .doc > h1.page:first-child,
-  .static > h1:first-child {
-    font-size: inherit;
-  }
-

Review comment:
       I'm wondering why this was removed?

##########
File path: antora-ui-camel/src/css/projects.css
##########
@@ -0,0 +1,94 @@
+.projects h2 {
+  text-align: center;
+}
+
+.projects .box {
+  display: inline-flex;
+  border: 1px solid var(--color-smoke-90);
+  width: 46%;
+  flex-direction: column;
+  align-items: center;
+  padding: 1rem;
+  margin: 1rem;
+}
+
+.projects .box a > img {
+  display: inline-block;
+  width: auto;
+  height: 5rem;
+}
+
+.projects .box a > img + img {
+  padding-left: 1rem;
+}
+
+.projects .box .description {
+  padding: 1rem;
+  text-align: center;
+}
+
+.projects .box .links {
+  align-items: center;
+  margin: 1.5rem 0;
+}
+
+.projects .box .links img {
+  display: inline-flex;
+  margin: 0 0.25rem;
+  width: 1rem;
+  height: 1rem;
+  vertical-align: -0.18rem;
+  filter: invert(24%) sepia(38%) saturate(1353%) hue-rotate(200deg) brightness(89%) contrast(99%);
+}
+
+.projects .box .links span {
+  padding: 0.5rem;
+  margin: 0 0.4rem;
+  border: 1px solid var(--color-gray-10);
+  border-radius: 10rem;
+  color: var(--body-font-color);
+}
+
+.projects .box .links span:hover {
+  color: var(--body-font-color);
+  border: 2px solid var(--color-gray-30);

Review comment:
       This changes the metrics of the link and causes a reflow.




----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-638946145


   > I think this change bites more than it needs to, I would make it much simpler for the first iteration.
   >
   > I have concerns about introducing new design elements without incorporating them with the rest of the website, e.g. looking at the difference between the way similarly purposed design is presented on the frontpage and on the projects page links that look like buttons are very much different than the current design; underlining the headings for project names; abbreviating "Documentation" to "Docs"; having a border around project cards.
   >
   > I think we should consolidate the design across the frontpage and the projects page.
   
   Okay, I understand. Here's what I think we can do :
   1) Make the CSS as much common as possible for front page projects section and projects page. We can include the border on the front page and remove the underlined headings on the projects page (although this is the default behaviour of H2 on the rest of the website)
   2) We can either remove the button-shaped links on the projects page and make them similar to the frontpage : eg ``` option1 | option2 | option3 ```  or we could adapt the frontpage - have just the icons for each project card, because the buttons with icons+text would be too big.
   3) As for the abbreviations, documentation -> docs was done to reduce the length. I agree, on the menu and the front page, we have used the term "documentation", but I feel that "docs" is quite an accepted abbreviation and earlier we used to have a "read the docs" button on the front page. I'm not sure about this issue though, please tell me what to do here. As mentioned in (2), we can replicate the way links are presented on the front page.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

zregvart commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-639741181


   @aashnajena sounds great, I'd like to unify the design across the front page and the projects page, I suggest that we start with the simplest design and work from that. I'm really adverse to shortening the words, e.g. documentation to docs, this is my personal preference, doesn't have to be universally shared.
   
   I strongly believe that making things simpler takes more effort and that it pays of in the future by making maintenance/changes easier to do. We need to have a consistent design, I suggest that we start with the minimal changes and unify/change design between the front page and the projects page.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on a change in pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on a change in pull request #370:
URL: https://github.com/apache/camel-website/pull/370#discussion_r436252592



##########
File path: antora-ui-camel/src/css/doc.css
##########
@@ -652,11 +652,6 @@ kbd,
 }
 
 @media screen and (max-width: 1023px) and (min-width: 480px) {
-  .doc > h1.page:first-child,
-  .static > h1:first-child {
-    font-size: inherit;
-  }
-

Review comment:
       This piece of code is causing h1's font-size to become smaller than other headings (only for 480px-1023px).
   
   ![image](https://user-images.githubusercontent.com/32356795/83940521-64a29900-a802-11ea-8320-77a70822b633.png)
   




----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-640187864


   @zregvart Okay, here's what I think : On the rest of the website, links are never presented as buttons, and I don't see icons associated with links either. I think it's best to keep the project card simple like shown below :
   
   ![projects-design-simple](https://user-images.githubusercontent.com/32356795/83965506-cc73e500-a8d1-11ea-8634-d44b3a1575e1.png)
   
   I feel that we're repeating too much information on the front page, like description and links. When I visit the front page and see the projects section, I think that documentation is the only available link for each project. I propose that we make the front page "projects" section much simpler, with logos, heading and one-line description. This is completely reusing the design from the projects page.
   
   ![frontpage-projects-simple](https://user-images.githubusercontent.com/32356795/83965560-1d83d900-a8d2-11ea-9538-f8bbb85af3b0.png)
   
   If the user wants to read more about this project, they can click on the card, which can take them to the projects page. Right now, clicking on the logo takes you to the manual for the project. I think we can maintain the hierarchy as frontpage-project-card (small description) --> projects-section project card (longer description + useful links) --> project manuals (detailed documentation).
   
   Would we prefer this or do we want links on the front page as well?


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena edited a comment on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena edited a comment on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-640187864


   @zregvart Okay, here's what I think : On the rest of the website, links are never presented as buttons, and I don't see icons associated with links either. I think it's best to keep the project card simple like shown below :
   
   ![projects-design-simple](https://user-images.githubusercontent.com/32356795/83965506-cc73e500-a8d1-11ea-8634-d44b3a1575e1.png)
   
   I feel that we're repeating too much information on the front page, like description and links. When I visit the front page and see the projects section, I think that documentation is the only available link for each project. I propose that we make the front page "projects" section much simpler, with logos, heading and one-line description. This is completely reusing the design from the projects page.
   
   
   ![image](https://user-images.githubusercontent.com/32356795/83965666-d9dd9f00-a8d2-11ea-814f-36b699aed920.png)
   
   
   If the user wants to read more about this project, they can click on the card, which can take them to the projects page. Right now, clicking on the logo takes you to the manual for the project. I think we can maintain the hierarchy as frontpage-project-card (small description) --> projects-section project card (longer description + useful links) --> project manuals (detailed documentation).
   
   Would we prefer this or do we want links on the front page as well?


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena edited a comment on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena edited a comment on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-640187864


   @zregvart Okay, here's what I think : On the rest of the website, links are never presented as buttons, and I don't see icons associated with links either. I think it's best to keep the project card simple like shown below :
   
   ![projects-design-simple](https://user-images.githubusercontent.com/32356795/83965506-cc73e500-a8d1-11ea-8634-d44b3a1575e1.png)
   
   I feel that we're repeating too much information on the front page, like description and links. When I visit the front page and see the projects section, I think that documentation is the only available link for each project. I propose that we make the front page "projects" section much simpler, with logos, heading and one-line description. This is completely reusing the design from the projects page.
   
   
   ![image](https://user-images.githubusercontent.com/32356795/83965666-d9dd9f00-a8d2-11ea-814f-36b699aed920.png)
   
   
   If the user wants to read more about this project, they can click on the card, which can take them to the projects page. Right now, clicking on the logo takes you to the manual for the project. I think we can maintain the hierarchy as frontpage-project-card (small description) --> projects-page-project-card (longer description + useful links) --> project manuals (detailed documentation).
   
   Would we prefer this or do we want links on the front page as well?


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] aashnajena commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-640198967


   Pushed changes which resolve/undo most of the issues mentioned above, and simplify the front-page.  @zregvart @davsclaus Please go through how the front-page and projects-page look for different screen sizes now. If we want to restore the bigger descriptions/ links on front-page, it wouldn't be hard.


----------------------------------------------------------------
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:
[hidden email]


Reply | Threaded
Open this post in threaded view
|

[GitHub] [camel-website] zregvart commented on pull request #370: [CAMEL-14994] Improve Projects Page

GitBox
In reply to this post by GitBox

zregvart commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-640222277


   This also needs to be rebased on latest changes in master branch.


----------------------------------------------------------------
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:
[hidden email]


12