Using Kirby-Typography should not be limited to Kirbytext or by utilizing the Smartypants component. In Some cases, you want to use different settings for different fields and/or in different sections of a template (see #7).
Kirby-Typography should provide methods utilizing the plugin directly:
typography($text, $settings = []);
This should always be based a language’s default settings with the possibility to override them using the $settings parameter. It could also be possible to define presets in the config file, which can then be used in templates by providing a string instead of an array for $settings.
Using Kirby-Typography should not be limited to Kirbytext or by utilizing the Smartypants component. In Some cases, you want to use different settings for different fields and/or in different sections of a template (see #7).
Kirby-Typography should provide methods utilizing the plugin directly:
This should always be based a language’s default settings with the possibility to override them using the
$settingsparameter. It could also be possible to define presets in the config file, which can then be used in templates by providing a string instead of an array for$settings.