Hi Karen, thanks for taking interest in our project and especially around the documentation! Some answers inline.
On Mon, Apr 26, 2021 at 10:54 PM Karen Lease <karenlease...@gmail.com> wrote: > > Thanks for the reply. > > In fact, when I click the "Edit this page" link, it takes me to the git > repository page with this message: > > "You need to fork this repository to propose changes. > Sorry, you’re not able to edit this repository directly—you need to fork > it and propose your changes from there instead." > > I am connected with my github account but apparently that's not sufficient. Yes, this is the process, on GitHub contributions by way of pull requests can be done only from forks. Though clicking on "Fork this repository" should set everything up for you and you should be able to do edits from there and propose changes via pull requests. The preview is done only for the changes made to the apache/camel-website repository, for changes to other repositories (like apache/camel) we don't have the preview. After merging the changes, if there are no issues found by checks the website is updated in the next 20-30min. > >> Since the actual website matches the adoc file, I assume the md file in > >> camel-website is obsolete. There are some other files which have both > >> .adoc & .md files. Would it make sense to delete the .md files from the > >> camel-website if those are obsolete? We started with content from the previous system (Confluence Wiki), and in the process of conversion sometimes we duplicated the effort and ended up with copies. The website gathers content from multiple repositories (and branches) and formats (asciidoc and markdown). We never took the time to implement a documentation strategy, as to where what kind of content is placed. For me it would make more sense to have the user stories outside of the user manual, that is in the markdown file. That ends up being published here: https://camel.apache.org/community/user-stories/ And that's the version we link from the community page (https://camel.apache.org/community/). If that makes sense to folk, it seems that we need to refresh that markdown file with the changes that went into the asciidoc file in the user manual and consider removing that copy. zoran -- Zoran Regvart
