Title Enterprise Laravel Platform for Political Party Internal Governance + Public Website ⸻ Description Hello, We are building a full-scale digital infrastructure for a newly forming political party, consisting of two separate but connected web systems: ⸻ 1. TECHNICAL ARCHITECTURE OVERVIEW The project consists of the following structure hosted on a dedicated server: • /engine_laravel/ → Main Laravel backend engine (core database, roles, permissions, APIs) • /public_html/ → Public-facing party website (no authentication, lightweight frontend) • /party_internal_subdomain/ → Internal secured organizational platform (full authentication) The public website dynamically consumes selected data from the Laravel engine (news, leadership, activity reports, transparency data). The internal platform is a custom-built governance and membership management system, not a marketing website. ⸻ 2. INTERNAL PLATFORM — CORE PURPOSE The internal system is designed to manage a real political party structure including: • Membership onboarding and administration • Statutory leadership roles • Organizational branches (national → county → local) • Internal documents and official workflows • Role-based dashboards and permissions • Internal communication and reporting Political parties typically operate across multiple territorial layers (national, regional/county, local branches).  ⸻ 3. MEMBERSHIP WORKFLOW (STRICT MULTI-STAGE ONBOARDING) Registration is not a simple signup. It follows a mandatory workflow: 1. User registers (Step 1) 2. Email verification required (Step 2) 3. Completion of legally required personal membership data (Step 3) 4. Temporary waiting state (cannot access platform) 5. Manual activation by Secretary-General / Admin 6. Only then access is granted based on assigned structure and role No page can be accessed unless all onboarding stages are completed. ⸻ 4. ROLE-BASED ACCESS CONTROL (RBAC — ENTERPRISE LEVEL) The platform requires extremely granular permission handling: • Permissions are not static • Sidebar navigation is dynamically generated based on role + structure membership • Access rules apply down to route/action level Two parallel role systems exist: A) Statutory Roles (Party Constitution Roles) Examples: • President • Secretary-General • Vice-President • Treasurer • National Executive Members B) Earned / Appointed Roles via Internal Structures Examples: • County Coordinator • Local Branch Organizer • Youth Organization Leader • Media & Communications Officer • Internal Audit Officer Roles depend on organizational membership and can stack. ⸻ 5. ORGANIZATIONAL STRUCTURE MANAGEMENT The party contains multiple governing bodies: • National Congress • National Political Council • National Executive Bureau Plus territorial organizations: • National level • County branches (41 counties + Bucharest) • Local branches (municipalities, towns, communes) Romania’s territorial administrative structure includes counties and local councils, which is relevant for mapping party branches geographically.  ⸻ 6. SPECIALIZED INTERNAL ORGANIZATIONS (BRANCHES) The platform must support additional national organizations such as: • Youth Wing (Tineret) • Women’s Organization • Seniors Organization • Professional Councils (teachers, doctors, entrepreneurs) • Diaspora Branches Each organization has independent leadership, roles, internal membership and reporting. Youth branches are common political structures across Europe.  ⸻ 7. DYNAMIC DASHBOARD PER ROLE AND STRUCTURE The homepage is a real-time governance dashboard showing: • Tasks and approvals relevant to your role • Membership statistics in your hierarchy • Local branch activity if you are a county leader • National reports if you are part of executive leadership Example: • A local organizer sees only their locality members • A county coordinator sees all local branches under their county • National leadership sees nationwide analytics ⸻ 8. INTERNAL DOCUMENT GENERATION + PDF SYSTEM The system includes official political documents such as: • Membership application (Adeziune) • Appointment and Investiture documents • Role assignment certificates • Internal regulations and bylaws • Printable recruitment forms for offline use Documents must be: • Generated dynamically • Downloadable as PDF • Stored with audit trails ⸻ 9. INTERNAL COMMUNICATION MODULES Planned features include: • Internal messaging system • Notifications by organizational structure • Group email broadcasting: • National → County • County → Local • Organization leaders → members Example: Media department can send press instructions only to approved spokespeople. ⸻ 10. NEWS + MEDIA PUBLISHING SYSTEM A restricted CMS system is required: • Only designated Media Officers can create/publish articles • Articles are categorized and pushed dynamically to the public website • Category-based access and editorial approval workflow may be added later ⸻ 11. ADVANCED PERMISSION-BASED NAVIGATION The UI must support: • Sidebar links shown only if user has permissions • Dropdown menus listing occupied roles and active structures dynamically • Structure-based discovery: • “Your branch” • “Your council” • “Your organization” ⸻ 12. SECURITY + COMPLIANCE REQUIREMENTS This platform handles sensitive political membership data and must include: • Secure authentication • Access logs and audit trail • GDPR-compliant storage practices • Strict separation between internal/private and public data ⸻ 13. REQUEST We are looking for an experienced Laravel developer or agency able to provide: • Approximate cost estimate • Timeline estimate • Team requirements • Risks and complexity assessment This is an enterprise governance platform, not a simple website. Thank you.