feat: init code

Author: qinluhe

.eslintignore

@@ -0,0 +1,3 @@
+.next
+node_modules
+next.config.js

.eslintrc.js

@@ -0,0 +1,25 @@
+module.exports = {
+  extends: ['next', 'eslint:recommended', 'plugin:@typescript-eslint/recommended'],
+  parser: '@typescript-eslint/parser',
+  plugins: ['@typescript-eslint'],
+
+  rules: {
+    'no-duplicate-case': 'error',
+    'no-duplicate-imports': 'error',
+    '@next/next/no-img-element': 'off',
+    '@typescript-eslint/no-empty-function': 'error',
+    'padding-line-between-statements': [
+      'warn',
+      { blankLine: 'always', prev: ['const', 'let', 'var'], next: '*' },
+      {
+        blankLine: 'any',
+        prev: ['const', 'let', 'var'],
+        next: ['const', 'let', 'var'],
+      },
+      { blankLine: 'always', prev: 'import', next: '*' },
+      { blankLine: 'any', prev: 'import', next: 'import' },
+      { blankLine: 'always', prev: 'block-like', next: '*' },
+      { blankLine: 'always', prev: 'block', next: '*' },
+    ],
+  },
+};

.github/FUNDING.yml

@@ -0,0 +1,2 @@
+ko_fi: appflowy
+

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,49 @@
+name: Bug Report
+description: Create a bug report to help us improve
+title: "[Bug] "
+body:
+  - type: textarea
+    id: desc
+    attributes:
+      label: Bug Description
+      description: A clear and concise description of what the bug is
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: How to Reproduce
+      description: What steps can we take to reproduce this behavior?
+    validations:
+      required: true
+  - type: textarea
+    id: expected
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: Operating System
+      description: What OS are you seeing this bug on?
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: AppFlowy Version(s)
+      description: What version(s) of AppFlowy do you see this bug on?
+    validations:
+      required: true
+  - type: textarea
+    id: screenshots
+    attributes:
+      label: Screenshots
+      description: If applicable, please add screenshots to help explain your problem
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Add any additonal context about the problem here

.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,25 @@
+name: Feature Request
+description: Suggest an idea for AppFlowy
+title: "[FR] "
+body:
+  - type: textarea
+    id: desc
+    attributes:
+      label: Description
+      description: Describe your suggested feature and the main use cases
+    validations:
+      required: true
+      
+  - type: textarea
+    id: users
+    attributes:
+      label: Impact
+      description: What types of users can benefit from using the suggested feature?
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Add any additonal context about the feature here

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,27 @@
+<!---
+Thank you for submitting a pull request to AppFlowy. The team will dedicate their best efforts to reviewing and approving your pull request. If you have any questions about the project or feedback for us, please join our [Discord](https://discord.gg/wdjWUXXhtw).
+-->
+
+<!---
+If your pull request adds a new feature, please drag and drop a video into this section to showcase what you've done! If not, you may delete this section.
+-->
+
+### Feature Preview
+
+<!---
+List at least one issue here that this PR addresses. If it fixes the issue, please use the [fixes](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) keyword to close the issue. For example:
+fixes https://github.com/AppFlowy-IO/AppFlowy/pull/2106
+-->
+
+---
+
+<!---
+Before you mark this PR ready for review, run through this checklist!
+-->
+
+#### PR Checklist
+
+- [ ] My code adheres to the [AppFlowy Style Guide](https://appflowy.gitbook.io/docs/essential-documentation/contribute-to-appflowy/software-contributions/submitting-code/style-guides)
+- [ ] I've listed at least one issue that this PR fixes in the description above.
+- [ ] I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
+- [ ] All existing tests are passing.

.github/workflows/commit_lint.yml

@@ -0,0 +1,12 @@
+name: Commit messages lint
+on: [pull_request, push]
+
+jobs:
+  commitlint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
+      - uses: wagoid/commitlint-github-action@v4
+

.github/workflows/deploy_dev.yml

@@ -0,0 +1,36 @@
+name: Auto Deploy to Development
+
+on:
+  push:
+    branches:
+      - develop
+      - main
+
+jobs:
+  deploy-develop:
+    runs-on: ubuntu-latest
+
+    env:
+      SSH_TARGET: 54.206.53.213
+      NODE_ENV: production
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Get current branch
+        id: branch
+        run: echo "::set-output name=branch::$(echo $GITHUB_REF | awk 'BEGIN{FS="/"} {print $3}')"
+
+      - name: Set up SSH
+        run: |
+          mkdir -p ~/.ssh
+          echo "${{ secrets.SSH_KEY_DEV }}" | openssl rsa -out ~/.ssh/id_rsa.pem  # set the SSH key into the ~/.ssh/id_rsa file
+          chmod 600 ~/.ssh/id_rsa.pem  # set the permissions
+          ssh-keyscan "$SSH_TARGET" >> ~/.ssh/known_hosts  # add the host to the known_hosts file
+          chmod 644 ~/.ssh/known_hosts  # set the permissions
+
+      - name: Deploy to EC2
+        run: |
+          ssh -o StrictHostKeyChecking=no -i ~/.ssh/id_rsa.pem admin@$SSH_TARGET "cd space/AppFlowy-Website && git fetch && git reset --hard origin/${{ steps.branch.outputs.branch }} && pnpm install && pnpm run build && node run-script.js" || { echo "Failed to execute the command"; exit 1; }
+        

.github/workflows/deploy_prod.yml

@@ -0,0 +1,36 @@
+name: Manual Deploy to Production
+
+on:
+  workflow_dispatch:
+    inputs:
+      branch:
+        description: 'Branch to deploy'
+        required: true
+        default: 'main'
+        options:
+          main:
+            description: 'Deploy the main branch'
+
+jobs:
+  deploy-main:
+    runs-on: ubuntu-latest
+
+    env:
+      SSH_TARGET: 54.206.53.213
+      NODE_ENV: production
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up SSH
+        run: |
+          mkdir -p ~/.ssh
+          echo "${{ secrets.SSH_KEY }}" | openssl rsa -out ~/.ssh/id_rsa.pem  # set the SSH key into the ~/.ssh/id_rsa file
+          chmod 600 ~/.ssh/id_rsa.pem  # set the permissions
+          ssh-keyscan "$SSH_TARGET" >> ~/.ssh/known_hosts  # add the host to the known_hosts file
+          chmod 644 ~/.ssh/known_hosts  # set the permissions
+
+      - name: Deploy to EC2 (Main)
+        run: |
+          ssh -o StrictHostKeyChecking=no -i ~/.ssh/id_rsa.pem admin@$SSH_TARGET "cd space/AppFlowy-Website && git fetch && git reset --hard origin/${{ inputs.branch }} && pnpm install && pnpm run build && node run-script.js" || { echo "Failed to execute the command"; exit 1; }

.github/workflows/test.yml

@@ -0,0 +1,34 @@
+name: Test
+on: [pull_request]
+
+env:
+  NODE_VERSION: "18.16.0"
+  PNPM_VERSION: "8.5.0"
+
+concurrency:
+  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout source code
+        uses: actions/checkout@v2
+      - name: setup node
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ env.NODE_VERSION }}
+      - name: install dependencies
+        run: |
+          npm install -g pnpm@${{ env.PNPM_VERSION }}
+          pnpm install
+          pnpm run build
+      - name: run lint
+        run: |
+          pnpm run lint
+      - name: run tests
+        run: |
+          pnpm run start & sleep 10 && pnpm run test:headless
+

.gitignore

@@ -33,3 +33,7 @@ yarn-error.log*
 # typescript
 *.tsbuildinfo
 next-env.d.ts
+
+cypress/videos
+
+**/*.log

.idea/.gitignore

@@ -0,0 +1,3 @@
+pnpm-lock.yaml
+node_modules
+.next

.idea/appflowy-website.iml

@@ -1,4 +1,5 @@
-This is a [Next.js](https://nextjs.org/) project bootstrapped with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
+This is a [Next.js](https://nextjs.org/) project bootstrapped
+with [`create-next-app`](https://github.com/vercel/next.js/tree/canary/packages/create-next-app).
 
 ## Getting Started
 
@@ -16,19 +17,39 @@ Open [http://localhost:3000](http://localhost:3000) with your browser to see the
 
 You can start editing the page by modifying `app/page.tsx`. The page auto-updates as you edit the file.
 
-This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and load Inter, a custom Google Font.
+This project uses [`next/font`](https://nextjs.org/docs/basic-features/font-optimization) to automatically optimize and
+load Inter, a custom Google Font.
 
-## Learn More
+## Deploy
 
-To learn more about Next.js, take a look at the following resources:
+### Automatic Testing Environment Deployment
 
-- [Next.js Documentation](https://nextjs.org/docs) - learn about Next.js features and API.
-- [Learn Next.js](https://nextjs.org/learn) - an interactive Next.js tutorial.
+We have set up an automated deployment process for the testing environment. When code is merged into either the `main`
+or `develop` branch, the system automatically deploys the changes to the testing environment. You can find the
+deployment workflow configuration in `.github/workflows/deploy_dev.yml`.
 
-You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome!
+### Manual Production Environment Deployment
 
-## Deploy on Vercel
+To deploy changes to the production environment, follow these steps:
 
-The easiest way to deploy your Next.js app is to use the [Vercel Platform](https://vercel.com/new?utm_medium=default-template&filter=next.js&utm_source=create-next-app&utm_campaign=create-next-app-readme) from the creators of Next.js.
+1. Visit the project's GitHub page.
+2. Navigate to the "Actions" tab.
+3. Click on "Manual Deploy to Production."
+4. Select "Run workflow" to initiate a manual deployment to the production environment.
 
-Check out our [Next.js deployment documentation](https://nextjs.org/docs/deployment) for more details.
+## Testing
+
+Our testing framework of choice is Cypress. Comprehensive testing information will be provided in this section as the
+project progresses.
+
+```bash
+pnpm run build
+pnpm run start
+
+pnpm run test
+# or
+pnpm run test:headless
+```
+
+Feel free to update this README with more details as the project evolves. If you have any questions or need further
+assistance, please don't hesitate to reach out. Happy coding!