← All guides
For teachers & handbook authors

Flowcharts for teaching materials, in batches

Writing a course handbook, lecture notes or a distance course, and need dozens of flowcharts in one consistent style? By hand that’s days of work — and if you tweak one code example, you redraw the chart. rombik takes your code files and returns the whole set of standards-compliant charts at once: in batch via API or CLI, with continuous “Figure N” numbering and editable Word export. Here’s how it works.

The author’s pain, not the student’s

A handbook or lecture course needs dozens of flowcharts in one style. Draw them by hand and it’s days of work — and a single tweaked code example means redrawing the chart. rombik generates the whole set from your code files at once.

✓Dozens, not one

A course handbook can carry 30–50 charts. rombik renders them in a single batch, not one screenshot at a time.

✓One consistent style

Every figure uses the same shapes, spacing and layout — built to ДСТУ 19.701-90, so nothing looks glued together from different tools.

✓Change code → re-render

Edited an example between editions? Re-run the batch and the whole figure set updates. No manual redrawing.

✓Editable in the manuscript

Export native Word (.docx) shapes you can nudge and relabel right in the document — not flat pictures.

Generate many at once

Point rombik at your code files (or URLs) and get one bundle back: a multi-page PDF, or a ZIP with one file per figure. Two honest ways to do it.

Command line — the rombik CLI

One command over a folder of examples. Each file becomes its own captioned figure.

rombik batch lecture-*.py \
  --format docx --figStart 1 \
  --out handbook-figures.zip
HTTP API — POST /api/v1/render/batch

1–100 items per call, one credit per rendered figure. Wire it into your own build script.

curl -X POST https://rombik.app/api/v1/render/batch \
  -H "X-API-Key: rk_ВАШ_КЛЮЧ" \
  -H "Content-Type: application/json" \
  -d '{ "items": [
        {"code": "def gcd(a,b): ...", "lang": "python", "name": "gcd"},
        {"url": "https://.../sort.cpp"}
      ], "format": "pdf" }' -o figures.pdf

One numbering across the whole methodichka

Set capWord and a starting number, and every chart is captioned in sequence — «Рисунок 1», «Рисунок 2», «Рисунок 3»… — so the handbook’s figure list stays continuous no matter how many you generate.

start
end
Figure 1 — Linear search
start
end
Figure 2 — Bubble sort
start
end
Figure 3 — Euclid’s GCD

By hand vs in batch

✗By hand
  • ·Days for one handbook
  • ·50 charts drift out of one style
  • ·Redraw everything for the next edition
✓Batch with rombik
  • ·The whole set in one run
  • ·Identical ДСТУ shapes everywhere
  • ·Re-run → figures update in place

Ten languages for any course

Teaching Pascal to first-years, C++ in algorithms, Java in OOP? Mix languages in one batch — the output shapes are identical, so a mixed-language handbook still looks uniform.

PythonCC++C#JavaPascalJavaScriptTypeScriptGoPHP

Common questions

Can I generate many flowcharts at once?

Yes. The batch endpoint POST /api/v1/render/batch and the rombik CLI take 1–100 code files or URLs and return one PDF (a page per figure) or a ZIP with one file per figure.

Will every figure look the same?

Yes — all charts are built to the ДСТУ 19.701-90 (ISO 5807) standard with identical shapes and layout, so a handbook full of them stays visually uniform.

Can figures be numbered continuously?

Set the caption word (Рисунок / Рис. / Figure) and a starting number, and rombik numbers every chart in sequence across the batch — matching your figure list.

Are the charts editable in Word?

Export .docx and the shapes are native Word objects — move and relabel them straight in the manuscript. Visio, PDF, SVG and PNG are available too.

Which languages can I mix?

Ten: Python, C, C++, C#, Java, Pascal, JavaScript, TypeScript, Go, PHP — combine them in one batch without breaking the visual style.

Batch-generate your handbook figures

Preview each chart free, then export the whole set with continuous numbering in the format you need.

Try it on your code