initial setting

.circleci/config.yml

@@ -0,0 +1,45 @@
+# This config was automatically generated from your source code
+# Stacks detected: cicd:github-actions:.github/workflows,deps:node:.
+version: 2.1
+orbs:
+  node: circleci/node@5
+jobs:
+  build-node:
+    # Build node project
+    executor: node/default
+    steps:
+      - checkout
+      - node/install-packages:
+          cache-path: ~/project/node_modules
+          override-ci-command: npm install
+      - run:
+          command: npm run build
+      - run:
+          name: Create the ~/artifacts directory if it doesn't exist
+          command: mkdir -p ~/artifacts
+      # Copy output to artifacts dir
+      - run:
+          name: Copy artifacts
+          command: cp -R build dist public .output .next .docusaurus ~/artifacts 2>/dev/null || true
+      - store_artifacts:
+          path: ~/artifacts
+          destination: node-build
+  deploy:
+    # This is an example deploy job, not actually used by the workflow
+    docker:
+      - image: cimg/base:stable
+    steps:
+      # Replace this with steps to deploy to users
+      - run:
+          name: deploy
+          command: "#e.g. ./deploy.sh"
+      - run:
+          name: found github actions config
+          command: ":"
+workflows:
+  build:
+    jobs:
+      - build-node
+    # - deploy:
+    #     requires:
+    #       - build-node

.editorconfig

@@ -0,0 +1,4 @@
+root = true
+
+[*.tsx]
+indent_style = space

.eslintignore

@@ -0,0 +1 @@
+.eslintrc.cjs

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @ubinquitous @5ewon @jyh071116

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,38 @@
+Contributor Covenant Code of Conduct
+Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+    Using welcoming and inclusive language
+    Being respectful of differing viewpoints and experiences
+    Gracefully accepting constructive criticism
+    Focusing on what is best for the community
+    Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+    The use of sexualized language or imagery and unwelcome sexual attention or advances
+    Trolling, insulting/derogatory comments, and personal or political attacks
+    Public or private harassment
+    Publishing others' private information, such as a physical or electronic address, without explicit permission
+    Other conduct which could reasonably be considered inappropriate in a professional setting
+
+Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+Attribution
+
+This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at http://contributor-covenant.org/version/1/4

.github/CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# 부마위키에 기여하기
+
+우리는 커뮤니티의 모든 사람의 기여를 환영합니다.<br/>
+이 레포지토리는 다양한 나라의 언어로 이루어지며, 한국어를 중심으로 이루어집니다.
+
+> BSM의 모든 기여자는 우리의 행동 강령을 준수해야 합니다.
+> <br/>어떤 행동이 허용되고 허용되지 않는지 이해하려면 [전체 내용](./CODE_OF_CONDUCT.md)를 읽어보시기 바랍니다 .
+
+## 1. 이슈
+
+다음을 통해 BSM에 기여할 수 있습니다 :
+
+- [버그 신고하기](https://github.com/Team-INSERT/bssm-frontend/issues/new/choose)
+- [새로운 기능 요청](https://github.com/Team-INSERT/bssm-frontend/issues/issues/new/choose)
+- [이미 있는 이슈를 보고](https://github.com/Team-INSERT/bssm-frontend/issues/issues) 수정해야 할 사항을 확인하세요.
+
+## 2. Pull Requests
+
+> [PR 시작하기](https://github.com/Team-INSERT/bssm-frontend/compare) <br/>
+
+나만의 PR을 올릴 수 있습니다. PR 제목은 다음 형식과 일치해야 합니다.
+
+```
+<commit keyword>(template scope): <description>
+
+ex) feat(calendar): 바 형식으로 조회하는 기능 추가
+```
+
+> 우리는 모든 PR을 메인에 병합하기 때문에 기록의 커밋 수나 스타일에 신경 쓰지 않습니다.<br/>
+> 편안하다고 느끼는 스타일로 자유롭게 커밋해주세요.
+
+### commit keyword
+
+**유형은 다음 중 하나여야 합니다:**
+
+src 내 메인 로직을 포함하는 코드를 수정한 경우 :
+
+- feat - 새로운 기능 추가
+- fix - 새로운 기능을 추가하지 않은 수정사항
+
+src 내 메인 로직을 포함하는 코드를 수정하지 않은 경우 :
+
+- test - 테스트 코드를 작성하거나 변경한 경우
+
+그 외 :
+
+- chore - 기타 모든 것 ( 주석 추가 등등... )
+
+### 3. etc
+
+코드를 작성할 때 부마위키가 추구하는 구조 자체를 건드리는 것은 유쾌하지 않습니다.  
+만약 더욱 가독성이 좋은 디렉터리 구조를 발견하셨다면 이슈로 제보해주세요.

.github/ISSUE_TEMPLATE/bug.yml

@@ -0,0 +1,17 @@
+name: "Bug"
+description: "🤬"
+labels: 버그
+body:
+  - type: textarea
+    attributes:
+      label: Describe
+      description: |
+        버그에 대해서 설명해주세요!
+      placeholder: |
+        헤더가 깨지는 버그가 발생해요
+
+  - type: textarea
+    attributes:
+      label: Additional
+      description: |
+        추가로 해주실 말씀이 있나요?

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,24 @@
+name: "Feature"
+description: "추가할 일이 있으신가요? 📗"
+body:
+  - type: textarea
+    attributes:
+      label: Describe
+      description: |
+        추가할 일에 관한 설명
+      placeholder: |
+        요구사항을 작성해주세요
+
+  - type: textarea
+    attributes:
+      label: Work
+      description: |
+        [작업내용] 무슨 작업을 하셨나요?
+      placeholder: |
+        ~~이런 작업을 했습니다.
+
+  - type: textarea
+    attributes:
+      label: Additional
+      description: |
+        추가로 해주실 말씀이 있나요?

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,9 @@
+<!-- reviewers와 assignee는 설정하셨는지, label을 설정했는지 확인해주세요! -->
+
+## Issue Number
+
+## What
+
+## How
+
+## ScreenShot

.github/labeler.yml

@@ -0,0 +1,43 @@
+# labeler "full" schema
+
+# enable labeler on issues, prs, or both.
+enable:
+  issues: false
+  prs: true
+
+comments:
+  issues: |
+    Thanks for opening this issue!
+    I have applied any labels matching special text in your title and description.
+
+    Please review the labels and make any necessary changes.
+
+# Labels is an object where:
+# - keys are labels
+# - values are objects of { include: [ pattern ], exclude: [ pattern ] }
+#    - pattern must be a valid regex, and is applied globally to
+#      title + description of issues and/or prs (see enabled config above)
+#    - 'include' patterns will associate a label if any of these patterns match
+#    - 'exclude' patterns will ignore this label if any of these patterns match
+labels:
+  "fix":
+    include:
+      - '\bfix\b'
+  "refactor":
+    include:
+      - '\brefactor\b'
+  "docs":
+    include:
+      - '\bdocs\b'
+  "chore":
+    include:
+      - '\bchore\b'
+  "feat":
+    include:
+      - '\bfeat\b'
+  "test":
+    include:
+      - '\btest\b'
+  "ci":
+    include:
+      - '\bci\b'

.github/workflows/labeler.yml

@@ -0,0 +1,14 @@
+name: Auto Labeler
+on:
+  pull_request_target:
+    types: [opened]
+
+jobs:
+  labeler:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check Labels
+        id: labeler
+        uses: jimschubert/labeler-action@v2
+        with:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}

.gitignore

@@ -0,0 +1,40 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# Dependencies
+node_modules
+.pnp
+.pnp.js
+
+# Local env files
+.env
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# Testing
+coverage
+
+# Turbo
+.turbo
+
+# Vercel
+.vercel
+
+# Build Outputs
+.next/
+out/
+build
+dist
+
+
+# Debug
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+
+# Misc
+.DS_Store
+*.pem
+
+.eslintcache

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+pnpm lint

.husky/pre-push

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+pnpm run build

.npmrc

@@ -0,0 +1 @@
+prefer-workspace-packages=true

.nvmrc

@@ -0,0 +1 @@
+21.4.0

.prettierrc

@@ -0,0 +1,11 @@
+{
+  "printWidth": 100,
+  "semi": true,
+  "singleQuote": false,
+  "trailingComma": "all",
+  "tabWidth": 2,
+  "bracketSpacing": true,
+  "endOfLine": "auto",
+  "useTabs": false,
+  "arrowParens": "always"
+}

.vscode/settings.json

@@ -0,0 +1,7 @@
+{
+  "eslint.workingDirectories": [
+    {
+      "mode": "auto"
+    }
+  ]
+}

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Insert
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.