No Lesson Ten Blocks Cannot Build: Getting the Most Out of the Block Editor

When you flip between a document tool, a survey tool, and a doc full of video links just to build one set of materials, you end up thinking about 'which tool do I build this in' before 'what am I teaching.' The more tools, the busier the screen, and when it comes time to hand things out, the links split into several. The flashier the authoring tool, the more time goes into learning its features, and often there is no energy left for designing the lesson itself. Good lesson materials are good not because they have many features, but because the activities you need run in one connected flow. The problem is that this 'connecting' is the most tedious job in most tools.

Why splitting into blocks makes it easier

A lesson is really a combination of a few activities. Keep those activities as small blocks and the design gets simple.

1. Explanation blocks: heading, text, callout, and code carry the concept. Pull whatever needs emphasis out into a callout.
2. Source blocks: image and YouTube embeds drop visuals and video right into the material.
3. Activity blocks: short answer, written response, and file submission take students' responses on the spot.

However varied lesson formats look, it comes down to which few kinds of blocks you stack, and in what order.

Changing the shape of a lesson by recombining blocks

Flipsson, from Nallijaku, assembles these blocks by dragging, so the same materials can become an entirely different lesson. It runs in the browser with nothing to install, and changing only the order changes the character of the lesson.

For a lecture-style lesson, stack heading, text, YouTube, and short answer to make an explain-then-check flow. For inquiry, lead with a written response block so students write their thinking first and only then tidy it up with an explanation block, flipping the order so the question comes first and the concept follows. For hands-on work, run a code block into a file submission block so students look at an example and upload their result immediately. For a presentation lesson, attach materials with image blocks and take the product through a file submission block, holding everything from prep to hand-in on one screen. Assignment blocks let you set a character limit, whether a response is required, and which file types are allowed with a click, so you can nail the conditions down right there without a separate survey tool. Small moves like binding the key point visibly into a callout, or laying an example out neatly in a code block, are enough to change how finished the material feels.

Nor do you have to rebuild the same pieces over and over. Save a combination that works to the library, then reuse it in the next unit by changing only the block order. Store the opening callout or the check-for-understanding task you use often as its own small module, and a period comes together simply by pulling pieces out and assembling rather than stacking from scratch. Add the real-time submission cards of a live lesson and the instant a student answers an assignment block inside the material it surfaces as a card, so building, distributing, and checking all finish on one screen.

The short version

The power of a block editor is not in the number of blocks but in the freedom of combination. Depending on the order you stack about ten kinds of blocks, lecture, inquiry, and hands-on lessons all get built inside one tool. It starts without a credit card and is free for up to 10 classes, so I would suggest starting with a single period: rebuild a unit you have always taught, in blocks.