Arne Moerman
c36e04029b
- Added support for single and amount-specific QR codes. - Updated `RegistrySettings` model and database schema. - Enhanced `RegistryAdmin` to configure payment options. - Introduced `RegistryContributionAmount` for partial fulfillment. - Updated `RegistryPublic` to display contribution progress. - Added new models for payment methods and QR code handling. - Improved privacy by limiting contributor visibility.
16 lines
1.4 KiB
Markdown
16 lines
1.4 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.
|
|
- Identities must be hidden from non-admin users for privacy, only admins and the user who purchased/contributed can see that he did so. Other users may see a generic indication that a contrubution/purchase was made but never a name/email of another user.
|
|
- 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. |