The guide

Getting started as an Admin

Ebiblo writes nothing by itself. Every page you make comes with agents: Quill writes posts and sections, and Quest writes the questions. Nothing they write reaches a reader until a person approves it.

1. Sign in, or create your account. Press Get started. Sign in with email and password, Apple or Google — or create an account with your name, email, a password, your birth month, and one question: What brings you here? Say Create and teach and you start on the Admin side, ready to make your first page.
2. Make your first page. Home greets a new creator with "What would you like to make first?" — a blog, a document or a quiz. Pick one, name it, say in a line what it should cover, and choose its language and who it's for. The page opens with its agents already attached. The free plan covers your first pages.
3. Ask the agents to write. Press Start writing on a blog or document, or Start a new question set on a quiz, and say what you want — typed or spoken, with files attached if you have them. On the free plan they write a set number of times a month.
4. Approve the draft. It lands on the page marked Awaiting approval, and Ebiblo tells you when it arrives. Read everything, fix or cut what you want, then publish.
5. Share it. Send the page's link, add learners, or let a public blog be found on the open web.

Home also keeps a Getting started list — make a page, get its first draft, publish it, share it — that ticks itself off as you go, and leaves once everything is done.

The screens below are the app itself, shown with sample pages and people.

Two roles, one account

One account holds both roles. The switch in the header changes what the same screens show. It is a way of looking, not a second login, and each device remembers your choice.

You have an Admin side if you own any page, or said at sign-up that you came to create. Open a page someone shared with you and you are a Learner on it. Their page stays theirs. So one account can own a page and answer on someone else's — and since your own published work also shows on your Learner side, you can sit exactly where your learners sit.

The home screen

Both roles share one layout with different data:

• As an admin — the headline is your review queue ("One set is waiting for you"). A Next for review card holds the oldest draft, with Publish and Review ready, and two numbers keep count across your pages: what is awaiting approval, and your drafts.
• As a learner — a Continue learning card picks up the set you are in the middle of, with your progress and the one fact that matters: your score and date when finished, or when you last worked on it. Two numbers count what you finished and what is new for you this week.
• Library — four tabs: Quizzes, Documents and Blogs for everyone, Inputs for admins. One row per question set, section or post, with search and filters; names open the page on that very item. A row's ⋯ holds Open, Pin to top, Page settings and Remove. An Input page goes with the page it feeds; one whose page is gone can be removed on its own.

Creating a page

The Create button sits by Home's headline, on the Admin side. It offers three kinds of page, and a new creator's welcome offers the same three:

• Blog — a home for posts that come out regularly. A blog is always public.
• Document — reading for your learners, section by section, in order.
• Quiz — question sets for your learners.

Each kind asks for the same few things:

• Title — what the page is called everywhere.
• What should it cover? — a line or two for the page's agents. Optional, and yours to change later as the Brief in the page's Settings.
• Access — private, group or public. A blog is always public; public documents and quizzes are on Pro.
• Language — the page's own language, chosen once. Its agents write everything in it.

On success you land on the new page, agents attached, ready to be asked for a first draft.

Quill, Quilt and Quest, the page's agents

A document or a blog comes with three agents, listed in the order they work. Quill writes its posts or sections. Quilt draws a lead picture for each one. Quest writes the questions, as a knowledge check inside the text. A quiz page has one agent, which writes its sets. More agents added in Emidox appear after them.

Each agent is one quiet row under the page's Admin controls: its mark, its state ("Ready", or "Last wrote 10 Oct 2026"), and its job. Open Advanced and each row adds its prompt, which opens to read and edit, a model picker, its Input page (the tray icon) and the ↗, which opens the agent in Emidox. The page's Brief is read alongside the prompt, and learners never see either.

Each agent's work has a home of its own. Quill's Input page holds the material it works from, under Library → Inputs. Quest's question sets sit on the page itself, on its Question sets tab, and in Library → Quizzes.

Writing posts and sections

Start writing asks Quill for a new post or section. Add a note if you like, typed or spoken with Speak; attach files for this one only; and pick the model it writes with. What it reads besides is set once, on its Input page, in Use data from: the most recent update, the last 24 hours or 7 days, or everything. The page shows Quill at work, and opens the new draft when it lands, even if you started from the Question sets tab.

Change what's written. In the editor, Write with AI rewrites the whole post from your note, and Add picture has Quilt draw a lead picture for it, from your note if you wrote one. The new picture goes first and takes the place of one Quilt drew there by itself; your own pictures stay where they are. Select any passage and a small bar appears over it: Quill rewrites just that part the way you ask, Quilt draws a picture of it, put right under it, and Quest adds a knowledge check right after it, from at least ten words. Nothing is saved until you save, and Undo takes it back.

Everything you send goes through the page's one Input page, tagged with the post it's for, so all you ever asked is kept in one place.

The editor is a full writing surface: bold, italic and underline, H2 and H3 headings, quotes, lists, callouts, links, pictures and YouTube, undo and redo. A document adds the working set — a smaller heading, strikethrough, code and code blocks, dividers, and tables with row and column options. The Font pick at the bar's end chooses among five families of the page's script, worn by writer and reader alike, and the editor writes in the page's own direction.

On a blog post, topic tags ride under the text: Quill suggests up to five, in the page's language, and you keep, dismiss, or add your own — five at most, saved as you go. Readers see them under the article.

Knowledge checks inside posts

A post can carry a knowledge check right where it is read. The editor's check tool drops the card into the text, or Quest adds one after a passage you select, and each is linked to its own question set on the page. On a document or blog, that's how question sets are made: one check, one set, all listed on the page's Question sets tab. The reading and the proof of reading live together.

• Readers answer in place. The card opens into the questions; answers are marked on submit; the card remembers where they got to — resume, review, retake.
• Every word is yours. A fresh check arrives saying "Did it stick?", "Quick questions on this post." and one button, "Test yourself" — the heading, the description, even the button label are yours to change, and the check can stand left, centre or right. The next check you add copies the last one's wording and settings — never its question set.
• Nothing half-made shows. A check with no linked set draws nothing for readers, and neither does one whose set still waits for approval. The post can go live before its check does.
• No account needed to try. A signed-out reader's attempt stays on their device; signing in afterwards keeps the result.

Question sets and their states

A set is a group of questions on one topic, written by the page's agent from the material and brief you gave it. Posts and sections live by the same three states:

• Awaiting approval — just written. Learners cannot see it.
• Draft — you have edited it but not published it. If it was already live, learners keep seeing the live version until you publish your changes.
• Published — visible to readers and learners on that page.

Approving and publishing

This is the step that makes Ebiblo safe to send. Nothing reaches a learner unless a person says so.

1. Open the page. Use the Awaiting approval tab to see what needs you.
2. Open a set or a post. Every question is listed with its options and, for written ones, the answer you expect; a post shows its full text.
3. Read it. Change the wording, the options or the expected answer. Delete what you don't want. Editing something approved turns it back into a draft until you publish again.
4. Press Publish. It goes live on that page.

Prefer new work to go straight out on a page you trust? Turn Require approval off in that page's Settings: new sets publish themselves, and you are told each time. Turning it off also releases everything that was waiting.

Doing several at once

Press Select in the list to show tick boxes. Tick the sets, posts or sections you want, or Select all, then Publish or Delete. Deleting asks you to confirm and removes the items, their questions and any attempts — it can't be undone. There is no bulk Unpublish on purpose; each item's own bar takes it down.

Input pages and triggers

An input page holds the material an agent works from. Open it from the Inputs tab on the home screen — a document's or blog's belongs to Quill.

• Sources — the files you add: outlines, slides, documents, pictures, a photo of a worksheet. They belong to this page.
• Prompt — a line or two about what to ask for. Type it, or press Speak and say it.
• Connected agent — which agent works on this page, and where it sends what it writes.
• Trigger — when the agent works:
  • On update — the usual choice. Change a file and a new draft is written.
  • Daily — once a day, at a time you set.
  • Manually — nothing happens until you press Send. Choose what each send reads under Use data from: the most recent update, the last 24 hours or 7 days, or everything.
  • Off — the agent is switched off and you cannot send it anything.
• Picture agent — on a document's or a blog's own Input page, Quilt with a trigger of its own: On update for a picture with each new post or section, or Manually for a picture only when you press Add picture.

Press Send to ask for a draft now. It arrives on the page marked Awaiting approval.

Public, group and private

Every page has one of three doors, chosen at Create and changed in Settings:

• Private — one named learner, and only them. One page per learner is the point: everything on it is for that person, and their results stand alone.
• Group — the people you add, and the people you approve. When Allow requests to join is on, a signed-in reader who finds the page can ask for a place, and the request waits in your Learners tab. A document and its quiz page are one membership — joined and left together.
• Public — anyone with the link, once they sign in to answer. Public documents and quizzes are on Pro; a blog is always public, and its readers Subscribe to it rather than join.

A page's Settings also hold its icon and colour, Require approval, the Brief its agents read, the page's Language (stated there, fixed at Create), and a confirmed Remove. Documents, blogs and quiz pages lay them out the same way.

Adding learners

Add learner is page-first: pick the page, then say who. What you type decides the door:

• An email address becomes an invitation. It holds its place on the plan for 7 days, and can be resent or cancelled from the roster.
• An Ebiblo username adds an existing account directly.
• A name alone makes a login code — for a learner without an email. They sign in at ebiblo.com/join with a code like AB-1234, and you can issue a new code any time.

The roster counts "{used} of {cap} places" and filters All · Active · Invited · Requested. Requests from group pages wait under Requested with Approve and Decline; at the cap, the doors give way to Upgrade or Add seats. A learner sees their pages the moment they are added — a page with nothing published yet says so, and opens the day something goes out.

What readers see

A published post is one centred article: the page's name, the title, the writer's byline, the date and reading time, then the text. A document adds its place in the reading order, a contents list and Previous / Next; a blog ends with More posts. On desktop, a contents rail follows the reader down the page — and on a right-to-left page, everything mirrors.

• Blogs are social. Readers Subscribe to a blog (its quiz page comes along), leave a like, and write comments — any signed-in reader can comment, and you can delete any comment on your page. Signed-out readers see it all, read-only.
• Every post is a real web page. A public blog's published post has its own address, title, description and share picture, so it looks right on LinkedIn, X, Facebook or WhatsApp — and search engines and AI assistants can read the article itself.
• Share is built in. The Share menu offers copy link, LinkedIn, X, Facebook, WhatsApp, email, and the device's own sheet where there is one.
• Posts carry topics. Quill suggests up to five topic tags for a post, you keep the ones you want, and they show under the post.

Taking a quiz

1. Open a quiz page from your library, or from a link someone sent you. A shared link asks you to sign in first, so every answer has a name on it — and brings you back to the page you were opening.
2. Pick a published set and press Start. In progress? It says Resume.
3. Answer each question. Choice questions are a tap; written ones have a text box. Your progress is saved as you go, so you can stop on one device and carry on from another.
4. Finish with Submit quiz, and your results appear. Try again is on the page if you want another go — every attempt is kept, so you and the page's owner can both see how each one went.

It works on a small phone screen, with the main button at the bottom where your thumb is.

Reading passages. Some sets start with a passage, as an exam's reading section does. It sits above each of its questions in its own scrolling box, says which questions use it, and folds away on its title when you need the room.

Gaps to fill. Some questions are a text with numbered gaps: type a word in each, or pick it from the gap's list. Case and a closing full stop don't count against you. Most exams mark each gap on its own, so two right out of three still earns two marks; a few (like a two-gap completion) need every gap right.

Matching. Give each item (a paragraph, a statement, a feature) its option from a list. Where an item can take several, you tick across a grid instead. Each row usually earns its own mark.

Number answers. Some questions take one number, marked exactly. Decimals, fractions (3/4), mixed numbers (1 1/2), percentages (25%) and thousands with commas are all read, and a unit sits beside the box. Where a measurement allows it, an answer within a small margin counts.

Math and data. Formulas show as they would on paper, in questions, options and passages. A data set comes as a table in the passage, so you read the numbers beside the question.

Put in order. Move each item up or down, or drag it, until the order is right: paragraphs, the words of a sentence, the steps of a task. If it starts right, press Use this order. Some orders earn a mark for each pair in place; others count only when every item is.

Highlight in text. Tap the words or sentences that answer; tap again to unpick. Some questions take one pick, some several. Where several are right, each right pick earns a mark and each wrong one takes one away.

Mock exams. A mock exam runs in sections, like Reading then Writing, each with its own clock above the question. Finish a section early to move on; its spare time doesn't carry over, and a section that runs out moves on by itself. Once a section is behind you, it's closed.

Listening. Some questions come with a recording above them. Press Play; it can't be paused, and it plays as many times as the exam allows, which is often just once. Answer as you listen. Once the set is marked, the transcript shows and the recording plays freely.

Speaking. Some tasks are answered aloud. Press Record answer: you get time to prepare, then to speak, and it stops by itself. What you say is written down and marked on the exam's scale. You can play your recording back, record again, or Type instead.

Pictures and hot spots. Some questions come with a chart, a map, a diagram or a photo: describe it, label it, or answer about it. On a hot spot, pick the numbered area on the picture that answers; tap a picture elsewhere to see it larger.

Hear about new sets. Press Subscribe under the page's name, and each new set reaches you as it's published. It reads Subscribed once it's on; press it again to stop. It's free. Not signed in yet? It signs you in first, then brings you back to the page.

• For learners — no checking back. Each new set comes to you in your notifications.
• For admins — publish once and your subscribers hear. No new link to send for each set.

Marking and results

• Choice questions are marked the moment the set is submitted. The reason was written with the question, so it is part of what you approved, not something made up afterwards.
• Written answers are marked against the answer you expect, which you can edit while approving. So you set the standard the marking follows. They are scored out of 10, and the reason is shown.
• The results banner shows the overall score, and the score out of 10 for any written answer. Every attempt is kept, with its score and date.

On the quiz page's Admin view, the Attempts card gathers every reader's runs: attempts, people, the average, the median time, and a row per reader that opens into their tries. In-post knowledge checks mark the same way, and show readers how the room did once enough have finished.

On an exam's scale. When a quiz page's Question style is an exam, written answers are marked on that exam's own scale, such as an IELTS band out of 9, with a score for each of its criteria. The results also give an estimated exam score from the auto-marked questions, worked out from published conversion guides. It is a guide to where you stand, never an official score: only the exam itself gives one.

Notifications

Notifications are what stop anyone having to check the app. They arrive in your inbox in Ebiblo — the bell in the header, with an unread badge, live as things happen — and as push notifications on a phone or desktop where you turn them on.

You're told when:

• a draft is ready and waiting for your approval — or went out on its own, where approval is off
• something is published or updated on a page you're on
• a page is shared with you, or someone asks to join yours
• your results are marked, or a learner's results come in
• someone comments on or likes one of your posts

Turn device notifications on in Preferences. On an iPhone, add Ebiblo to your Home Screen first — push reaches iPhones through the installed web app.

The page's language

The interface is English. Menus, buttons and settings read the same for everyone.

A page's language is its own, chosen when the page is created — around ninety to choose from — and fixed from then on. Its agents write everything in it: posts, question sets, knowledge checks, even the suggested topics. The words readers meet around the content — dates, counts, Subscribe, comments, Previous and Next — follow the page's language too.

A page in a right-to-left language — Arabic, Persian, Hebrew, Urdu and others — reads right-to-left end to end, with its own dates and numerals, inside the English interface. Each script wears its own typography, and the writer picks the face from five families made for it. Two pages can run in two directions; nothing leaks between them.

Devices and settings

Ebiblo works in the browser — on a phone, a tablet or a desktop — and can be added to your home screen like an app. Progress is saved as you go, so a learner can start on one device and finish on another.

Press your avatar for the menu: Profile, Preferences, Dashboard for a plan's owner, and Log out.

• Profile — your name, username and birth month.
• Preferences — Appearance (Auto, Light or Dark) and notifications for this device.
• Security — change your password, and delete your account. Deletion is immediate, and offered once nothing on the account can bill again.
• Dashboard — a plan owner's view: Overview, Learners, Tutors, and Plan and billing.

The free plan and paying

Every account starts on the free plan — no card, no time limit. It gives you 1 document, 1 blog and 1 quiz, with 20 agent writes and 10 question sets a month and up to 5 learners. When you reach a limit, Ebiblo says which one and offers the plans.

1. Pick Starter or Pro. Starter is one seat with up to 10 learners on private pages. Pro adds public pages and brings 100 learners with every seat.
2. Pay on Stripe. Your card is entered on Stripe's checkout page and the plan starts at once. Ebiblo never sees the card.
3. Carry on. Change the plan, add seats or cancel any time from the Dashboard; Stripe shows exactly what's due before anything changes. A cancelled plan runs to the end of the period you've paid for.

The owner pays for everyone: one invoice covers every seat and learner, and nobody else enters a card. Prices and the finer points are on pricing.

Paid pages

On Starter or Pro you can charge readers a monthly price for a page: a document, a blog or a quiz page, public, private or group. Stripe pays you. Ebiblo keeps 10%, and Stripe's own fees come out of your share.

1. Set up payouts. On the Dashboard's Plan and billing, Set up payouts takes you to Stripe for your bank details. Ebiblo never sees them.
2. Set a price. In the page's Settings, turn on Paid subscription and enter a monthly price. Readers already subscribed keep the price they joined at.
3. Choose what's paid. Each post, section and set is Free or Paid, under Who reads it below its review bar. New ones on a paid page start Paid.

For readers. A paid post shows its opening, then Subscribe; a paid set says it's for subscribers. Payment is on Stripe's page, and the page opens in full straight after. Manage or cancel any time from Account → Preferences; a cancelled subscription runs to the end of the month paid for.