doc updates

Author: pwelter34

AspNetCore.SecurityKey.sln

@@ -0,0 +1,19 @@
+<Solution>
+  <Folder Name="/Build/">
+    <File Path=".github/workflows/dotnet.yml" />
+    <File Path="README.md" />
+    <File Path="src/Directory.Build.props" />
+  </Folder>
+  <Folder Name="/Samples/">
+    <File Path="samples/Directory.Build.props" />
+    <Project Path="samples/Sample.Controllers/Sample.Controllers.csproj" />
+    <Project Path="samples/Sample.Middleware/Sample.Middleware.csproj" />
+    <Project Path="samples/Sample.MinimalApi/Sample.MinimalApi.csproj" />
+    <Project Path="samples/Sample.Shared/Sample.Shared.csproj" />
+  </Folder>
+  <Folder Name="/Tests/">
+    <File Path="test/Directory.Build.props" />
+    <Project Path="test/AspNetCore.SecurityKey.Tests/AspNetCore.SecurityKey.Tests.csproj" />
+  </Folder>
+  <Project Path="src/AspNetCore.SecurityKey/AspNetCore.SecurityKey.csproj" />
+</Solution>

AspNetCore.SecurityKey.slnx

@@ -0,0 +1,65 @@
+# Contributing to AspNetCore.SecurityKey
+
+Thank you for considering contributing to AspNetCore.SecurityKey! We welcome contributions from the community.
+
+## How to Contribute
+
+### Reporting Issues
+
+- Use the GitHub issue tracker to report bugs or request features
+- Provide clear reproduction steps for bugs
+- Include environment information (.NET version, OS, etc.)
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a feature branch from `main`
+3. Make your changes
+4. Add or update tests as needed
+5. Ensure all tests pass
+6. Update documentation if needed
+7. Submit a pull request
+
+### Development Setup
+
+1. Clone the repository:
+
+   ```bash
+   git clone https://github.com/loresoft/AspNetCore.SecurityKey.git
+   ```
+
+2. Build the solution:
+
+   ```bash
+   dotnet build
+   ```
+
+3. Run tests:
+
+   ```bash
+   dotnet test
+   ```
+
+4. Run samples to test your changes:
+
+   ```bash
+   cd samples/Sample.MinimalApi
+   dotnet run
+   ```
+
+### Code Style
+
+- Follow existing code conventions
+- Use meaningful variable and method names
+- Add XML documentation for public APIs
+- Keep methods focused and concise
+
+### Testing
+
+- Write unit tests for new functionality
+- Ensure existing tests continue to pass
+- Test with the sample applications
+
+## Questions?
+
+Feel free to open an issue for any questions about contributing.