For content admins
A guide for content admins
The CMS is where lessons, stories and quizzes are written, drafted with AI, reviewed and published. One rule runs through all of it: nothing an AI drafts reaches a child until a person has approved it.
What an admin account is
An admin signs in with an email address and password from Admin sign-in on the homepage. Parents sign in with Google. The two kinds of account never overlap, and a parent who opens an admin page is turned away.
There is no sign-up page and no invitation. An engineer creates each admin account with a script: Part 1 of the admin account guide covers local development, and Part 2 covers a deployed server. A forgotten password is reset the same way.
The workspace
The sidebar has six sections: Curriculum, Stories, Media, Badges, AI Queue and Analytics. You land on Analytics when you sign in, and AI Queue shows how many drafts are waiting for review. The CMS is designed for a desktop screen; on narrower screens the sidebar becomes a bar along the top.
Building the curriculum
Content is organised as subjects, then topics, then lessons, shown side by side in three panes. You can drag to reorder at any level. A lesson's world, the setting a child sees it in, is a field on the lesson rather than another level.
Each lesson has an English tab and a Bangla tab, each with a title, intro and narration scripts, videos and grade levels, and links to one activity and one quiz. The quiz and activity editors check what you type as you go, and preview it with the same component a child will see.
Media
Videos, audio and images upload straight from your browser to Cloudinary. No file passes through our server, which keeps only each file's address and details. You can attach media to lesson videos, story pictures, quiz questions, world mascots and badge icons.
The AI pipeline
From the AI Queue you can ask for a draft lesson, story, set of quiz questions, narration or illustration. Text and images come from Google's Gemini models; narration comes from Google Cloud Text-to-Speech, with English and Bangla voices.
Every draft is checked against the same rules that hand-written content must pass, then saved as a draft waiting for review. Each kind of draft has a daily limit, so one busy day cannot use up the whole budget.
The review queue
Filter the queue by type, language or grade, then open a draft to read the text, listen to the audio and look at the pictures. You have three choices:
- Approve: it is published as it is.
- Edit, then approve: fix it in an editor that opens already filled in.
- Reject: give a reason of at least ten characters, so the next person knows why.
A draft cannot be published while it still has a placeholder image. Every decision is recorded with who made it, when and why.
The publishing lifecycle
All content, whether written by hand or drafted by AI, moves through the same statuses. Children only ever see published content.
Rejected content cannot jump straight to published: it goes back to draft and through review again. Published content can be taken back to draft, and anything can be archived and restored later.
What an admin cannot do
Some limits are deliberate. An admin cannot:
- See any child's or parent's personal details. The CMS holds no family records, and Analytics shows totals only.
- Publish AI-drafted content without a review decision. The server refuses.
- Create another admin, or reset a password, from the CMS.
- Sign in with Google. That is for parents only.