Along with a work-in-progress documentation so that developers can take a look and start testing it.

Our first round of testing is promising: rendering is consistent, user settings are reliable—there isn’t a lot of issues to report so far—, we can offer implementers with flexibility since our design approach is strategy-agnostic, and we achieved this in modern and future-proof CSS.

We’d like to take this opportunity to thank the #eprdctn community once again. You provided useful samples and they helped us tremendously.

Implementers, start your (rendering) engines

Although Readium CSS is not production-ready yet, you can at least take a look and maybe experiment with it.

What’s noteworthy:

we tried to make it JavaScript-friendly;

we’re trying to make the transition from Readium to Readium CSS as smooth as possible;

we’ve designed it in a modular way (task-oriented stylesheets), so that you can pick the styles you want to use and generate customized stylesheets out of them;

user settings are strategy-agnostic, you can manage them as you wish, on both the technical and UX sides;

everything can be customized;

it is spec-compliant out of the box (both EPUB 3.1 and CSS snapshot 2017);

it is designed to be compliant with future specs as well.

Please feel free to weigh in the Github repo issues if you’d like to see any specific issue or feature request addressed.

What’s coming next

We’ll focus on testing this prototype, adding support for CJK (Chinese, Japanese and Korean) and RTL (Right-to-left script), and improving paged and scrolled views in the next weeks.

Any feedback and help in those areas will be greatly appreciated. Indeed, we want to get it right so that readers all around the world can feel empowered. And this is the reason why we’ll extend language support as far as we can. But we’ll obviously need your expertise to achieve such a goal.