Ecodesign topics to tackle

[pylapp]

Context

One of the pilar of OUDS (with open source and trials to be unisifed and cohesive kof kof) is the ecodesign.
However this technical topic is not always aligned with design and stake holders visions.
Here are lsit of topics to tackle.

Topics

Use of fonts

Some themes embed or can embed non-native fonts. For example Wireframe uses Chalboard, Sosh its font, Parnasse also, and Orange can use for France other fonts.
But it increases the size of the libs if we add TFF or WOFF2 files.
For Wireframe the font in use is also available natively, so it can be replaced by this one.
But for others, no.

Note

A workaround will b to let users load their fonts

Countries images for phone number input

One component of OUDS is the phone number input, i.e. an input text field with a selector of country with flags.
Technical team suggested to use emojis to avoid embeding country flags images, but design team refuses as emojis are bad, not relavant and not aligned with "flat" design.
So we need a workaround to provide a component with enough flexilibility.

Note

Maybe let users give closures in components to provides business objets with countrys flags, prefix, palcehollders and regex for validation.
Thus component by design will be agnostic.
And add code samples for users of they want PhoneNumberKit or use archives of images.

Number of tokens

We have today thousands of raw, component and semantic tokens. They are public variables icnreasing the memory footprint.
Indeed we use in the end raw types to avoid to have big ones, and type alaises to point to theses raw types.
But number of tokens is still big.

Note

Reduce the number of tokens can be interesting, but the effort must be done in design team.

See #1180