HBASE-29689 Upgrade the website

[yuriipalam]

The improved, basically new, Apache HBase website.

Demo: https://hbase-landing.vercel.app/

The detailed description is available in README.md

Brief overview:

• Use React.js & TypeScript
• Everything is statically generated at build time and works even if JS is disabled
• Integrated to the Maven ecosystem (hopefully it works)
• Modern look, dark/light themes, fully responsive

[stoty]

I don't think we're going to use this in production

[stoty]

Generally, we need to figure out how this integrates into the existing Website update workflow.
(For which we need someone who knows how the existing workflow is built)

[wchevreuil]

Generally, we need to figure out how this integrates into the existing Website update workflow. (For which we need someone who knows how the existing workflow is built)

@Apache9 , can you help us with that? Also, would you share your views on this website redesign proposal?

[Apache9]

I'm OK with the new design, looks good.

What we pushed to the hbase-site repo will be published to hbase.apache.org. The .asf.yaml can control which branch to publish, now we use asf-site branch.

So maybe we could manually push our new site to another branch, try publishing it and see the result. If we think it is OK, then we can working on change the current publish website job to do it automatically.

And since the old branch is still there, if there are something wrong, we can switch back to the old web site.

[PDavid]

Many thanks, especially for the detailed README. Really nice. 👍

Just that the type check failed in the PR build with some strange "Error: Cannot find native binding. " error.

Also we should add the ASF licence to the top of every source file and the spotless check (formatter) is complaining.

You can check the comments left by the Apache HBase build bot.

[PDavid]

I'm OK with the new design, looks good.

What we pushed to the hbase-site repo will be published to hbase.apache.org. The .asf.yaml can control which branch to publish, now we use asf-site branch.

So maybe we could manually push our new site to another branch, try publishing it and see the result. If we think it is OK, then we can working on change the current publish website job to do it automatically.

And since the old branch is still there, if there are something wrong, we can switch back to the old web site.

Thanks @Apache9, great idea! 👍

I built the new website locally and pushed to the website repo on this branch: https://github.com/apache/hbase-site/tree/asf-site-staging

According to https://github.com/apache/infrastructure-asfyaml#staging-a-web-site-preview-domain we can stage (live preview) another branch, so opened a new PR for staging this new website branch:
apache/hbase-site#11

Can you please have a look?

[PDavid]

Many thanks Yurii for the additional improvements, looks really nice. 💪

I found some very minor issues.

[PDavid]

Many thanks, looks good to me.

Would be great if the PR build could go through. Maybe rebasing on master could help.

[PDavid]

OK, now the preview website is live at:
https://hbase-beta.staged.apache.org/

EDIT: The website might be unavailable as it takes a lot of time to check out the site git repo. I asked the ASF Infra on Slack.

[stoty]

It's still not available.

[PDavid]

It's still not available.

Yes, unfortunately. Yesterday there was a timeout checking out the git repo, The ASF Infra team re-triggered it but did not saw why it is not working yet.
It certainly is a big repo at 8.4GB to clone it.

[PDavid]

OK, now https://hbase-beta.staged.apache.org/ is working.

[Apache9]

OK, now https://hbase-beta.staged.apache.org/ is working.

Looks good. We could send an email to the mailing list to attract more feedbacks.

[NihalJain]

Site looks great. Just wondering how do we handle dynamic content like teams page? I see its hardcoded here. I think its important to do an audit and call out all such discrepancies in this version of site.

[PDavid]

I found some minor issues in links under the "Documentation and API" menu:

• In "1.4 Documentation" we have a User API (Test) link in this new website but that does not exists for this version (HTTP 404 - Not Found). On our current production site we have a Developer API link there instead.
• In "2.3 Documentation" the link for "Reference Guide (PDF)" is not correct. It is https://hbase.apache.org/2.3/book.pdf but it should be https://hbase.apache.org/2.3/apache_hbase_reference_guide.pdf
• In "2.4 Documentation" the link for "Reference Guide (PDF)" is not correct. It is https://hbase.apache.org/2.4/book.pdf but it should be https://hbase.apache.org/2.4/apache_hbase_reference_guide.pdf

[yuriipalam]

@NihalJain thanks for the review. Now we generate the developers.json file at a build time based on the content of the pom.xml file. Then in the code we just render the list. So pom.xml remains as the source of truth, what do you think?

@PDavid Thanks again, I fixed the issues.

[Apache-HBase]

💔 -1 overall

Vote	Subsystem	Runtime	Logfile	Comment
+0 🆗	reexec	0m 0s		Docker mode activated.
-1 ❌	patch	0m 8s		#7419 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem	Report/Notes
GITHUB PR	#7419
Console output	https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-7419/8/console
versions	git=2.17.1
Powered by	Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

[Apache-HBase]

💔 -1 overall

Vote	Subsystem	Runtime	Logfile	Comment
+0 🆗	reexec	0m 0s		Docker mode activated.
-1 ❌	patch	0m 13s		#7419 does not apply to master. Rebase required? Wrong Branch? See https://yetus.apache.org/documentation/in-progress/precommit-patchnames for help.

Subsystem	Report/Notes
GITHUB PR	#7419
Console output	https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-7419/8/console
versions	git=2.34.1
Powered by	Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.