Added a Roadmap and Contributing guidelines

Author: ckenst

CONTRIBUTING.md

@@ -0,0 +1,35 @@
+# Contributing to testingconferences.org
+
+First off, thank you for considering contributing! It’s people like you who keep this list accurate and useful for the testing community.
+
+## How Can I Contribute?
+
+### 1. Adding a New Conference
+The most common way to help is by adding a conference that isn't on the list yet or updating one that is. 
+- Search the current list to make sure it isn't already there.
+- Open a Pull Request (PR) adding the conference to the relevant data file.
+- Ensure you follow our data schema (see the `README.md` for field requirements).
+
+### 2. Reporting an Issue
+If you find a broken link, an incorrect date, or a bug on the site:
+- **Check the Footer:** Find the **Site Version** in the footer of the website.
+- **Open an Issue:** Include the version number and a description of the error.
+
+### 3. Improving the Site (DX/Quality)
+We are currently working through our [ROADMAP.md](./ROADMAP.md) to improve site quality and developer experience. If you want to help with Lighthouse scores, build scripts, or automation, please check the roadmap for "Open" tasks.
+
+---
+
+## Pull Request Guidelines
+To help us review your changes quickly, please follow these steps:
+
+1. **Fork the repo** and create your branch from `main`.
+2. **Test your changes** locally to ensure the build passes.
+3. **Reference Issues**: If your PR fixes a bug, include `Closes #123` in the description.
+4. **Style**: Please ensure your code/data follows the project's formatting (Prettier/ESLint).
+
+## Code of Conduct
+By participating in this project, you agree to abide by our Code of Conduct [link to file or text]. We strive to maintain a welcoming and inclusive environment.
+
+---
+**Need help?** If you have questions about how to contribute, feel free to open a "Question" issue and we'll help you get started!

ROADMAP.md

@@ -0,0 +1,54 @@
+# Roadmap: testingconferences.org
+
+## Project Vision
+Continue to use TCorg to experiment and learn. I want to track quality metrics automatically. Yes these are indirect quality metrics, but I'd like to see what I can track on the build side and how it works. Then improve upon them later.
+
+---
+
+## Phase 1: Versioning & Traceability (High Priority)
+*Goal: Establish a "Source of Truth" for site deployments.*
+
+- [x] **Implement `VERSION` file**: Create a plaintext file in the root directory to track SemVer (e.g., `1.0.0`).
+- [ ] **Footer Integration**: Update the website footer to dynamically display the current string from the `VERSION` file.
+- [ ] **Automated Increments**: Create a workflow to increment the `VERSION` file on every deployment.
+- [ ] **Deployment Tagging**: Ensure every production deploy is tagged in Git to match the internal version.
+
+## Phase 2: Quality Ledger & Metrics
+*Goal: Associate every site version with a specific quality snapshot.*
+
+- [ ] **Lighthouse Tracking**: Automate Lighthouse audits during CI and record Performance, Accessibility, and SEO scores per version.
+- [ ] **Link Integrity**: Implement a broken link checker (e.g., `linkinator`) to log broken link counts against the current version.
+- [ ] **Build Analytics**: Track and log build times to monitor the impact of site growth on CI/CD performance.
+- [ ] **Bug Attribution**: Update Issue Templates to include a "Site Version" field to track bug counts relative to specific releases.
+
+## Phase 3: Developer Experience (DX) & AI Workflows
+*Goal: Streamline contributions using automation and AI context.*
+
+- [ ] **Automatic Linting**: Set up Prettier and ESLint with pre-commit hooks (Husky) to ensure code consistency.
+- [ ] **AI Contextualization**: Create a `.github/copilot-instructions.md` to help GitHub Copilot understand the conference data schema and project goals.
+- [ ] **Prompt Imports**: Build a library of standardized prompts to assist contributors in formatting and validating new conference submissions.
+
+## Phase 4: Public Quality Dashboard
+*Goal: Surface project health and transparency to the community.*
+
+- [ ] **Metrics Dashboard**: Build a public-facing page (e.g., `/stats` or `/quality`) to visualize project health.
+- [ ] **Trend Visualization**: Display historical graphs of Lighthouse scores, bug counts, and conference growth over different versions.
+- [ ] **Live Status Badges**: Integrate dynamic README badges for current version, build status, and site health.
+
+## Misc:
+*Goal: Other important features
+
+- [ ] **Calendar Download**: Make it possible to just download the current TC.org data as a ICO and import it into your calendar
+- [ ] **Reference License in Footer**: Should we reference our MIT-LICENSE file in super footer?
+
+---
+
+## Version History & Quality Log
+*This table tracks the evolution of the site's quality over time.*
+
+| Version | Release Date | Lighthouse (Perf) | Broken Links | Build Time | Bugs Found |
+| :--- | :--- | :--- | :--- | :--- | :--- |
+| v1.0.0 | 2025-XX-XX | TBD | TBD | TBD | TBD |
+
+---
+*Last Updated: December 2025*