It's just another tool in your belt. You can use it, but don't have to.
We used it for the Hugo migration, where we could only test some things
(like the rewrite rules) in a production-like environment.
I'm +0 on whether to move the docs to the repo or not.
On 27/03/2023 14:46, Jing Ge wrote:
Wow, that is good news! Thanks Chesnay for your effort.
I'd like to ask the same question as what Matthias asked. Speaking of the
workflow, should we first push changes to the asf-staging branch and check
it at https://flink.staged.apache.org and then cp them to the asf-site?
Should there always be two separate commits, one for changes and a direct
follow up one for rebuilding the site?
Best regards,
Jing
On Mon, Mar 27, 2023 at 1:39 PM Matthias Pohl
<matthias.p...@aiven.io.invalid> wrote:
Thanks for sharing that information.
Is there a specific workflow expected for pushing changes? Shall we always
go through the staging environment first or is it more like a nice-to-have
feature?
I'm also wondering whether we should move the documentation from the
Confluent page into the README file in apache/flink-web [1]. The wiki feels
to be too far away from the code here. WDYT?
Matthias
[1] https://github.com/apache/flink-web#readme
On Mon, Feb 6, 2023 at 5:09 PM Chesnay Schepler <ches...@apache.org>
wrote:
Hello,
Just so more people are aware of it, I recently enabled a staging
environment for the Flink Website.
You can push the rebuilt website to the asf-staging branch in flink-web,
and the changes will be visible at https://flink.staged.apache.org
shortly.
This has been documented at
https://cwiki.apache.org/confluence/display/FLINK/Website.
Currently a Hugo-based version of the Website (FLINK-22922) can be seen
in the staging environment.
Cheers
