[#2][Release] First Release

[Release] First Release

Author: x-0o0

.github/workflows/deploy.yml

@@ -0,0 +1,37 @@
+name: 사이트 배포
+
+on:
+  push:
+    branches: [ "main" ]
+  
+  # Action 탭에서 워크플로우 수동 실행 허용
+  workflow_dispatch:
+
+jobs:
+  build:
+    permissions:
+      id-token: write
+      contents: read
+      deployments: write
+      pages: write
+    
+    runs-on: macos-latest
+    
+    steps:
+      - uses: actions/checkout@v4
+      - uses: swift-actions/setup-swift@v2
+      
+      - name: 스위프트 패키지 실행
+        run: swift run --configuration release
+
+      - name: Pages 설정
+        uses: actions/configure-pages@v5
+
+      - name: Artifact 업로드
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: './Build'
+          
+      - name: 배포
+        id: deployment
+        uses: actions/deploy-pages@v4

Assets/Assets.txt

@@ -0,0 +1 @@
+Place any assets you want copied into the build here.

Assets/images/Images.txt

@@ -0,0 +1 @@
+This is the best place to put images for your build, creating subfolders below here as needed.

Assets/images/discord.svg

@@ -0,0 +1,3 @@
+If you want Ignite to generate pages based on Markdown files, you should place them in here. You can group your content however, you want – category, year, etc – just by placing them into subfolders of Content.
+
+The same path (minus "Content") is used to place your rendered Markdown files in the Build folder, but you can also use the "path" YAML front matter to customize this.

Assets/images/favicon.png

@@ -0,0 +1 @@
+If you need to import some pre-written HTML, you can place files here then bring them into your project using Include("YourFilename.html"). The Include element automatically looks in this Includes folder.