Blog Page Version 1

.github/CODEOWNERS

@@ -0,0 +1,22 @@
+# Configs
+tsconfig.json       @ArsenTech
+*.config.*          @ArsenTech
+components.json     @ArsenTech
+
+# Package Managing
+package.json        @ArsenTech
+package-lock.json   @ArsenTech
+
+# Common Repo Files
+README.md           @ArsenTech
+LICENSE.md          @ArsenTech
+CONTRIBUTING.md     @ArsenTech
+CODE_OF_CONDUCT.md  @ArsenTech
+CHANGELOG.md        @ArsenTech
+.gitignore          @ArsenTech
+
+# Everything in scripts folder
+/scripts/**         @ArsenTech
+
+# All GitHub workflow files
+.github/**          @ArsenTech

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,38 +1,37 @@
 ---
 name: Bug report
 about: Create a report to help us improve
-title: ''
-labels: ''
+title: "[BUG]: "
+labels: 'bug'
 assignees: ''
 
 ---
 
-**Describe the bug**
+## Describe the bug
 A clear and concise description of what the bug is.
 
-**To Reproduce**
-Steps to reproduce the behavior:
+## Steps To Reproduce
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
 4. See error
 
-**Expected behavior**
+## Expected results
 A clear and concise description of what you expected to happen.
 
-**Screenshots**
-If applicable, add screenshots to help explain your problem.
+## Screenshots / Video
+If applicable, add screenshots or video to help explain your problem.
 
-**Desktop (please complete the following information):**
+## Desktop (please complete the following information)
  - OS: [e.g. iOS]
  - Browser [e.g. chrome, safari]
  - Version [e.g. 22]
 
-**Smartphone (please complete the following information):**
+## Smartphone (please complete the following information)
  - Device: [e.g. iPhone6]
  - OS: [e.g. iOS8.1]
  - Browser [e.g. stock browser, safari]
  - Version [e.g. 22]
 
-**Additional context**
-Add any other context about the problem here.
+## Additional context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +1,20 @@
 ---
 name: Feature request
 about: Suggest an idea for this project
-title: ''
-labels: ''
+title: "[NEW FEATURE]: "
+labels: 'new feature request'
 assignees: ''
 
 ---
 
-**Is your feature request related to a problem? Please describe.**
+## Is your feature request related to a problem?
 A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
 
-**Describe the solution you'd like**
+## Proposed solution
 A clear and concise description of what you want to happen.
 
-**Describe alternatives you've considered**
+## Alternative solutions
 A clear and concise description of any alternative solutions or features you've considered.
 
-**Additional context**
-Add any other context or screenshots about the feature request here.
+## Additional context
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,20 +1,18 @@
 # Pull Request | Description
-
 Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
 
-Fixes # [issue]
+It fixes the issue #[ISSUE NUMBER]
 
 ## Type of change
 
+Please delete options that are not relevant.
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 - [ ] This change requires a documentation update
 
 # How Has This Been Tested?
-
 Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
-
 - [ ] Test A
 - [ ] Test B
 
@@ -33,4 +31,4 @@ Please describe the tests that you ran to verify your changes. Provide instructi
 - [ ] My changes generate no new warnings
 - [ ] I have added tests that prove my fix is effective or that my feature works
 - [ ] New and existing unit tests pass locally with my changes
-- [ ] Any dependent changes have been merged and published in downstream modules
+- [ ] Any dependent changes have been merged and published in downstream modules

.gitignore

@@ -40,3 +40,8 @@ yarn-error.log*
 # typescript
 *.tsbuildinfo
 next-env.d.ts
+
+# Ignore generated RSS feed
+public/rss.xml
+public/rss.json
+public/atom.xml

CHANGELOG.md

@@ -0,0 +1,46 @@
+# Change Log
+All notable changes of my blog page will be documented here.
+
+This project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+---
+## [1.0.0] - Unreleased
+### Added
+- Custom blockquote variants: `Note`, `Tip`, `Important`, `Warning`, `Caution`
+- Breadcrumbs and Buttons (Mobile TOC, Comments, Share) all in 1 component
+- Skeleton Loading on every posts
+- Search pages (`/tags/[tag]`, `/categories/[category]`)
+- Scroll To Top Button
+- Progress Bar on Header
+- RSS Feed (`/feed.xml`)
+- Blog page: Interactions (Powered by Giscus)
+- SEO (Title, Description, Metadata, Tags, Sitemap, Search Pages, OpenGraph)
+- Toaster to show the Share Status while Sharing the post (Success or Error)
+### Changed
+- Migrated from `markdown-to-jsx` to MDX
+- Made widgets collapsible (TOC, Categories, etc.)
+- Other UI/UX improvements and bug fixes
+- Made Flair-style Categories widget collapsible
+- Made Table of Contents widget mobile compatible
+- Made Badges Clickable
+- Updated Pagination
+### Removed
+- “Coming Soon” placeholder
+
+## [0.1.1] - 2025-06-14 (Pre-release) 
+### Added
+- Home page widgets: Flair-style Categories, Featured Posts, and Search Bar
+- Blog page: Table of Contents widget and Tag-style Categories, Related Posts section
+- Theme toggle (Light/Dark Mode)
+- Copy Code button in Markdown
+- Christmas theme (active during Dec–Jan; legacy seasonal feature preserved)
+- Markdown Parse by using `markdown-to-jsx`
+- Pagination Support
+### Added Pages
+- 404 Page
+- Landing Page with feature highlights
+- Blog Post page with full Markdown support
+
+## [0.1.0] - 2025-03-28 (Pre-release)
+### Initialized
+- “Coming Soon” placeholder

CODE_OF_CONDUCT.md

@@ -60,7 +60,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[email protected].
+[the contact page](https://arsentech.github.io/#contact).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -83,7 +83,7 @@ behavior was inappropriate. A public apology may be requested.
 ### 2. Warning
 
 **Community Impact**: A violation through a single incident or series
-of actions, Code Disrespect.
+of actions.
 
 **Consequence**: A warning with consequences for continued behavior. No
 interaction with the people involved, including unsolicited interaction with
@@ -114,6 +114,15 @@ the community.
 
 ## Attribution
 
-If You Want to Fork, Give Credit to [ArsenTech](https://arsentech.github.io).
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
 
-### **It's Important to Respect My Code :-)**
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.