[WIP] Find improvements in codebase

.gitignore

@@ -0,0 +1,71 @@
+# Operating System Files
+.DS_Store
+.DS_Store?
+._*
+.Spotlight-V100
+.Trashes
+ehthumbs.db
+Thumbs.db
+*~
+
+# IDE and Editor Files
+.vscode/
+.idea/
+*.swp
+*.swo
+*.swn
+*.bak
+*.sublime-project
+*.sublime-workspace
+
+# Logs
+logs/
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Dependencies
+node_modules/
+vendor/
+*.egg-info/
+dist/
+build/
+
+# Environment Variables
+.env
+.env.local
+.env.*.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+# Temporary Files
+tmp/
+temp/
+*.tmp
+
+# Build Artifacts
+*.pyc
+*.pyo
+__pycache__/
+*.class
+*.jar
+*.war
+*.ear
+target/
+
+# Test Coverage
+coverage/
+.nyc_output/
+htmlcov/
+.coverage
+*.cover
+.hypothesis/
+.pytest_cache/
+
+# Package Files
+*.zip
+*.tar.gz
+*.rar

CONTRIBUTING.md

@@ -0,0 +1,79 @@
+# Contributing to will-glas-test
+
+First off, thank you for considering contributing to will-glas-test! 🎉
+
+## How Can I Contribute?
+
+### Reporting Bugs
+
+Before creating bug reports, please check the issue list as you might find that you don't need to create one. When you are creating a bug report, please include as many details as possible:
+
+* **Use a clear and descriptive title** for the issue to identify the problem
+* **Describe the exact steps to reproduce the problem** in as much detail as possible
+* **Provide specific examples to demonstrate the steps**
+* **Describe the behavior you observed** after following the steps
+* **Explain which behavior you expected to see instead and why**
+* **Include screenshots and animated GIFs** if relevant
+
+### Suggesting Enhancements
+
+Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion, please include:
+
+* **Use a clear and descriptive title** for the issue
+* **Provide a step-by-step description of the suggested enhancement** in as much detail as possible
+* **Provide specific examples to demonstrate the steps** or point out the part of the project where the enhancement should go
+* **Describe the current behavior** and **explain which behavior you expected to see instead**
+* **Explain why this enhancement would be useful** to most users
+* **List some other projects where this enhancement exists** if applicable
+
+### Pull Requests
+
+* Fill in the pull request template
+* Follow the style guidelines of this project
+* Write clear, concise commit messages
+* Include relevant issue numbers in your PR description
+* Update documentation as needed
+* Ensure your code follows the existing code style
+
+## Style Guidelines
+
+### Git Commit Messages
+
+* Use the present tense ("Add feature" not "Added feature")
+* Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
+* Limit the first line to 72 characters or less
+* Reference issues and pull requests after the first line
+* Consider starting the commit message with an applicable emoji for better readability:
+  * 🎨 `:art:` when improving the format/structure of the code
+  * 🐛 `:bug:` when fixing a bug
+  * ✨ `:sparkles:` when introducing new features
+  * 📝 `:memo:` when writing docs
+  * 🚀 `:rocket:` when improving performance
+
+### Code Style
+
+* Follow the existing code style in the repository
+* Keep code clean and readable
+* Comment complex logic when necessary
+* Write meaningful variable and function names
+* Keep functions small and focused on a single task
+
+## Getting Started
+
+1. Fork the repository
+2. Create a new branch from `main` (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Test your changes thoroughly
+5. Commit your changes (`git commit -m 'Add some amazing feature'`)
+6. Push to the branch (`git push origin feature/amazing-feature`)
+7. Open a Pull Request
+
+## Code of Conduct
+
+This project and everyone participating in it is governed by our Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior by opening an issue.
+
+## Questions?
+
+Feel free to open an issue with your question or reach out to the maintainers directly.
+
+Thank you for your contributions! ❤️

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 will-glas-test contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -1 +1,93 @@
-# will-glas-test
+# will-glas-test
+
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
+[![GitHub issues](https://img.shields.io/github/issues/willglas/will-glas-test)](https://github.com/willglas/will-glas-test/issues)
+[![GitHub stars](https://img.shields.io/github/stars/willglas/will-glas-test)](https://github.com/willglas/will-glas-test/stargazers)
+
+A test repository for exploring GitHub features, workflows, and best practices.
+
+## 📋 Table of Contents
+
+- [About](#about)
+- [Getting Started](#getting-started)
+- [Usage](#usage)
+- [Contributing](#contributing)
+- [License](#license)
+- [Contact](#contact)
+
+## 🎯 About
+
+This repository serves as a testing ground and learning environment for:
+
+- GitHub workflow experimentation
+- CI/CD pipeline testing
+- Documentation standards and best practices
+- Community contribution practices
+- Version control strategies
+- Project management tools
+
+## 🚀 Getting Started
+
+### Prerequisites
+
+Before you begin, ensure you have the following installed:
+
+- [Git](https://git-scm.com/downloads) (version 2.0 or higher)
+- A GitHub account
+
+### Installation
+
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/willglas/will-glas-test.git
+   ```
+
+2. Navigate to the project directory:
+   ```bash
+   cd will-glas-test
+   ```
+
+3. Start experimenting with your own features!
+
+## 💡 Usage
+
+This repository is designed for experimentation and learning. Feel free to:
+
+- Create new branches to test different features
+- Experiment with GitHub Actions and workflows
+- Practice writing issues and pull requests
+- Test documentation improvements
+- Explore different Git strategies
+
+## 🤝 Contributing
+
+We welcome contributions from the community! Please read our [Contributing Guidelines](CONTRIBUTING.md) for details on:
+
+- How to report bugs
+- How to suggest enhancements
+- Code style guidelines
+- The pull request process
+
+Please also read our [Code of Conduct](CODE_OF_CONDUCT.md) to understand the standards we expect from our community.
+
+## 🔒 Security
+
+If you discover a security vulnerability, please follow the instructions in our [Security Policy](SECURITY.md).
+
+## 📄 License
+
+This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
+
+## 📞 Contact
+
+- **Issues**: For questions or issues, please [open an issue](https://github.com/willglas/will-glas-test/issues)
+- **Discussions**: Join our [GitHub Discussions](https://github.com/willglas/will-glas-test/discussions) for general questions and community interaction
+
+## 🙏 Acknowledgments
+
+- Thanks to all contributors who help improve this project
+- Inspired by open source best practices from the community
+
+---
+
+Made with ❤️ by the will-glas-test community