Matthias Kretschmann
299084de93
* basic astro setup, kick out all gatsby configs * move content folder * src/pages setup * more file reorg * more config updates * more reorgs * refactor * refactor * bump astro * refactor * svg icon build system, theme switch * remark plugin for lead paragraph, more refactor * make images work * post meta * custom Picture component * Pagination, More component, 404 fixes * linking fixes * add table of contents * post actions fixes * tag fixes * content changes * content changes: move media files to their posts * more content moving, remove media folder * refactor remark-lead-paragraph * link css file when defined in post frontmatter * move content up again * kbd post update * allow js * downloads solution * add astro check * redirect_from solution * githubLink solution * reorg * exif solution as prebuild step * exif solution on each post during build * isolate lead paragraph extraction to articles * restore Exif components * deploy script update * fix redirects * xml & json feeds * build fix * fix exif readout in production * head and seo tweaks, add feeds * tweak image display * archive pages with single layout * restore tags archive * sitemap setup * restore thanks page functionality * reorg * cleanup * parallel scripts during prebuild * restore jest setup * remove jest, switch to vitest as test runner * adapt CI * test refactor * typescript tweaks * avatar fixes * typings * restore search functionality * theme switch with nanostores * fixes * test fixes * restore changelog functionality * umami script * border color tweak * related posts with fuse.js * plawright e2e testing setup * search tweaks * simplify typekit loading * photo fix * e2e tests * related posts fix * fix tags archive * tweaks * tweaks * linux snapshots * fix header test * new symlink tactic * fix dev server in codespaces * fix yaml * ci fixes * changelog loading tweaks * e2e against dev server on ci * changelog tweaks * ci tweaks * ci tweaks * ci tweaks * docs updates * ci tweaks * refactor photo creation script * package updates * refactor search * ci tweak * ci tweaks * test tweaks, more unit tests * more unit tests * post creation script tweaks * refactor new scripts, test them for real life * more tests * refactor * codeclimate-action update * uses update * limit ci runs * fix theme toggle, test it * more tests * favicon files cleanup * icon components location change * type checking through ci * command fixes * ci fix * search tweaks * ci tweaks * revised favicons, write post draft about it * drafts filtering fix * lint fix, favicon fixes * copy changes * fix related search images * content updates * new codeblock styles, copy tweaks, fixes * package updates * typing fixes * lint fix * content updates * restore link posts * faster theme switching * split up astro utils * related posts fixes * fix * refactor * fixes * copy tweaks * fixes * picture tweaks * image fixes * feed fixes, adapt for json feed v1.1 * e2e test updates * layout tweaks * update snaphots * migrate to createMarkdownProcessor * ci cache tweaks * activate more browsers for e2e testing * switch to macos-13 images * build caching tweaks * markdown fix * set image quality * remove avif generation * picture tweaks * head fixes * add og:image:alt * create-icons test * new post: Favicon Generation with Astro
3.0 KiB
| title | image | style | author | date | tags | |||
|---|---|---|---|---|---|---|---|---|
| Using <kbd> for fun and profit | ./kremalicious-kbdfun-teaser.png | /post-kbd.css | Matthias Kretschmann | 2012-07-16 14:36:58+00:00 |
|
There's this HTML element meant for marking up keyboard keys named kbd. Obviously it can be styled with CSS so why not use it to make those elements look a bit more like hardware or the iOS and Android software keys.
The above picture might be blurry depending on the device you're using so here's a live rendered demo:
Light Dark iOS An dro id
They are completely styled with CSS3 so they're sharp on all screens no matter how high the dpi. Have a look at the full demo or grab the project folder with the CSS & LESS files from GitHub. The code is under the MIT license so you're free to use it in any personal or commercial project.
Usage
CSS
Just drop in the kbdftw.css in your head:
<link rel="stylesheet" href="kbdfun.css" />
If you want to use the Android key style, include roboto.css before:
<link rel="stylesheet" href="roboto.css" />
<link rel="stylesheet" href="kbdfun.css" />
You also need to add all the Roboto font files from assets/fonts to your project.
LESS
There're some variables in the kbdfun.less file you can customize.
For the Android style, there's roboto.less as include at the end. But the font files won't load unless you uncomment the .font-roboto line in kbdftw.less. This is to make sure, users won't download all the font files if you don't use the Android style.
Markup
The default styling are light keys with Lucida Grande as font:
<kbd>Q</kbd>
becomes Q
Add a dark class to get the dark keys:
<kbd class="dark">Q</kbd>
becomes Q
Adding an ios or android class gives a replica of those system keys. Android uses three different colors on the default keyboard.
<kbd class="ios">Q</kbd>
becomes Q
<kbd class="android">Q</kbd>
becomes Q
<kbd class="android dark">Q</kbd>
becomes Q
<kbd class="android color">Q</kbd>
becomes Q
I've let the default display: inline intact so all padding on the kbd elements won't affect the line-height of the surrounding text. This leads to problems when you want to use them over multiple lines so just make them display: inline-block in this scenario.
Pro Tip: if you want to replicate all Mac keyboards after 2003 you have to get VAG rounded for the font.