kirby3 plugin to provide a tag (badge) to make badges
Open Issues: 2
- php: >=7.1
- badges/poser: ^1.2
- getkirby/composer-installer: ^1.1
- getkirby/cms: ^3.0.1
- jakub-onderka/php-parallel-lint: ^1.0
- localheinz/composer-normalize: ^1.0.0
- omz13/omz13-coding-standard: dev-master
- phpcompatibility/php-compatibility: ^8.2
- phpmd/phpmd: ^2.6
- phpstan/phpstan: ^0.10.3
- phpstan/phpstan-strict-rules: ^0.10.1
- roave/security-advisories: dev-master
This package is auto-updated.
Last update: 2023-01-08 22:32:08 UTC
Requirement: Kirby 3
Coffee, Beer, etc.
This plugin is free. However, to show your support, especially if using it in a commercial project, you are welcome (greatly encouraged) to:
For a Kirby3-powered site, this plugin (omz13/badges) provides a KirbyTag (called
badge) that allows badges to be rendered in a page.
- This plugin is a convenience wrapper around PHP Badges Library.
- No configuration is really necessary as it comes with sensible defaults.
- The render style can be specified in the configuration file and overridden on a per tag basis.
- The color for the value can be specified in the configuration file and overridden on a per tag basis.
- There are sensible defaults if you forget to provide the necessary key and/or value data in a tag.
- The badge is rendered locally, provided as a SVG image, and wrapped in a
<div>with an optional
The non-binding list of further features and implementation notes are:
- Page-level function
- Put a joke or two into README
- Use the word epistemological in README to confuse everybody (except people who do or have done philosophy or art history).
Pick one of the following per your epistemological model:
composer require omz13/kirby3-badges; the plugin will automagically appear in
- Download a zip of the latest release - master.zip - and copy the contents to your
git submodule add https://github.com/omz13/kirby3-badges.git site/plugins/kirby3-badges.
For the record: installation by composer is cool; supporting installation by zip and submodule was an absolute pain, especially as I am an installation by composer person, so do feel guilted into getting me Coffee, Beer, etc., because this is for your benefit and not mine (and yes, I would have have preferred to spend my time somewhere warm and sunny instead of being hunched over a keyboard while the snow falls outside and the thermometer shows no inclination to get above 0C).
The following mechanisms can be used to modify the plugin's behavior.
In your site's
site/config/config.php the following entries prefixed with
omz13.badges. can be used:
style- optional - the name of the rendering style to apply.
Possible values are:
flat(default if not specified)
color- optional - the name or RGBHEX value to be used for the badge's name.
If not specified,
class- optional - the code for the badge will be wrapped in a
<DIV>with a classname specified here.
If not specified, the
<DIV>wrapper has no class.
<?php return [ 'omz13.badges.style' => 'plastic', 'omz13.badges.class' => 'badge', ], ];
"(badge:" key value [ color [ "style:"style ] ] ")"
When writing content, this plugin provide a new tag,
badge, which has two mandatory parameters that specify the
value for the badge; an optional third parameter specifies the color for the value, either as a named color (e.g.
red) or a RGBhex (e.g.
An optional attribute of
style can be used to override the default style (c.f.
style in Configuration).
Parameters can be separated by spaces (
,), or semicolons (
key is not supplied, then
??? will be used.
value is not supplied, then
??? will be used.
Use the (implicit) style from the configuration, or explictly set:
- (badge: style, implicit - from configuration) - (badge: style, explicit flat style:flat) - (badge: style, explicit plastic style:plastic) - (badge: style, explicit flat-square style:flat-square)
Applying some color:
- (badge: copyright ; public domain ; green ) - (badge: stability: unstable orange) - (badge: licence MIT) - (badge: statis YES yellow)
Missing key and/or value:
- (badge:) - (badge: wibble)
This plugin is provided "as is" with no guarantee. Use it at your own risk and always test it yourself before using it in a production environment. If you find any issues, please create a new issue.
You are prohibited from using this plugin in any project that promotes racism, sexism, homophobia, animal abuse, violence or any other form of hate speech.