Archive of implemented ideas

Typstatic 
 Roadmap
TODO: The drawing ‘Perspective of the Regular Bodies: H. III’ by Wentzel Jamnitzer (1568)Contents

Ideas from the roadmap are moved here when they get implemented. They are copied as they are or with minimal editing: the text is not changed to reflect the fact they are behind us and not in front of us. Some details may be out of date.

Implemented in 0.1.0

Change et to tufte-css

It makes more sense, since in the future more Tufte-inspired themes (both for paged and html) might be added.

<details> support

<details> is a relatively little used tag introduced in HTML5. It’s very handy for cases in which longer content is organised under shorter titles, as it allows the reader to glance over what interests them and choose to read only the relevant parts.Examples for use in sites I made: Srigurumi and Hebridge. Both are in Hebrew, but you don’t have to read Hebrew in order to understand the structure.

This bears some common features with stretchtext, although the two are different.

Multilingual sites

Currently there is Typstatic has no concept of translated pages. Adding such a concept might be a breaking change (meaning it might break backward compatibility), but this is important. Themes should be able to take advantage of language indication, so things like directionality, webfonts and verbal elements can be set per language.

Page hierarchy

Many websites have ‘free-floating’ pages which are only loosely connected to other pages thematically or otherwise, as well as pages which form more strict hierarchical clusters where you have a parent page with children, grandchildren, etc.For example, you might have a blog where some posts make a series (linear) or something more complex with subdivisions (a tree). These can make use of optional page hierarchy, where pages can list their children and children can refer back to their parent page.

This feature is also called breadcrumbs.


Backlinks