About

Why this exists, and why I am building it.

Why ScribeBloc exists

ScribeBloc began with a simple problem: information can be available, accurate and technically accessible — and still be difficult to use.

A document can contain the answer and still make someone work too hard to find it. A webpage can meet a technical standard and still be confusing. A student can have all the material they need and still struggle to turn it into something they can study from.

The gap between information being available and information being usable is where ScribeBloc began.

Why I am building it

My background is in helping people navigate complex information. As a university librarian, I taught students how to find, evaluate and use research. Later work has included digital content, accessibility, , design and AI-enabled content systems.

I have also contributed to AI content governance and publishing. That work sharpened my focus on trustworthy AI-assisted content, human review, source fidelity and the risk of unsupported generated material.

My web development and AI architecture experience means I can build and operate the first ScribeBloc engine myself. What I learn from users can feed directly into the next information journey, workflow or test without waiting for an external development cycle.

Across these experiences, the same issue kept appearing: access to information is not the same as being able to use it.

How it is designed

There is no average reader

People differ in knowledge, language, attention, time, device, context and purpose. One standard version cannot work equally well for every person, situation and task.

  • KnowledgeWhat someone already knows about the subject
  • LanguageReading in a first, second or third language
  • AttentionFocused, interrupted, or exhausted
  • TimeTen minutes, or a full study session
  • DeviceA phone on a train, or a desktop at work
  • ContextRevising, deciding, checking or acting
  • PurposeWhat the information is actually needed for

ScribeBloc restructures information around what the person needs it for, rather than assuming everyone can adapt to a “standard” version.

Accessibility should be considered a baseline. Usability is our goal.

matter. For universities and other organisations, WCAG conformance, screen-reader compatibility, readable typography, layout and mobile usability are essential baselines.

This approach is informed by : designing for human variation from the beginning. The same source may need to work differently for different people and tasks.

One engine. Different information journeys.

Accessibility is one path among several — alongside plain language, study-ready structure, translation and other fit-for-purpose versions. One underlying restructuring engine, instead of a separate product for every audience.

Where ScribeBloc is now

ScribeBloc is in development and customer discovery.

The aim is simple: you bring the source, you get something you can actually use, and you can see what changed.

See a worked example — a spoken law lecture restructured into study-ready notes.

References

The sources behind the terms used on this site. These links leave ScribeBloc.

Get in touch

If you have information that is hard to use, or you want to follow the build, email [email protected].