initialize

Author: OllieJT

.changeset/README.md

@@ -0,0 +1,8 @@
+# Changesets
+
+Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works
+with multi-package repos, or single-package repos to help you version and publish your code. You can
+find the full documentation for it [in our repository](https://github.com/changesets/changesets)
+
+We have a quick list of common questions to get you started engaging with this project in
+[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md)

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+	"$schema": "https://unpkg.com/@changesets/config@2.0.0/schema.json",
+	"changelog": "@changesets/cli/changelog",
+	"baseBranch": "main",
+	"commit": false,
+	"fixed": [],
+	"linked": [],
+	"access": "public",
+	"updateInternalDependencies": "patch",
+	"ignore": ["@forge/docs"]
+}

.github/workflows/release.yml

@@ -0,0 +1,44 @@
+name: Release
+
+on:
+  push:
+    branches:
+      - main
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout Repo
+        uses: actions/checkout@v4
+
+      - name: Setup pnpm 8
+        uses: pnpm/action-setup@v3
+        with:
+          version: 8
+
+      - name: Setup Node.js 20.x
+        uses: actions/setup-node@v4
+        with:
+          node-version: 20.x
+
+      - name: Install Dependencies
+        run: pnpm i
+
+      - name: Create Release Pull Request or Publish to npm
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          # This expects you to have a script called release which does a build for your packages and calls changeset publish
+          publish: pnpm release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Send a Slack notification if a publish happens
+        if: steps.changesets.outputs.published == 'true'
+        # You can do something when a publish happens.
+        run: my-slack-bot send-notification --message "A new version of ${GITHUB_REPOSITORY} was published!"

.gitignore

@@ -0,0 +1,13 @@
+.DS_Store
+node_modules
+.turbo
+*.log
+.next
+dist
+dist-ssr
+*.local
+.env
+.cache
+server/dist
+public/dist
+.turbo

.npmrc

@@ -0,0 +1 @@
+auto-install-peers = true

.vscode/extensions.json

@@ -0,0 +1,17 @@
+{
+	"recommendations": [
+		// Tailwind CSS - Intellisense
+		"bradlc.vscode-tailwindcss",
+
+		// Biome - Code Linting + Formatting
+		"biomejs.biome",
+
+		// Astro - Syntax Highlighting
+		"astro-build.astro-vscode",
+
+
+		// MDX - JSX in markdown
+		"unifiedjs.vscode-mdx"
+	],
+	"unwantedRecommendations": []
+}

.vscode/launch.json

@@ -0,0 +1,11 @@
+{
+	"version": "0.2.0",
+	"configurations": [
+		{
+			"command": "./apps/docs/node_modules/.bin/astro dev",
+			"name": "Development server",
+			"request": "launch",
+			"type": "node-terminal"
+		}
+	]
+}

.vscode/settings.json

@@ -0,0 +1,31 @@
+{
+	// Triggers biome formatting on save.
+	"[json][typescript][javascript][tsx][html][css][postcss][sql]": {
+		"editor.codeActionsOnSave": {
+			"source.fixAll.ts": "explicit",
+			"source.organizeImports": "explicit"
+		},
+		"editor.defaultFormatter": "biomejs.biome"
+	},
+
+	// Enables tailwind intellisense in typescript
+	"tailwindCSS.experimental.classRegex": [
+		"class:\\s*?[\"'`]([^\"'`]*).*?,",
+		"className:\\s*?[\"'`]([^\"'`]*).*?,",
+		"([\"'`][^\"'`]*.*?[\"'`])",
+		"[\"'`]([^\"'`]*).*?[\"'`]"
+	],
+	"tailwindCSS.experimental.configFile": "packages/ui/src/styles/globals.css",
+	"files.associations": {
+		"*.css": "tailwindcss",
+		"CONTRIBUTING": "md"
+	},
+	"editor.quickSuggestions": {
+		"strings": "on"
+	},
+
+	// Excludes generated files in explorer
+	"files.watcherExclude": {
+		"**/node_modules": true
+	}
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,72 @@
+# DH Forge Community Code of Conduct
+
+## Our Pledge
+
+We, as members, contributors, and leaders of the DH Forge community, pledge to make participation in our project and community a harassment-free, inclusive, and positive experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We aim to foster an environment built on **Kindness**, a commitment to **Assuming Good Intent**, and a spirit of **Collaboration**. We believe these values honor the shared storytelling and inclusive experiences that **Daggerheart™** itself represents, and we strive to uphold them in all our interactions.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment include:
+
+- Demonstrating empathy and **kindness** toward other people.
+- Being respectful of differing opinions, viewpoints, and experiences.
+- Giving and gracefully accepting **constructive** feedback.
+- **Assuming good intent** in others' actions and words, while being open to clarification.
+- Focusing on what is best for the overall community and the DHFS project.
+- Showing appreciation for the voluntary efforts of others – **nobody is paid to be here, so please be appreciative of the community support you receive.**
+- Helping others learn – **when looking for support, share your context and learnings so others can learn from your experience.**
+- Using welcoming and **inclusive** language.
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or advances of any kind.
+- Trolling, insulting or derogatory comments, and personal or political attacks.
+- Public or private harassment. This includes, but is not limited to, unwelcome comments or actions related to a person’s identity or beliefs.
+- Publishing others' private information, such as a physical or email address, without their explicit permission ("doxing").
+- Other conduct which could reasonably be considered inappropriate in a professional or community setting.
+
+**A Note on Harassment & Inclusivity:** DH Forge is committed to being a safe space. We take harassment and exclusionary behaviour seriously. Unacceptable behaviour, particularly harassment targeting community members, will not be tolerated, **even if it occurs on third-party platforms outside of official DH Forge spaces**, if it impacts a participant's ability to engage safely and productively with the DH Forge community.
+
+## Scope
+
+This Code of Conduct applies within all official DH Forge project spaces, which currently include:
+
+- The [DHForge GitHub Organization](https://www.google.com/search?q=https://github.com/DH-Forge) (including Issues, Pull Requests, and Discussions).
+- Any official DH Forge communication platforms (such as a future Discord server).
+
+It also applies when an individual is representing the DH Forge community in public spaces.
+
+## Reporting Violations
+
+If you witness or experience unacceptable behavior, or have any other concerns, please report it by contacting **Ollie at ollie@dhfs.dev**.
+
+All complaints will be reviewed and investigated promptly and fairly. We are committed to maintaining the confidentiality of the reporter where possible, though full anonymity cannot always be guaranteed, especially if direct action involving the reporter is necessary.
+
+Your report should ideally include:
+
+- Your contact information (and your GitHub profile if relevant).
+- The name/handle(s) of the individual(s) involved.
+- A description of the incident.
+- A link to the specific comment/conversation/log, or a screenshot if possible.
+- The approximate time and date.
+- Any other context or witnesses.
+- Please state if you wish for your report to remain anonymous, and we will do our best to honor that request within the bounds of a fair investigation.
+
+## Enforcement
+
+Project maintainers (initially the BDFL, Ollie, until a governing body is formed) are responsible for clarifying and enforcing our standards and will take appropriate and fair corrective action in response to any behavior they deem inappropriate, threatening, offensive, or harmful.
+
+Enforcement actions may include, but are not limited to:
+
+- A private warning.
+- Deletion or moderation of comments or other contributions.
+- A temporary ban from one or all DH Forge community spaces.
+- A permanent ban from one or all DH Forge community spaces.
+
+We understand that DH Forge is a volunteer-run project with limited facilities. While our priority is to maintain a safe space for all participants, we will address issues to the best of our abilities within these constraints. We strive for fairness but may not always be able to provide solutions that satisfy everyone.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).