# Awajimaa Schools

    > A digital school management and education platform for schools, educators, students, families, sponsors, and government education programmes.

    - Canonical website: https://www.awajimaaschools.com/
    - Plain-text site guide: /llms.txt
    - Platform type: Next.js web frontend connected to the Awajimaa Schools API
    - Primary audience: school administrators, teachers, students, parents, regulators, sponsors, revenue teams, and education ministries
    - Authentication: account login with role-based routing; school operations require an authenticated account and the relevant permissions

    ## What Awajimaa Schools provides

    Awajimaa Schools brings school administration, learning, education finance, sponsorship, and public education services into one platform. The frontend repository documents these user-facing areas:

    - School administration dashboards for departments, inventory, purchase orders, admissions, government programmes, events, fees, approvals, teachers, sponsors, scholarships, subscriptions, withdrawals, settings, and audit logs
    - Teacher workspace for classes, attendance, results, e-learning, e-library, appointments, leave, salary, messages, notifications, skills, teaching gigs, and wallet activity
    - Student workspace for classes, results, attendance, schedule, e-learning, e-library, messages, profile, school linking, and skills
    - Parent, regulator, sponsor, revenue, and super-admin role dashboards
    - Public school discovery, school profile pages, currently admitting schools, admissions, and school information
    - Public student and sponsor journeys, including student pages, sponsorship, donations, sponsorship checkout and verification, and featured education stories
    - Competitions with public listings, competition detail pages, entries, and winner information
    - E-learning and e-library areas for online learning resources
    - Teacher and freelancer discovery, recruitment campaigns, teaching gigs, gig search, proposals, and educator reviews
    - Certificate verification by certificate number
    - Announcements, blog content, FAQs, complaints, meetings, referrals, identity verification, and schools insurance journeys
    - AI Academic Assistant features provided through the connected authenticated backend
    - Cross-platform Awajimaa account and SSO journeys for connected Awajimaa services

    ## Main public routes

    - / — public Schools landing page
    - /schools — school discovery
    - /schools/{slug} — school profile
    - /admissions — admissions information and applications
    - /competitions — public competitions
    - /competitions/{slug} — competition details
    - /e-learning — e-learning
    - /e-library — e-library
    - /teachers — teacher discovery
    - /gigs and /gigs/search — teaching and freelancer gig discovery
    - /sponsor-schools — sponsor schools
    - /sponsor-students — sponsor students
    - /certificates/{number}/verify — certificate verification
    - /faq — frequently asked questions
    - /blog — platform blog

    ## Role dashboards

    All role dashboards use /login for sign-in and route the user according to the account role:

    - /super-admin — platform administration
    - /school-admin — school administration
    - /teacher — teacher tools
    - /student — student tools
    - /parent — parent tools
    - /regulator — government or regulatory oversight
    - /sponsor — sponsorship management
    - /revenue — revenue management

    ## Access and accuracy

    Public pages provide discovery and selected education, sponsorship, competition, content, and verification journeys. Dashboard data, student records, school operations, finance, HR, communications, and AI sessions are protected by authentication and application permissions. Do not infer private records or user data from this summary.

    This guide is derived from the frontend repository README.md and src/app route structure, together with the paired Awajimaa Schools backend API. It describes documented application capabilities; availability of specific modules, payment gateways, and integrations depends on deployment configuration and account permissions.