aashnajena edited a comment on pull request #432: URL: https://github.com/apache/camel-website/pull/432#issuecomment-661358432
For all three points, I just want to say that I want to keep things as automated as possible. - The last few links are not needed on the user manual sitemap I agree. I wasn't able to figure out a way to particularly exclude those so I'm not sure how to proceed there. - Since we're giving the user easy access to all links present, I don't see why we shouldn't include Releases. The pages under "Releases" are different from those under "Blog" and picking pages to remove from the sitemap would just make it more customized, less automated. - Renaming Mailing List is out of the scope of this PR, but we should definitely do that. We should also consider moving "building" and "sources" with the other documentation pages. - If we want FAQ to be a separate component, we should refactor that in the Camel repository, and it will reflect here automatically. I remember that when I was refactoring FAQ into a separate module on the Camel repo, I had initially converted it to a different component altogether, but everyone was not happy about it, so we put it as a module inside User Manual. - I did initially go with 3 columns because it definitely does use much less vertical space. But 3 columns become very congested for entries under FAQ or Security which have long headings, so I went with the safer middle option. Overall, since this is the first iteration, I want to keep it simple with one common layout and common CSS. It's hard to keep track of which titles to trim and which entries to exclude because the pages keep growing and changing. ---------------------------------------------------------------- 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
