Prompt 13: CUTE - examples: Difference between revisions

From Reuse
Jump to navigationJump to search
No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
The CUTE, “Conditions d'utilisations typographiques engageantes” (engaging typographic conditions for use) were developed between 2022 and 2024 by '''Bye Bye Binary'''. The Franco-Belgian collective is invested in proliferating a specific post-binary typographic practice. The CUTE stipulates under which conditions the fonts can be used and modified. CUTE sparked two prompts (see Prompt 01 and 02) and '''Bye Bye Binary''' sent later a third one.
The CUTE, “Conditions d'utilisations typographiques engageantes” (engaging typographic conditions for use) were developed between 2022 and 2024 by '''Bye Bye Binary'''. The Franco-Belgian collective is invested in proliferating a specific post-binary typographic practice. The CUTE stipulates under which conditions the fonts can be used and modified. CUTE sparked two prompts (see [[Prompt_01:_CUTE_-_donations|Prompt 01]] and [[Prompt_02:_CUTE - packets|Prompt 02]]). '''Bye Bye Binary''' sent a third one.


<div class="prompt">
<div class="prompt">
During the process of writing CUTE, Bye Bye Binary did several reading sessions of the CC4r. They were inspired by "emancipatory" perspective. But some members felt that it was sometimes too opaque and that more people could access the CC4r if it was more promptly understandable.
During the process of writing CUTE, Bye Bye Binary did several reading sessions of the CC4r. They were inspired by its paradigmatic shift on free licenses and its intersectional perspective. But some members found the language sometimes opaque, and believe that more people could learn from and use the CC4r if its wording was more accessible. How could the language of CC4r become more accessible and instructive without giving up on complexity? In the CUTE we decided to include examples to help with that. Could this work for CC4r too?
</div>


Could the CC4r text become more accessible and instructive without giving up on complexity? I CUTE we decided to include examples to be less abstract. Could this work for CC4r as well?
Source: Bye Bye Binary, CUTE (Conditions d’Utilisations Typographiques Engageantes V.01), 2024. [[:File:Cute.pdf|Download PDF]]
</div>
 
[[Category:Prompts]]

Latest revision as of 09:20, 30 April 2024

The CUTE, “Conditions d'utilisations typographiques engageantes” (engaging typographic conditions for use) were developed between 2022 and 2024 by Bye Bye Binary. The Franco-Belgian collective is invested in proliferating a specific post-binary typographic practice. The CUTE stipulates under which conditions the fonts can be used and modified. CUTE sparked two prompts (see Prompt 01 and Prompt 02). Bye Bye Binary sent a third one.

During the process of writing CUTE, Bye Bye Binary did several reading sessions of the CC4r. They were inspired by its paradigmatic shift on free licenses and its intersectional perspective. But some members found the language sometimes opaque, and believe that more people could learn from and use the CC4r if its wording was more accessible. How could the language of CC4r become more accessible and instructive without giving up on complexity? In the CUTE we decided to include examples to help with that. Could this work for CC4r too?

Source: Bye Bye Binary, CUTE (Conditions d’Utilisations Typographiques Engageantes V.01), 2024. Download PDF