Arne Moerman
c1b11603e8
Build and Push Docker Image / build-and-push (push) Successful in 1m14s
Implemented a Blazor Web App (.NET 8) for a public-by-link birth registry platform, following project guidelines. Added domain entities, EF Core context, and Blazor components for authentication, registry management, and public views. Introduced core services for registries, theming, user context, platform owner bootstrapping, and SMTP email. Included static assets (Bootstrap, favicon), launch settings, Dockerfile, CI workflow, and deployment configs. Added bootstrap.min.css.map for improved CSS debugging.
15 lines
1.2 KiB
Markdown
15 lines
1.2 KiB
Markdown
# Copilot Instructions
|
|
|
|
## Project Guidelines
|
|
- Use Blazor Web App (.NET 8) with an interactive server and CSS isolation; split components into code-behind files when component parameter count grows beyond a few.
|
|
- Support partial quantities in the purchase flow and display purchased/desired progress; guests must log in before reserving/purchasing.
|
|
- Authentication must support local accounts plus Microsoft and Google login; admin invite links are single-use and not email-locked.
|
|
- Money participation defaults to EUR and tracks fulfilled amount per item via bank-transfer contributions with item-linked messages.
|
|
- Registry visibility is public-by-link initially, but logged-in users who visited a registry should be able to rediscover it in-app.
|
|
- Use SQL Server as the default provider and set `RequireConfirmedAccount=false` for MVP testing; the first registered account should be the owner with full access.
|
|
|
|
## Technical Specifications
|
|
- Use SMTP via Google initially for email functionalities.
|
|
- Support registry type theming from day one to enhance user experience.
|
|
- URL autofetch should utilize OpenGraph/meta tags for better link previews.
|
|
- Use Blazored.TextEditor for rich text editing. |