diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml
new file mode 100644
index 000000000..918a4ba13
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug-report.yml
@@ -0,0 +1,29 @@
+name: 🐛 Bug report
+description: Create a bug report
+body:
+ - type: checkboxes
+ attributes:
+ label: Are you certain it's a bug?
+ description: This issue tracker is only for reporting bugs.
+ options:
+ - label: Yes, it looks like a bug
+ required: true
+ - type: checkboxes
+ attributes:
+ label: Are you sure this is not an issue in Docusaurus?
+ description: If this is a Docusaurus issue, report it at https://github.com/facebook/docusaurus/issues.
+ options:
+ - label: It is not a Docusaurus issue
+ required: true
+ - type: checkboxes
+ attributes:
+ label: Is there an existing issue for this?
+ description: Please search to see if an issue already exists
+ options:
+ - label: I have searched existing issues, it hasn't been reported yet
+ required: true
+ - type: textarea
+ attributes:
+ label: Issue description
+ validations:
+ required: true
\ No newline at end of file
diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml
new file mode 100644
index 000000000..a6e494f81
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature-request.yml
@@ -0,0 +1,21 @@
+name: 🎉 Feature request
+description: Suggest an idea
+body:
+ - type: checkboxes
+ attributes:
+ label: Is there an existing issue for this?
+ description: Please search to see if an issue already exists
+ options:
+ - label: I have searched existing issues, it hasn't been reported yet
+ required: true
+ - type: textarea
+ attributes:
+ label: Use case description
+ description: Describe the problem (use case) that needs to be solved
+ validations:
+ required: true
+ - type: textarea
+ attributes:
+ label: Proposed solution (optional)
+ description: |
+ e.g. propose how the configuration of the new feature could look
\ No newline at end of file
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 000000000..36d7984c5
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,15 @@
+## Description
+
+Describe your PR here.
+
+## Resolved issues
+
+Closes #1
+
+### Before submitting the PR, please take the following into consideration
+- [ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. If you don't have an issue, please create one.
+- [ ] Prefix your PR title with `feat: `, `fix: `, `chore: `, `docs:`, or `refactor:`.
+- [ ] The description should clearly illustrate what problems it solves.
+- [ ] Ensure that the commit messages follow our guidelines.
+- [ ] Resolve merge conflicts (if any).
+- [ ] Make sure that the current branch is upto date with the `master` branch.
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
new file mode 100644
index 000000000..515b8482f
--- /dev/null
+++ b/.github/workflows/publish.yml
@@ -0,0 +1,36 @@
+name: publish
+
+on:
+ push:
+ branches: [ master ]
+ workflow_dispatch:
+
+jobs:
+ publish:
+ runs-on: ubuntu-latest
+
+ steps:
+ - name: Check out repository
+ uses: actions/checkout@v4
+
+ - name: Setup node 18 env
+ uses: actions/setup-node@v4
+ with:
+ node-version: '18'
+ cache: "npm"
+
+ - name: build
+ run: |
+ git config --global url."https://github.com/".insteadOf git://github.com/
+ npm install
+ npm run build
+
+ - name: Publish to OSS
+ uses: tvrcgo/oss-action@master
+ with:
+ key-id: ${{ secrets.OSS_ACCESS_KEY_ID }}
+ key-secret: ${{ secrets.OSS_ACCESS_KEY_SECRET }}
+ region: ${{ secrets.OSS_REGION }}
+ bucket: ${{ secrets.OSS_BUCKET }}
+ assets: |
+ ./build/**:${{ secrets.OSS_TARGET_PATH }}
diff --git a/.github/workflows/pull_preview.yml b/.github/workflows/pull_preview.yml
new file mode 100644
index 000000000..9fe3bd108
--- /dev/null
+++ b/.github/workflows/pull_preview.yml
@@ -0,0 +1,77 @@
+name: pr_test
+
+on:
+ issue_comment:
+ types: [created]
+ workflow_dispatch:
+
+jobs:
+ preview:
+ if: github.event.issue.pull_request
+ runs-on: ubuntu-latest
+
+ steps:
+
+ - name: Check comment command
+ uses: actions-ecosystem/action-regex-match@v2
+ id: regex-match
+ with:
+ text: ${{ github.event.comment.body }}
+ regex: '^/preview$'
+
+ - uses: actions/github-script@v3
+ id: get-pr
+ if: ${{ steps.regex-match.outputs.match != '' }}
+ with:
+ script: |
+ const request = {
+ owner: context.repo.owner,
+ repo: context.repo.repo,
+ pull_number: context.issue.number
+ }
+ core.info(`Getting PR #${request.pull_number} from ${request.owner}/${request.repo}`)
+ try {
+ const result = await github.pulls.get(request)
+ return result.data
+ } catch (err) {
+ core.setFailed(`Request failed with error ${err}`)
+ }
+
+ - name: Check out pull request head
+ if: ${{ steps.regex-match.outputs.match != '' }}
+ uses: actions/checkout@v4
+ with:
+ repository: ${{ fromJSON(steps.get-pr.outputs.result).head.repo.full_name }}
+ ref: ${{ fromJSON(steps.get-pr.outputs.result).head.sha }}
+
+ - name: Setup node 18 env
+ if: ${{ steps.regex-match.outputs.match != '' }}
+ uses: actions/setup-node@v4
+ with:
+ node-version: '18'
+ cache: "npm"
+
+ - name: Build the website
+ if: ${{ steps.regex-match.outputs.match != '' }}
+ run: |
+ git config --global url."https://github.com/".insteadOf git://github.com/
+ npm install
+ PULL_NUM=${{ github.event.issue.number }} npm run build
+
+ - name: Upload to OSS
+ if: ${{ steps.regex-match.outputs.match != '' }}
+ uses: tvrcgo/oss-action@master
+ with:
+ key-id: ${{ secrets.OSS_ACCESS_KEY_ID }}
+ key-secret: ${{ secrets.OSS_ACCESS_KEY_SECRET }}
+ region: ${{ secrets.OSS_REGION }}
+ bucket: ${{ secrets.OSS_BUCKET }}
+ assets: |
+ ./build/**:${{ secrets.OSS_TARGET_PATH }}pull_${{ github.event.issue.number }}/
+
+ - name: Create comment
+ if: ${{ steps.regex-match.outputs.match != '' }}
+ uses: peter-evans/create-or-update-comment@v4
+ with:
+ issue-number: ${{ github.event.issue.number }}
+ body: 🪧The website for this PR is deployed at https://hypercrx.cn${{ secrets.OSS_TARGET_PATH }}pull_${{ github.event.issue.number }}/
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000000000..8e89f19bf
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,23 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+.vscode
+publish.sh
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 000000000..b888f7077
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,129 @@
+# Working by Forking
+Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or just head straight to the command line:
+
+## Clone your fork to your local machine
+```
+git clone git@github.com:USERNAME/FORKED-PROJECT.git
+```
+Keeping Your Fork Up to Date
+While this isn't an absolutely necessary step, if you plan on doing anything more than just a tiny quick fix, you'll want to make sure you keep your fork up to date by tracking the original "upstream" repo that you forked. To do this, you'll need to add a remote:
+
+## Add 'upstream' repo to list of remotes
+```
+git remote add upstream https://github.com/hypertrons/hypercrx-website.git
+```
+
+## Verify the new remote named 'upstream'
+```
+git remote -v
+```
+Whenever you want to update your fork with the latest upstream changes, you'll need to first fetch the upstream repo's branches and latest commits to bring them into your repository:
+
+## Fetch from upstream remote
+```
+git fetch upstream
+```
+
+## View all branches, including those from upstream
+```
+git branch -va
+```
+Now, checkout your own master branch and merge the upstream repo's master branch:
+
+## Checkout your master branch and merge upstream
+```
+git checkout master
+git merge upstream/master
+```
+If there are no unique commits on the local master branch, git will simply perform a fast-forward. However, if you have been making changes on master (in the vast majority of cases you probably shouldn't be - see the next section), you may have to deal with conflicts. When doing so, be careful to respect the changes made upstream.
+
+Now, your local master branch is up-to-date with everything modified upstream.
+
+**Create a Branch** (doing your work)
+Whenever you begin work on a new feature or bugfix, it's important that you create a new branch. Not only is it proper git workflow, but it also keeps your changes organized and separated from the master branch so that you can easily submit and manage multiple pull requests for every task you complete.
+
+To create a new branch and start working on it, perform the following flow.
+
+## Checkout the master branch - you want your new branch to come from master
+```
+git checkout master
+```
+
+## Create a new branch (give your branch its own simple informative name)
+For enhancements use `feature/your_username/issue#` or `feature/your_username/name_of_feature`
+
+For bugs use `bug/your_username/issue#` or `bug/your_username/name_of_bug`
+
+```
+git branch feature/jdoe/567
+```
+
+## Switch to your new branch
+```
+git checkout feature/jdoe/567
+```
+Now, go to town hacking away and making whatever changes you want to.
+
+## Submitting your changes (a Pull Request)
+Prior to submitting your pull request, you might want to do a few things to clean up your branch and make it as simple as possible for the original repo's maintainer to test, accept, and merge your work.
+
+In the time that you've been working on your changes, if any commits have been made to the upstream master branch, you will need to rebase your development branch so that merging it will be a simple fast-forward that won't require any conflict resolution work.
+
+## Fetch upstream master and merge with your repo's master branch
+```
+git fetch upstream
+git checkout master
+git merge upstream/master
+```
+
+## If there were any new commits, rebase your development branch
+```
+git checkout feature/jdoe/567
+git rebase master
+```
+Now, it may be desirable to squash some of your smaller commits down into a small number of larger more cohesive commits. You can do this with an interactive rebase:
+
+## Rebase all commits on your development branch
+```
+git checkout
+git rebase -i master
+```
+This will open up a text editor where you can specify which commits to squash.
+
+## Signing-off on Commits (Developer Certificate of Origin)
+
+To contribute to this project, you must agree to the Developer Certificate of
+Origin (DCO) for each commit you make. The DCO is a simple statement that you,
+as a contributor, have the legal right to make the contribution.
+
+See the [DCO](https://developercertificate.org) file for the full text of what you must agree to
+and how it works [here](https://github.com/probot/dco#how-it-works).
+To signify that you agree to the DCO for contributions, you simply add a line to each of your
+git commit messages:
+
+```
+Signed-off-by: Jane Smith
+```
+
+In most cases, you can add this signoff to your commit automatically with the
+`-s` or `--signoff` flag to `git commit`. You must use your real name and a reachable email
+address (sorry, no pseudonyms or anonymous contributions). An example of signing off on a commit:
+```
+$ commit -s -m “my commit message w/signoff”
+```
+
+To ensure all your commits are signed, you may choose to add this alias to your global ```.gitconfig```:
+
+*~/.gitconfig*
+```
+[alias]
+ amend = commit -s --amend
+ cm = commit -s -m
+ commit = commit -s
+```
+
+## Mermaid Diagrams
+If you are adding a new Mermaid diagram, you can use the [getting-started](https://mermaid.js.org/intro/getting-started.html) documentation to get started. You can also use the [Mermaid Live Editor](https://mermaid-js.github.io/mermaid-live-editor/) to create and preview your diagrams.
+
+## Submitting
+Once you've committed and pushed all of your changes to GitHub, go to the page for your fork on GitHub, select your development branch, and click the pull request button. If you need to make any adjustments to your pull request, just push the updates to GitHub. Your pull request will automatically track the changes on your development branch and update.
diff --git a/LICENSE b/LICENSE
new file mode 100644
index 000000000..f49a4e16e
--- /dev/null
+++ b/LICENSE
@@ -0,0 +1,201 @@
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
\ No newline at end of file
diff --git a/README.md b/README.md
new file mode 100644
index 000000000..2f1a91b4a
--- /dev/null
+++ b/README.md
@@ -0,0 +1,49 @@
+