| commit | c9b36438f5d6515fae3b52e3fb8b2e060ae92a16 | [log] [tgz] |
|---|---|---|
| author | Gerben <gerben@treora.com> | Sun Mar 29 18:51:14 2020 +0200 |
| committer | BigBlueHat <byoung@bigbluehat.com> | Mon Mar 30 10:20:14 2020 -0400 |
| tree | 93291ee9b68efe3bb4898815a5f81abd0d64f7a5 | |
| parent | 019149f74e00d7ad5de2700a1b5fa3813ec623e0 [diff] |
Use git submodule to deduplicate demo code. It seems more managable than duplicated code, but it is not yet ideal either. Some subideal aspects: The demo on the website currently has the header and footer of the main page; this is now removed. Is that an issue? It now puts the demo at /content/demo, but for this has to put style.css into /content/. We could consider to instead put the whole /web/dist from upstream into /content/web (or whatever name), but then the demo URL will change to be web/demo. Files get removed, built and copied in a single line in package.json. Better suggestions? One needs to keep the submodule in sync; may be okay, updating the demo is a manual process already anyway.
The site is currently in static HTML hosted out of the content/ directory.
Any pre-generated/rendered content or documentation should be added to additional folders in the root of this repo.
Currently, master and asf-site should be kept in sync. The asf-site branch gets published to an Apache HTTPD static hosting environment run by the Apache infrastructure team.
This website repository contains the main project repository as a git submodule, in order to build its demo without duplicating the code.
Run git submodule init && git submodule update to pull in the submodule.
Run yarn install to install development dependencies.
Run yarn build to build the demo code (it will overwrite content/demo).
We also use the Milestones for this repo on GitHub to track our quarterly board reports.
Web site issues and PRs are still more than welcome, though!
Apache License 2.0 (obviously...:wink:)