[
https://issues.apache.org/jira/browse/CAMEL-15185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155959#comment-17155959
]
Aemie edited comment on CAMEL-15185 at 7/11/20, 12:12 PM:
----------------------------------------------------------
[~aashnajena], I really liked their idea of sitemap on the apple site and as
ours is heavily documented, sitemap would make it really easy. I dealt with the
privacy policy and created a PR for that so it will be great if you can work on
a sitemap. However, the one thing we discussed on the call was to generate the
whole sitemap. So it will be nice if you can create the issue and then we can
have the discussion for it there.
I thought about it, so just sharing the idea here. What we could do is we want
the sitemap as one of the Hugo pages. So within the content folder, we could
create an automated version of each part like Blog, User Manual, Components,
EIP, and so on and then just use the Hugo attributes to list within the HTML
file in the layouts folder. The only thing is to create the automated version
'cause it keeps updating and we could fetch it through ./documentation folder
in the repo and make use of the title tag of each HTML file (we could use gulp
for this).
was (Author: aemie):
[~aashnajena], I really liked their idea of sitemap on the apple site and as
ours is heavily documented, sitemap would make it really easy. I dealt with the
privacy policy and created a PR for that so it will be great if you can work on
a sitemap. However, the one thing we discussed on the call was to generate the
whole sitemap. So it will be nice if you can create the issue and then we can
have the discussion for it there.
I thought about it, so just sharing the idea here. What we could do is we want
the sitemap as one of the Hugo pages. So within the content folder, we could
create an automated version of each part like Blog, User Manual, Components,
EIP, and so on and then just use the Hugo attributes to list within the HTML
file in the layouts folder. The only thing is to create the automated version
'cause it keeps updating and we can fetch it through ./documentation folder in
the repo.
> Improve Footer on Camel Website
> -------------------------------
>
> Key: CAMEL-15185
> URL: https://issues.apache.org/jira/browse/CAMEL-15185
> Project: Camel
> Issue Type: Improvement
> Components: website
> Reporter: Aashna Jena
> Priority: Major
> Labels: outreachy2020, suggestions
> Attachments: footer-design-2.png, footer-design.png,
> footer-mobile-1.1.png, footer-mobile-1.2.png
>
>
> I have some reservations about the website footer. On the mobile view, the
> footer takes up almost the entire height of my device because the Overview,
> Community and About columns do not fit into one row. Secondly, on the desktop
> view, the header navigation is fixed at the top, so I can view the header
> menu while I'm at the footer of the page. Having same links visible on the
> header menu and footer doesn't make sense to me (Download, Community, Blog
> etc). I do see a lot of websites having menu links on the footer, but they
> don't have a fixed navbar.
> Suggestions : I looked up best practices for footers. I think we can reduce
> the number of links we display on the footer, especially the ones overlapping
> with header menu. We can also add some things (from what I read up on best
> practices) - form for subscribing to the mailing list, sitemap link, contact
> information, link to report a bug on the website, privacy policy/ terms of
> use (if we have) and maybe a subscription for the blog, since we have quite
> informative and regular blog posts. I also really like the idea of having a
> row of social media icons in the footer, which a lot of websites do. This
> will give us the freedom of adding many more icons than on the header menu.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
