Hi Ananth,
The javadocs are already generated through the CI and the user docs ideally
would be also, see release page for details:
http://apex.apache.org/release.html
The release documentation is linked from the download page:
http://apex.apache.org/downloads.html
I think it would be good to si
Thanks for the feedback Thomas and Tushar.
@Thomas: I am wondering if the javadocs ( if that is what you meant by
documentation being a release artefact ) can be hosted on an external
system ? ( Ex: Flink seems to be simply pointing to ci.apache.org). I will
cut down the top level menu of "Ecosyst
+1 for website revamp with Jekyll.
Regarding the details:
Documentation is a release artifact that needs to remain decoupled from
other web site content. I would propose to keep the documentation
build/release process out of this effort.
The top level navigation looks a bit crowded. I would sugg
Hi Ananth,
The new pages looks awsome. I would like to collbrate on improving the
website. Do let me know how can I help?
- Tushar.
On Thu, Jun 21, 2018 at 8:03 AM Ananth G wrote:
>
> Hello All,
>
> Per some JIRA tickets and other PR review comments, having a single
> cohesive website along wit
Hello All,
Per some JIRA tickets and other PR review comments, having a single
cohesive website along with blogging capabilities seems to be long due for
Apache Apex.
I would like to propose moving the Apache Apex website to Jekyll to address
the following high level concerns:
- Aim to provide a
