Merge pull request #59 from danbaruka/main

chore(issues): refresh templates and links; add docs + feature reques…

Closes: #31

Author: Ranchhand87

.github/ISSUE_TEMPLATE/config.yml

@@ -1,13 +1,13 @@
 blank_issues_enabled: true
 contact_links:
-  - name: Contributing guidelines
-    url: https://github.com/xxxx-committee-documentation/blob/master/CONTRIBUTING.md
-    about: Some rules & processes we honor.
+  - name: Contribution guidelines
+    url: https://github.com/IntersectMBO/developer-experience/blob/main/CONTRIBUTING.md
+    about: Read the documentation and guidelines before filing an issue.
 
-  - name: Feature ideas
-    url: https://github.com/xxxx-committee-documentation/discussions/categories/ideas
-    about: Maybe someone else had the same or a similar idea already?
+  - name: Ideas and discussions
+    url: https://github.com/IntersectMBO/developer-experience/discussions
+    about: Share ideas and proposals or ask open questions.
 
-  - name: All issues
-    url: https://github.com/xxxx-committee-documentation/issues
-    about: Check whether your issue is not already covered here.
+  - name: Join Intersect
+    url: https://members.intersectmbo.org
+    about: Register with Intersect to access Discord and other community resources.

.github/ISSUE_TEMPLATE/documentation.yml

@@ -0,0 +1,44 @@
+name: Documentation
+description: Report an issue or request with the documentation or website
+labels: ["documentation"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template to request documentation additions, corrections, or link updates.
+
+  - type: input
+    id: page
+    attributes:
+      label: Page or section
+      description: Which page, path, or section needs an update?
+      placeholder: contributor-beginner/docs/tutorial-basics/directive-kickoff.md
+    validations:
+      required: true
+
+  - type: textarea
+    id: issue
+    attributes:
+      label: Issue description
+      description: What is wrong or missing?
+      placeholder: Broken link, outdated content, missing section, formatting, etc.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed change
+      description: How should it be updated? Include copy or links if available.
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checks
+      options:
+        - label: I searched existing issues and discussions
+          required: true
+        - label: This is about documentation (not a feature request or bug)
+          required: true

.github/ISSUE_TEMPLATE/feature_idea.yml

@@ -1,14 +1,15 @@
 name: Feature idea
-description: Idea or request for some feature on the xxx Committee GitBook
-labels: [':thought_balloon: idea']
+description: Propose a feature or improvement for Developer Experience
+labels: ["idea"]
 body:
   - type: markdown
     attributes:
       value: |
-        **Thank you for contributing to our project!** :green_heart:
+        Thank you for contributing to our project.
 
-        Instead of opening this issue, consider [starting a new idea discussion](https://github.com/IntersectMBO/xxxx-committee-documentation/discussions/new?category=ideas).
-        That way, we can discuss & refine your idea together, before we adopt it as a feature into the roadmap.
+        Consider starting a new idea discussion first:
+        https://github.com/IntersectMBO/developer-experience/discussions/new?category=ideas
+        This helps refine the proposal before it becomes a tracked feature.
 
   - type: textarea
     id: why
@@ -24,7 +25,7 @@ body:
     id: what
     attributes:
       label: What
-      description: What is this feature roughly about
+      description: What is this feature roughly about?
       placeholder: |
         For example describe a new API endpoint, a change in messaging formats,
         a new configuration option, ...
@@ -35,7 +36,7 @@ body:
     id: how
     attributes:
       label: How
-      description: How could we realize this feature
+      description: How could we realize this feature?
       placeholder: |
         Which technical solutions, libraries or systems should be used, which
         components need to change, steps how to implement this, ...

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,43 @@
+name: Feature request
+description: Request a new feature or enhancement
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template to propose enhancements to Developer Experience tooling, docs, or workflows.
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem statement
+      description: What problem are you trying to solve?
+      placeholder: Describe the pain point and who it affects.
+    validations:
+      required: true
+
+  - type: textarea
+    id: solution
+    attributes:
+      label: Proposed solution
+      description: How should we solve it? Include alternatives considered.
+    validations:
+      required: true
+
+  - type: textarea
+    id: scope
+    attributes:
+      label: Scope and impact
+      description: Affected areas, risks, and expected outcomes.
+    validations:
+      required: false
+
+  - type: checkboxes
+    id: checks
+    attributes:
+      label: Checks
+      options:
+        - label: I searched existing issues and discussions
+          required: true
+        - label: This is a feature/enhancement request (not a question or doc issue)
+          required: true