feat: initial site setup (#1)

### Explanation

_No response_

### Issue

_No response_

### Attestations

- [x] I have read and agree to the [Code of Conduct](https://docs.nhcarrigan.com/community/coc/)
- [x] I have read and agree to the [Community Guidelines](https://docs.nhcarrigan.com/community/guide/).
- [x] My contribution complies with the [Contributor Covenant](https://docs.nhcarrigan.com/dev/covenant/).

### Dependencies

- [x] I have pinned the dependencies to a specific patch version.

### Style

- [x] I have run the linter and resolved any errors.
- [x] My pull request uses an appropriate title, matching the conventional commit standards.
- [x] My scope of feat/fix/chore/etc. correctly matches the nature of changes in my pull request.

### Tests

- [ ] My contribution adds new code, and I have added tests to cover it.
- [ ] My contribution modifies existing code, and I have updated the tests to reflect these changes.
- [ ] All new and existing tests pass locally with my changes.
- [ ] Code coverage remains at or above the configured threshold.

### Documentation

_No response_

### Versioning

_No response_

Reviewed-on: #1
Co-authored-by: Naomi Carrigan <commits@nhcarrigan.com>
Co-committed-by: Naomi Carrigan <commits@nhcarrigan.com>

README.md

@@ -1,39 +1,59 @@
-# New Repository Template
+# Yurigpt
 
-This template contains all of our basic files for a new GitHub repository. There is also a handy workflow that will create an issue on a new repository made from this template, with a checklist for the steps we usually take in setting up a new repository.
+This project was generated using [Angular CLI](https://github.com/angular/angular-cli) version 20.0.5.
 
-If you're starting a Node.JS project with TypeScript, we have a [specific template](https://github.com/naomi-lgbt/nodejs-typescript-template) for that purpose.
+## Development server
 
-## Readme
+To start a local development server, run:
 
-Delete all of the above text (including this line), and uncomment the below text to use our standard readme template.
+```bash
+ng serve
+```
 
-<!-- # Project Name
+Once the server is running, open your browser and navigate to `http://localhost:4200/`. The application will automatically reload whenever you modify any of the source files.
 
-Project Description
+## Code scaffolding
 
-## Live Version
+Angular CLI includes powerful code scaffolding tools. To generate a new component, run:
 
-This page is currently deployed. [View the live website.]
+```bash
+ng generate component component-name
+```
 
-## Feedback and Bugs
+For a complete list of available schematics (such as `components`, `directives`, or `pipes`), run:
 
-If you have feedback or a bug report, please feel free to open a GitHub issue!
+```bash
+ng generate --help
+```
 
-## Contributing
+## Building
 
-If you would like to contribute to the project, you may create a Pull Request containing your proposed changes and we will review it as soon as we are able! Please review our [contributing guidelines](CONTRIBUTING.md) first.
+To build the project run:
 
-## Code of Conduct
+```bash
+ng build
+```
 
-Before interacting with our community, please read our [Code of Conduct](CODE_OF_CONDUCT.md).
+This will compile your project and store the build artifacts in the `dist/` directory. By default, the production build optimizes your application for performance and speed.
 
-## License
+## Running unit tests
 
-This software is licensed under our [global software license](https://docs.nhcarrigan.com/#/license).
+To execute unit tests with the [Karma](https://karma-runner.github.io) test runner, use the following command:
 
-Copyright held by Naomi Carrigan.
+```bash
+ng test
+```
 
-## Contact
+## Running end-to-end tests
 
-We may be contacted through our [Chat Server](http://chat.nhcarrigan.com) or via email at `contact@nhcarrigan.com`. -->
+For end-to-end (e2e) testing, run:
+
+```bash
+ng e2e
+```
+
+Angular CLI does not come with an end-to-end testing framework by default. You can choose one that suits your needs.
+
+## Additional Resources
+
+For more information on using the Angular CLI, including detailed command references, visit the [Angular CLI Overview and Command Reference](https://angular.dev/tools/cli) page.