60 lines
5.1 KiB
Markdown
60 lines
5.1 KiB
Markdown
# Product
|
|
|
|
<!-- impeccable:product-schema 1 -->
|
|
|
|
## Platform
|
|
|
|
web
|
|
|
|
## Users
|
|
|
|
- Students and other event participants who discover events, register, receive communications, read articles, and manage their account.
|
|
- Association members with different staff roles who organize events, manage registrations and participant communications, and publish articles or announcements.
|
|
- Designated content staff who draft public-page changes, and a smaller publisher group who approves them for release.
|
|
|
|
## Product Purpose
|
|
|
|
This is the public website and operating interface for the computer engineering student association at the University of Guilan's East Guilan Faculty of Engineering. It helps people understand the association, discover and attend events, and read its technical/editorial content; it helps members run those activities. The current project is a redesign and public-content management upgrade, not a change to the underlying event business rules.
|
|
|
|
## Operating Context
|
|
|
|
The existing system is a Persian RTL web application with Next.js/React frontend and a Django/Ninja backend, PostgreSQL, and Django admin. Student journeys include authentication, event discovery, registration, payment where applicable, notifications, and blog reading. Staff journeys include event, registration, user, and blog administration. The association also sends email/SMS messages to participants through the existing backend workflows.
|
|
|
|
## Capabilities and Constraints
|
|
|
|
- Public editorial content and shared branding—including Home/About copy, title/logo, approved images, navigation, footer, and SEO—must be editable through Django admin.
|
|
- Editors may change, reorder, or hide predefined Home/About section types; creating new layouts remains development work.
|
|
- Staff draft; a narrower publisher role approves and publishes. Superusers retain full access.
|
|
- Functional interface labels, form/validation messages, and admin-screen text remain in versioned application code.
|
|
- Existing event registration, capacity, payment, cancellation, and eligibility rules must be preserved in the first release.
|
|
- Transactional email, SMS, and in-app message templates are outside the first release and need a later reviewed phase.
|
|
- Redesign priority is Home/About, authentication, events and registration, blog, then the responsive staff-admin interface.
|
|
- Current static public content needs an auditable, reviewed production seed rather than manual re-entry or guessed corrections.
|
|
- The owner selected the About-page association contacts on 2026-09-24; scope and dates for legacy statistics and affiliate entries still need mapping before seeding.
|
|
|
|
## Brand Commitments
|
|
|
|
- Official full name: `انجمن علمی مهندسی کامپیوتر دانشگاه گیلان (دانشکدهی فنی و مهندسی شرق گیلان)`.
|
|
- Preserve the recognizable current association logo and use existing approved assets first.
|
|
- The owner rejected the two initial concepts and the first current-derived refinement on 2026-09-25. The owner approved the logo-led Home/About direction, based on the association's teal, pale gold, and charcoal and the three supplied references, on 2026-09-25; the CMS/API contract was approved on 2026-09-26. See `DESIGN.md` and the approved component mapping.
|
|
|
|
## Bundle 0 Owner Decisions (2026-09-24)
|
|
|
|
- Home/About should explain the association in the first screen before directing visitors to events or articles.
|
|
- The current repository logo is an approved source for the concepts.
|
|
- Use the About page's association contact set for the new design: `eastguilanceassociation@gmail.com`, `https://t.me/guilancea`, and `https://instagram.com/guilance.ir`. The Footer contains different legacy values; keep those differences visible in the content inventory until cutover.
|
|
- The earlier Plan A selection was withdrawn. The owner approved this Home order: current landing and website introduction, featured events, featured blog posts, CTA, footer. Use existing Shadcn/ui components and Lucide icons in implementation, with colors drawn from the association logo. The approved Home/About comps provide the visual direction; production content and responsive/accessibility details are verified during implementation.
|
|
|
|
## Evidence on Hand
|
|
|
|
- Real event and blog content exists in the backend; the current Home/About pages and shared navigation/footer contain legacy public copy and imagery.
|
|
- Current Home/About metadata, contacts, association names, and numeric claims differ. The owner says repository facts are verified and selected the About contact set; the migration inventory preserves variants and maps each claim to its entity before publication.
|
|
- No new approved association/team photography has been supplied for this project; do not fabricate documentary images.
|
|
|
|
## Product Principles
|
|
|
|
1. Keep event and registration information truthful to the backend state.
|
|
2. Give editors control over public content without making structural layout or sensitive workflow changes accidental.
|
|
3. Make student and staff tasks understandable and usable at phone and desktop widths.
|
|
4. Preserve existing data and behavior through a reversible, reviewed rollout.
|