docs: rebuild new website content about ASF (#620)

* docs: Add new website content about ASF

* chore: add Apache License headers to team page files

* chore: update license header format in team page files

* docs: corrected references throughout docs to use proper project name and status

* docs: add code review guide for contributors and committers

* docs: update contribution guide and fix links

Author: delei

.github/pull_request_template.md

@@ -22,6 +22,6 @@ Related: #ISSUE
 
 ## Checklist
 
-- [ ] I have read the [Contributor Guide](https://fesod.apache.org/community/contribution).
+- [ ] I have read the [Contributor Guide](https://fesod.apache.org/community/contribution/).
 - [ ] I have written the necessary doc or comment.
 - [ ] I have added the necessary unit tests and all cases have passed.

CONTRIBUTING.md

@@ -1,14 +1,11 @@
 # Contribution Guidelines
 
-Welcome every user and developer in the community to become contributors. Whether it's reporting issues, improving
-documentation, submitting code, or providing technical support, your participation will help make the Apache Fesod (
-Incubating) better.
 
----
+Welcome every user and developer in the community to become contributors. Whether it's reporting issues, improving documentation, submitting code, or providing technical support, your participation will help make it better.
 
 ## Contribution Directions
 
-There are many ways to contribute to Apache Fesod (Incubating):
+There are many ways to contribute to this project:
 
 - Fix typos
 - Fix bugs
@@ -19,237 +16,57 @@ There are many ways to contribute to Apache Fesod (Incubating):
 - Optimize code structure
 - Improve or refine documentation
 
-**Principle**:
+### Principle
 
 - Any pull request that contributes to the improvement of the project should be encouraged.
-- Before contributing a new feature, please propose and discuss it in an `issue` or `discussion`. We will not merge
-  features that have not been discussed and confirmed.
+- Before contributing a new feature, please propose and discuss it in an `issue` or `discussion`. We will not merge features that have not been discussed and confirmed.
 
----
+## Contribution Process
 
-## Contributing Code
+### Find tasks
 
-All improvements can be implemented through Pull Request (PR). Before submitting a Pull Request, please familiarise
-yourself with the following guidelines:
+Find the issue you are interested in! On our GitHub repo issue list, we often publish some issues with the label `good first issue` or `help wanted`. These issues welcome the help of contributors. Among them, `good first issues` tend to have low thresholds and are suitable for beginners.
 
-### Workspace Preparation
+Of course, if you have a good idea, you can also propose it directly on GitHub Discussion or contact with community.
 
-To develop Apache Fesod (Incubating), you need **Maven 3.9 or above** and **JDK (Java Development Kit) 17 or above**.
-However, you must
-use **Java 1.8** compatible language features during compilation to ensure Apache Fesod (Incubating) can run in
-environments with Java
-1.8 or above.
+### Discuss
 
-> You can use tools such as [SDKMAN](https://sdkman.io/) to configure multiple versions of the Java toolchain.
+Please refer to [Issue Feedback](https://fesod.apache.org/community/feedback/) to create an issue or discussion and endeavour to reach consensus.
 
-### Fork the repository
+**Note**: To request an issue, please note that it is not just a "please assign it to me", you need to explain your understanding of the issue, and your design, and if possible, you need to provide your POC code.
 
-Ensure that you have registered a GitHub account and follow the steps below to configure your local development
-environment:
+### Implement
 
-**Fork the repository**: Click the `Fork` button on the Apache Fesod (
-Incubating) [GitHub page](https://github.com/apache/fesod) to copy the project to your GitHub account.
+Implement the change according to the approach agreed upon in the issue.
 
-```bash
-https://github.com/<your-username>/fesod 
-```
+- Only start working on the implementation if there is consensus on the approach (e.g. you are assigned to the ticket)
+- If you are newer, can refer to [Code Contribution](https://fesod.apache.org/community/contribution/contribute-code/) to setup a dev environment.
 
-**Clone Repository**: Run the following command to clone the forked project to your local machine:
+### Review
 
-```bash
-git clone [email protected]:<your-username>/fesod.git
-```
+Create the pull request and work with the reviewer.
 
-**Set Upstream Repository**: Set the official repository as `upstream` for easy synchronization of updates:
+- Make sure no unrelated or unnecessary reformatting changes are included.
+- After submitting the PR, the CI process will be triggered. Please make sure that it has passed the CI checks.
+- Please ensure that the test passing.
+- Please don't resolve conversation.
 
-```bash
-git remote add upstream [email protected]:apahce/fesod.git
-git remote set-url --push upstream no-pushing
-```
+### Merge
 
-Running `git remote -v` can verify if the configuration is correct.
+- A committer of project checks if the contribution fulfills the requirements and merges the code to the codebase.
 
-### Branch definition
+## Contribution Code
 
-In Apache Fesod (Incubating), all contributions should be based on the `main` development branch. Additionally, there
-are the following branch types:
-
-- **release branches**: Used for version releases (e.g., `1.1.0`, `1.1.1`).
-- **feature branches**: Used for developing major features.
-- **hotfix branches**: Used for fixing critical bugs.
-
-When submitting a PR, please ensure that the changes are based on the `main` branch.
-
-### Commit Rules
-
-#### Commit Message
-
-Please ensure that commit messages are clear and descriptive, use **English**, and do not exceed 100 characters.
-
-The following types of commit messages are allowed and must follow the following format:
-
-- **docs**: Update documentation, e.g., `docs: update README.md`
-- **feature/feat**: New features, e.g., `feature: support for xxx`
-- **bugfix/fix**: Bug fixes, e.g., `fix: fix NPE in the A class`
-- **refactor**: Code refactoring (no functional changes), e.g., `refactor: optimise data processing logic`
-- **style**: Code formatting, e.g., `style: update code style`
-- **test**: Adding or improving tests, e.g., `test: add new test cases`
-- **chore**: Changes to the build process or auxiliary tools, e.g., `chore: improve issue template`
-- **dependency**: Modifications to third-party dependency libraries, e.g., `dependency: upgrade poi version to 5.4.1`
-
-Avoid using vague commit messages like:
-
-- ~~fixed issue~~
-- ~~update code~~
-
-For assistance, refer to [How to Write a Git Commit Message](http://chris.beams.io/posts/git-commit/).
-
-#### Commit Content
-
-Each commit should contain complete and reviewable changes, ensuring:
-
-- Avoid committing overly large changes.
-- Each commit content is independent and can pass CI tests.
-
-Also, ensure the correct Git user information is configured when committing:
-
-```bash
-git config --get user.name
-git config --get user.email
-```
-
-### PR Description
-
-To help reviewers quickly understand the content and purpose of the PR, use
-the [pull_request_template](https://github.com/apache/fesod/blob/main/.github/pull_request_template.md). A
-detailed description greatly improves code review efficiency.
-
----
+All improvements can be implemented through Pull Request (PR). Before submitting a Pull Request.
+Please refer to [Code Contribution](https://fesod.apache.org/community/contribution/contribute-code/) for information on how to contribute code.
 
 ## Contribution of Test Cases
 
-Any contribution of test cases is encouraged, especially unit tests. It is recommended to create `XXXTest.java` files in
-the corresponding module's `test` directory, preferably using the `JUnit5` framework.
-
----
+Any contribution of test cases is encouraged, especially unit tests. It is recommended to create `XXXTest.java` files in the corresponding module's `test` directory, preferably using the `JUnit5` framework.
 
 ## Contribution Document
 
-Documentation is an important component of the Apache Fesod (Incubating) official website and serves as a vital bridge
-between the
-project and the community.The Apache Fesod (Incubating) official website is built
-using [Docusaurus](https://docusaurus.io/), and the
-documentation is maintained in the [website](https://github.com/apache/fesod/tree/main/website) directory.
-
-### Requirements
-
-- [Node.js](https://nodejs.org/en/download/) version 18.0 or above (which can be checked by running `node -v`). You can
-  use [nvm](https://github.com/nvm-sh/nvm) for managing multiple Node versions on a single machine installed.
-- When installing Node.js, you are recommended to check all checkboxes related to dependencies.
-
-### Directory Structure Description
-
-Docusaurus supports I18n. The main documentation directory structure that needs to be maintained is as follows:
-
-```bash
-.
-├── community      # Community(English)
-├── docs           # Documentation(English)
-└── i18n           # I18n
-    └── zh-cn
-        ├── docusaurus-plugin-content-docs
-        │   └── current   # Documentation(Simplified Chinese)
-        └── docusaurus-plugin-content-docs-community
-            └── current   # Community(Simplified Chinese)
-```
-
-The directory structure for single-language documents is as follows:
-
-```bash
-.
-├── quickstart     # 1. Quick Start
-├── read           # 2. Read
-├── write          # 3. Write
-├── fill           # 4. Fill
-├── community      # 5. Community
-└── help           # 6. FAQ
-```
-
-### Documentation Writing Guidelines
-
-- Use file paths with the `.md` extension
-
-```markdown
-[Example](docs/quickstart/example.md)
-```
-
-- Use paths relative to the docs/ directory
-
-```markdown
-[Example](docs/quickstart/example.md)
-```
-
-- Image files must be stored in the `static/img` directory and referenced using relative directory paths.
-
-```markdown
-[img](/img/docs/fill/listFill_file.png)
-```
-
-### Preview and generate static files
-
-Enter the `website` directory and execute the command
-
-#### Installation
-
-```bash
-yarn install
-```
-
-#### Local Development
-
-```bash
-# English
-yarn start
-
-# Simplified Chinese
-yarn start --locale zh-cn
-```
-
-This command starts a local development server and opens up a browser window. Most changes are reflected live without
-having to restart the server.
-
-> Only one language version can be run at a time.
-
-#### Build(Optional)
-
-```bash
-yarn build
-```
-
-This command generates static content into the `build` directory and can be served using any static contents hosting
-service.
-
-### Document Format Inspection
-
-Apache Fesod (Incubating) uses [markdownlint-cli2](https://github.com/DavidAnson/markdownlint-cli2) to check document
-formatting. After writing the relevant Markdown articles, you can run the following command locally to pre-check whether
-the Markdown formatting meets the requirements:
-
-```bash
-cd website && yarn
-
-yarn md-lint
-
-# If the documentation is wrong, you can use the following command to attempt an automatic repair.
-yarn md-lint-fix
-```
-
-- For formatting rules for Markdown articles you can refer
-  to: [Markdown-lint-rules](https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md)
-- Markdown format configuration file in the
-  project: [.markdownlint-cli2.jsonc](https://github.com/apache/fesod/blob/main/website/.markdownlint-cli2.jsonc)
-
----
+Documentation is an important component of the project official website and serves as a vital bridge between the project and the community. Please refer to [Docs Contribution](https://fesod.apache.org/community/contribution/contribute-doc/) for information on how to contribute code.
 
 ## Other Ways to Contribute
 
@@ -258,20 +75,5 @@ Apart from directly contributing code, the following ways are also valuable supp
 - Answering other users' questions.
 - Assisting in reviewing others' PRs.
 - Providing improvement suggestions.
-- Writing technical blogs to promote.
+- Writing technical blogs to promote Apache Fesod (Incubating).
 - Sharing project-related knowledge in the community.
-
----
-
-## Code Style
-
-Apache Fesod (Incubating) uses [Spotless](https://github.com/diffplug/spotless) as its code formatting tool. Please
-ensure you run the following command to automatically format your code before submitting:
-
-```bash
-mvn spotless:apply
-```
-
----
-
-Finally, thank you for your support of Apache Fesod (Incubating)!

README.md

@@ -154,7 +154,7 @@ public static void main(String[] args) {
 ### Contributors
 
 Contributors are welcomed to join the Apache Fesod (Incubating). Please
-check [Contributing Guide](https://fesod.apache.org/community/contribution/) about how to contribute to this project.
+check [Contributing Guide](./CONTRIBUTING.md) about how to contribute to this project.
 
 Thank you to all the people who already contributed to the Apache Fesod (Incubating) !
 

website/README.md

@@ -4,7 +4,7 @@ This website is built using [Docusaurus](https://docusaurus.io/), a modern stati
 
 ## Requirements
 
-- [Node.js](https://nodejs.org/en/download/) version 18.0 or above (which can be checked by running `node -v`). You can use [nvm](https://github.com/nvm-sh/nvm) for managing multiple Node versions on a single machine installed.
+- [Node.js](https://nodejs.org/en/download/) version 20.0 or above (which can be checked by running `node -v`). You can use [nvm](https://github.com/nvm-sh/nvm) for managing multiple Node versions on a single machine installed.
 - When installing Node.js, you are recommended to check all checkboxes related to dependencies.
 
 ## Installation

website/blog/2025-09-17-fesod-entered-apache-incubator.md

@@ -0,0 +1,9 @@
+---
+title: "Way to Go: Fesod successfully entered Apache Incubator"
+description: Fesod successfully entered Apache Incubator.
+tags: [announcement]
+---
+
+On September 17th, 2025, the [Fesod](https://github.com/apache/fesod) project achieved a milestone by winning the approval to join the incubator of the [Apache Software Foundation](https://www.apache.org/) (ASF), the world's leading open source software organization. On September 25th, the Fesod project was officially transferred to the Apache Software Foundation.
+
+<!-- truncate -->

website/blog/authors.yml

@@ -0,0 +1,53 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you 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.
+
+jipengfei:
+  name: jipengfei
+  url: https://github.com/jipengfei-jpf
+  image_url: /img/team/198714007.png
+  socials:
+    github: jipengfei-jpf
+zhuangjiaju:
+  name: zhuangjiaju
+  url: https://github.com/zhuangjiaju
+  image_url: /img/team/18475586.png
+  socials:
+    github: zhuangjiaju
+psxjoy:
+  name: psxjoy
+  url: https://github.com/psxjoy
+  image_url: /img/team/10711694.png
+  socials:
+    github: psxjoy
+delei:
+  name: delei
+  url: https://github.com/delei
+  image_url: /img/team/17263766.png
+  socials:
+    github: delei
+alaahong:
+  name: alaahong
+  url: https://github.com/alaahong
+  image_url: /img/team/3264250.png
+  socials:
+    github: alaahong
+tmlx1990:
+  name: tmlx1990
+  url: https://github.com/tmlx1990
+  image_url: /img/team/5753992.png
+  socials:
+    github: tmlx1990