Merge pull request #2 from Mahmoudz/copilot/add-community-automation-files

Add community and automation infrastructure

Author: Mahmoudz

.github/ISSUE_TEMPLATE/report-broken-link.md

@@ -0,0 +1,13 @@
+---
+name: Report broken link
+about: Report a broken or outdated resource link
+title: "[broken link] "
+labels: broken-link
+---
+
+Please provide:
+
+- Resource name / URL:
+- Location in repo (e.g., README → Databases):
+- Short note about the problem:
+- Suggested replacement (if any):

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,23 +1,20 @@
-# Pull Request Template for Awesome Topics
+<!-- Use this template for adding or updating resources -->
 
-## PR Type
-- New Topic
-- Edit Topic
-- New Subject
-- Design Enhancement
+## Type of change
+- [ ] Add a resource
+- [ ] Update a resource
+- [ ] Fix a broken link
+- [ ] Reorganize categories
 
 ## Description
-Please provide a concise summary of your changes or the new topic you are introducing.
+- Category:
+- Resource name:
+- URL:
+- One-line description (20–120 chars):
+- Tags (format: category, language, difficulty, license):
 
 ## Checklist
-- [ ] I have read the project's [Contributing Guide](CONTRIBUTING.md).
-- [ ] I have adhered to the project's quality standards.
-- [ ] I have ensured there is no duplicate content in my submission.
-- [ ] I have reviewed all open PRs to confirm no similar contributions are pending.
-- [ ] I have updated the Table of Contents (if necessary).
-
-## Related Issue
-Link any related issues or discussions here.
-
-## Additional Notes
-Add any other context or screenshots about the PR here.
+- [ ] I checked for duplicates.
+- [ ] Description and tags included.
+- [ ] Links tested and working (or note provided).
+- [ ] I followed the project contribution format.

.github/workflows/awesome-lint.yml

@@ -0,0 +1,23 @@
+name: Awesome lint
+
+on:
+  pull_request:
+    branches: [ main ]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+      - name: Install awesome-lint
+        run: |
+          npm install -g awesome-lint
+      - name: Run awesome-lint
+        run: |
+          awesome-lint README.md

.github/workflows/link-check.yml

@@ -0,0 +1,27 @@
+name: Link check
+
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+  schedule:
+    - cron: '0 2 * * 1' # weekly on Monday UTC
+
+jobs:
+  markdown-link-check:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - uses: actions/checkout@v4
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+      - name: Install markdown-link-check
+        run: |
+          npm install -g markdown-link-check
+      - name: Run link checks on markdown files
+        run: |
+          find . -name '*.md' -not -path './node_modules/*' -print0 | xargs -0 -n1 markdown-link-check -q

CODE_OF_CONDUCT.md

@@ -0,0 +1,20 @@
+# Code of Conduct (summary)
+
+This project aims to be welcoming and inclusive. All contributors and visitors are expected to follow these basic guidelines.
+
+Be respectful
+- Be professional and courteous. Assume good intent.
+- Do not engage in harassment, hate speech, or personal attacks.
+
+Be constructive
+- Focus feedback on the content and the facts.
+- When possible, suggest improvements rather than only pointing out problems.
+
+Reporting
+- If you encounter unacceptable behavior, please open an issue with the title "CODE OF CONDUCT report" or contact a repository maintainer via GitHub.
+- Reports will be handled respectfully and promptly by project maintainers or community moderators.
+
+Enforcement
+- Responses may include a request to stop, moderation of content, or removal from the project for serious violations.
+
+This is a short, community-friendly code of conduct. You can replace or expand it with the full Contributor Covenant text if you prefer.

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing to awesome-topics
+
+Thanks for helping improve this curated map for developers — contributions from anyone are welcome.
+
+What to add
+- Ensure the resource is high-quality, relevant to software engineering or developer learning, and not already listed.
+- Proposed entry format (in a single list line):
+  - [Name](URL) — Short neutral description. (tags)
+  - Example: `- [Free Coding Course](https://example.com) — A beginner-friendly course on web fundamentals. (category:learning, language:js, difficulty:beginner)`
+
+Tags
+- Use simple tags in parentheses after the description. Common tags: category, language, difficulty, license.
+- Tags help readers filter the list and let scripts export machine-readable data.
+
+How to contribute
+1. Open a pull request that adds or updates entries in the README under the appropriate section.
+2. Keep changes focused and small (one logical change per PR is ideal).
+3. If your change is large (reorganizing many items or adding whole learning paths), open an issue first to discuss structure.
+
+Pull request checklist (for contributors)
+- [ ] I checked for duplicates.
+- [ ] The entry has a short description and tags.
+- [ ] Links work (or a note explains a known issue).
+- [ ] Changes are limited to the intended section.
+
+Review & maintenance
+- This project is community-maintained. Anyone can review and suggest improvements.
+- There is no fixed review deadline — maintainers and community members will triage and review PRs as available.
+- If you want to take responsibility for a category, mention it in an issue or comment and the community can coordinate.
+
+Automation & formatting
+- Try to keep list formatting consistent (Markdown list items).
+- Consider running markdown linters locally before opening large PRs.
+
+Thanks — your contribution helps other developers find better resources.