# keyboard Published articles for keyboard. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 20140622 release DevFeed: [Libreboot 20140622 release]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [Documentation](), [coreboot]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [documentation](), [free-software](), [grub](), [keyboard](), [layout](), [libre](), [libreboot](), [opensource](), [release](), [thinkpad](), [uefi](), [version]() ### AI overview The Libreboot 20140622 release supports the ThinkPad X60 and X60s. It adds and improves documentation, updates GRUB, adds keyboard-layout ROM images, reorganizes files, improves build-script comments, and includes SHA-512 checksum files. ### Source excerpt Article: Libreboot 20140622 release Web link: https://libreboot.org/news/libreboot20140622.html ## Haiku Activity & Contract Report, August 2026 DevFeed: [Haiku Activity & Contract Report, August 2026]() Original publisher: [Read original article]() Author: waddlesplash Published: 2026-09-10T20:00:00Z Content type: article Language: en Sources: [Haiku Project]() Topics: [systems](), [App](), [Bluetooth](), [Command-line interface](), [cpu](), [keyboard](), [MIDI](), [USB]() Tags: [2026](), [activity-report](), [application](), [authentication](), [bluetooth](), [command-line](), [contractor](), [cpu](), [keyboard](), [report](), [sorting](), [usb]() ### AI overview Haiku's August 2026 activity and contract report covers revisions hrev59922 through hrev60059 and notes the R1/beta6 release. It summarizes fixes and improvements across applications, command-line tools, system kits, and servers, including Tracker, authentication in su, Intel CPU branding, Bluetooth support, MIDI endpoints, and media output switching. ### Source excerpt This report covers hrev59922 through hrev60059. The main news, of course, is that R1/beta6 was released last month. You can read the announcement for more details. Many of the changes in this report made it into R1/beta6 (but not all of them.) Applications waddlesplash fixed a file-descriptors leak in Tracker's query code, fixing a number of open tickets. jscipione changed Tracker to not start editing file names while dragging, re-enabled sorting of poses when adding is completed, implemented undo of creating new files from templates, made the drag-and-drop context menu live-updating, and more. aquamatic continued work on the Devices application. (You can read more about that in his final report.) humdinger also made a small patch to use a translatable application name. humdinger fixed the background of the optional package list in Installer. jscipione fixed the Deskbar preferences window incorrectly moving the Deskbar itself when it was opened in certain modes. madmax fixed a Deskbar crash when applications quit very soon after launching. nephele and jscipione fixed ProcessController to load the "Power saving" setting when started, instead of when the menu is first opened. jscipione updated the Apple keyboard layouts used in Keymap preferences to the "Apple Magic" layouts. Command line tools waddlesplash fixed a number of authentication problems in su. Kits KevinAdams improved Intel CPU "brand strings" detection some more, trimming more extraneous details off the strings displayed in AboutSystem. przemub fixed a crash in the Locale Kit when a time unit formatter failed to initialize. jscipione fixed some minor issues in spinner button drawing. waddlesplash refactored BBitmap to use 64-bit-safe types. This allows for bitmaps over 2GB in size on 64-bit systems, but it also allows for an application's total size of all bitmaps to go over 2GB, which wasn't properly supported before either. Servers mohammedrattia continued work on Bluetooth HID support. (You can read mo ## A Dialog Can Now Be a Native Desktop Window DevFeed: [A Dialog Can Now Be a Native Desktop Window]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-05T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [dialog](), [Accessibility](), [Operating system](), [macOS]() Tags: [accessibility](), [bug](), [can](), [code](), [component](), [desktop](), [dialog](), [keyboard](), [macos](), [native](), [release]() ### AI overview Codename One adds an option for dialogs to open as native modal desktop windows while retaining lightweight in-window dialogs. The release also fixes top-level window ownership and updates focus, input routing, repainting, popup behavior, and accessibility handling across separate windows. ### Source excerpt Codename One dialogs can stay inside a secondary window or become native modal windows, while sheets, popups, overlays, tooltips, HTML, and accessibility now resolve the correct top level. ## I had two weeks, an 8-foot keyboard, and a Wordle Workflow DevFeed: [I had two weeks, an 8-foot keyboard, and a Wordle Workflow]() Original publisher: [Read original article]() Author: Shy Ruparel Published: 2026-07-21T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Development](), [keyboard](), [Figma]() Tags: [conference](), [figma](), [game](), [keyboard](), [temporal-voices](), [usb]() ### AI overview Temporal describes building and presenting a Wordle clone driven by Temporal Workflows, using an 8-foot USB-C keyboard and holographic fans to demonstrate durable execution at AI Engineer World's Fair. ### Source excerpt A Wordle clone, an 8-foot keyboard, and a holographic fan display made Temporal's Durable Execution visible at AI Engineer World's Fair. ## Generate editorial React presentations with one Claude Code prompt DevFeed: [Generate editorial React presentations with one Claude Code prompt]() Original publisher: [Read original article]() Author: Ishan Khanna Published: 2026-05-17T08:17:35Z Content type: tutorial Language: en Sources: [Ishan Khanna]() Topics: [Claude Code](), [React](), [Code](), [Large Language Model](), [Tailwind CSS](), [Vite]() Tags: [animation](), [architecture](), [claude-code](), [code](), [how-to](), [keyboard](), [llm](), [llms](), [presentation](), [prompt](), [prompting](), [react](), [tailwind](), [vite]() ### AI overview A tutorial presents a detailed Claude Code prompt for generating five-slide React presentations as a single Presentation.jsx file. The prompt fixes the design system and narrative structure while allowing the topic content to change, and the result can be used in a Vite, React, and Tailwind project. ### Source excerpt If you caught my YouTube Short on generating presentations as React apps with an LLM, this is the prompt I promised. Paste it into Claude Code, edit the CONTENT block at the top, and you get back a single-file Presentation.jsx -- five slides, keyboard nav, animated counters, an ## More Accessible Focus Indicators with Compose DevFeed: [More Accessible Focus Indicators with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-04-30T07:11:56.799000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [Accessibility](), [Android](), [Web Content Accessibility Guidelines](), [keyboard]() Tags: [accessibility](), [accessible](), [android](), [compose](), [focus](), [jetpack-compose](), [keyboard](), [web-content-accessibility-guidelines]() ### AI overview A tutorial on creating more visible keyboard focus indicators in Jetpack Compose. It explains relevant WCAG Focus Appearance requirements, notes that Android's default ripple may be insufficiently visible, and introduces the Indication API for drawing custom indicators such as an underline on focused interactive components. ### Source excerpt Last summer, I wrote a blog post about focus management with Compose. Ever since, I've had drafts of this post, but I didn't get to finalize it until now. The blog post is available in: It's All About (Accessibility) Focus And Compose. So, in this blog post, we're talking about focus indicators and how to make them more accessible with Compose. But let's first talk about focus indicators in general. Focus Indicators Focus indicators are, as the name suggests, indicators that show where keyboard focus currently is in the UI. They need to be visible so that keyboard and keyboard-emulating device users can navigate around the app effortlessly. An important thing to note is that the focus indicator I'm talking about here is not for the screen reader (e.g., TalkBack) focus. That is handled on the system level. Web Content Accessibility Guidelines (the standard behind accessibility legislation and used with apps as well, despite the name) has some requirements for accessible focus indicators. Per SC 2.4.13 Focus Appearance, the focus indicator needs to be either User agent's (Android system) default styles At least 2 pixels thick and has a contrast ratio of at least 3:1 between the same pixels of focused and unfocused states. Android's default focus indicator is the ripple, which isn't very visible. Technically, it would pass, but if you want to make the application accessible, you'll need to improve the visibility of the focus indicator. Let's next discuss one way to build more visible (and thus, more accessible) focus indicators with Compose. Building More Accessible Focus Indicators with Compose There are several ways of creating the focus indicators. You can, for example, add a border based on the focused state, as Appt.org suggests in their code snippets: Accessibility focus indicator in Jetpack Compose, but if you want anything more complex, you'll want to turn to Indication API. Indication API with a DrawModifierNode can be used to draw complex focus indicators. In ## Why Is WCAG Level AA the Standard for Digital Accessibility? DevFeed: [Why Is WCAG Level AA the Standard for Digital Accessibility?]() Original publisher: [Read original article]() Author: Mark Published: 2026-03-06T16:56:18Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Accessibility](), [Web Content Accessibility Guidelines](), [digital accessibility](), [Web Accessibility (a11y)](), [Usability]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-requirements](), [color](), [compliance](), [digital-accessibility](), [keyboard](), [readability](), [usability](), [wcag](), [web-content-accessibility-guidelines]() ### AI overview This article explains why WCAG Level AA is commonly used as the goal for digital accessibility. It contrasts Levels A, AA, and AAA, describing Level A as a baseline and highlighting Level AA requirements such as color contrast and visible focus. ### Source excerpt When you're building an accessibility initiative, it's a good idea to establish your goals up front -- and most accessibility experts will tell you that means seeking Level AA conformance with the Web Content Accessibility Guidelines (WCAG). ## Adding Navigation support to Large Content Viewer with Compose DevFeed: [Adding Navigation support to Large Content Viewer with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-02-28T04:26:46.364000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Jetpack Compose](), [navigation](), [Compose](), [keyboard](), [screen](), [Code]() Tags: [code](), [compose](), [keyboard](), [navigation](), [screen](), [test]() ### AI overview This tutorial explains how to add keyboard and assistive-technology navigation to a large content viewer built with Jetpack Compose. It presents an approach using focus handling to show item previews, covers keyboard and screen reader navigation, and discusses voice access support. The author notes that the example is a demo and should be tested with users of assistive technologies before production release. ### Source excerpt In my previous blog post, Beyond Font Scaling: Large Content Viewer with Compose, I explained how to build a large content viewer from iOS using Jetpack Compose. The implementation did not include support for keyboard or other assistive tech navigation, so this blog post tackles those topics. A disclaimer: The way I'm presenting the support for assistive tech navigation in this blog post is one approach, and my goal is to provide examples and context, but as always, this is a demo project. In your production app, things might get a bit more complicated, and you might need to handle more variables. So always remember to test the solution, ideally with your users who use assistive technologies. And I hope it goes without saying: Before releasing to production. In this blog post, I'm presenting code for keyboard and screen reader navigation, then sharing some considerations for voice access support. The code relies heavily on the code presented in the previous blog post, so if you have questions about it, please check that post. A link for the full code is also provided at the end of the blog post. Keyboard Navigation Support The pointer input implementation presented in the previous blog post relies on long-press, but keyboard navigation doesn't support that kind of interaction, so we need another tactic to display the item preview. With a keyboard, focusing on an item is a natural choice, so we're going to use that. The idea is that when a user who navigates with a keyboard or a keyboard-emulating device focuses on a bottom bar item for the same duration as a long press, we will show the item preview. We can do this with the following code: NavigationBarItem( modifier = Modifier .onFocusChanged { if (it.isFocused) { scope.launch { delay( viewConfiguration.longPressTimeoutMillis ) previewedItem = item } } else { previewedItem = null } }, ... } We use the onFocusChanged-modifier. Its state indicates whether the current element is focused via it.isFocused. If it is, we ## Everything we shipped at Sketch in 2025 DevFeed: [Everything we shipped at Sketch in 2025]() Original publisher: [Read original article]() Author: Freddie Harrison Published: 2025-12-16T08:00:00Z Content type: article Language: en Sources: [Sketch Blog]() Topics: [Sketch](), [releases](), [liquid glass](), [User interface design](), [macOS](), [iOS]() Tags: [2026](), [apple](), [apps](), [auto-layout](), [icons](), [ios-26](), [keyboard](), [latest-features](), [layout](), [liquid-glass](), [macos](), [releases]() ### AI overview Sketch reviews its 2025 product work, including the Athens, Barcelona, and Copenhagen releases. The updates introduced Stacks and Frames, expanded the Command Bar, added a glass effect for iOS and macOS 26 design, and included an MCP server and broader redesign work. ### Source excerpt From Stacks and Frames, to Glass effects and a complete macOS Tahoe redesign -- here's everything we shipped at Sketch in 2025. ## Mob Programming: Smells Like Team Spirit DevFeed: [Mob Programming: Smells Like Team Spirit]() Original publisher: [Read original article]() Author: Dmytro Kurets Published: 2025-12-04T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [Programming](), [Code](), [pull-requests](), [Back end](), [Front end](), [Data analysis](), [Refactoring]() Tags: [back-end](), [code](), [collaboration](), [data-analysis](), [engineering](), [engineering-culture](), [front-end](), [keyboard](), [pairing](), [programming](), [review](), [team]() ### AI overview The article explains mob programming as structured, shared-focus collaboration with one driver, rotating typing roles, and navigators guiding the work. It describes a trivago team experimenting with collaborative review and coding changes to address pull requests piling up and slowing delivery. ### Source excerpt Mob programming often sparks hot takes. "It's counter-productive." "One person could do it faster." "Why waste five people on one keyboard?" If that's what it looks like in your head--one senior ... ## 10 UI fixes I shipped in 10 days DevFeed: [10 UI fixes I shipped in 10 days]() Original publisher: [Read original article]() Author: Dmytro Tovstokoryi Published: 2025-12-01T00:00:00Z Content type: article Language: en Sources: [Mintlify Blog]() Topics: [ui](), [User experience (UX)](), [User interface design](), [Accessibility](), [navigation](), [dashboards]() Tags: [accessibility](), [dashboards](), [engineering](), [interaction](), [keyboard](), [layout](), [navigation](), [ui](), [ux]() ### AI overview A Mintlify design engineer describes 10 UI improvements shipped over 10 days, addressing layout shifts, dynamic number widths, dropdown animation origins, input focus behavior, navigation interactions, and keyboard accessibility. ### Source excerpt Little details are what make UX so good you don't notice it. ## Standardize with ⌘ O ⌘ P to reduce cognitive load DevFeed: [Standardize with ⌘ O ⌘ P to reduce cognitive load]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-11-01T00:38:50Z Content type: opinion Language: en Sources: [Kaushik Gopal's Site]() Topics: [macOS](), [Obsidian](), [Android Studio](), [IntelliJ IDEA](), [cursor](), [ide]() Tags: [android-studio](), [cognitive-load](), [cursor](), [ide](), [intellij](), [keyboard](), [macos](), [notes](), [shortcuts]() ### AI overview The author recommends standardizing ⌘ O for opening a file or note and ⌘ P for opening a command palette across macOS apps such as Obsidian, Android Studio, IntelliJ, and Cursor. They report that using consistent shortcuts reduces the need to remember app-specific commands and helps build muscle memory. ### Source excerpt There are a few apps on macOS in the text manipulation category that I end up spending a lot of time on. For example: Obsidian (for notes), Zed (text editor + IDE lite), Android Studio & Intellij (IDE++), Cursor (IDE + AI), etc. All these apps have two types of commands that I frequently use: Open a specific file or note Open the command palette (or find any action menu) But by default, these apps use ever so slightly different shortcuts. One might use ⌘ P, another might use ⌘ ⇧ P, etc. I've found it incredibly helpful to take a few minutes and make these specific keyboard shortcuts the same everywhere. So now I use: ⌘ O - Open a file/note ⌘ P - Open the command palette (or equivalent action menu) This small change has reduced cognitive load significantly. I no longer have to think about which app I'm in, and what the shortcut is for that specific app. Muscle memory takes over, and I can just get things done faster. Highly recommended! ## Why modal editing became associated with Vim DevFeed: [Why modal editing became associated with Vim]() Original publisher: [Read original article]() Author: Hillel Wayne Published: 2025-10-21T16:46:24Z Content type: article Language: en Sources: [Newsletter feed for Hillel Wayne's Newsletter]() Topics: [Vim](), [GUI]() Tags: [keyboard](), [shortcuts](), [vim]() ### AI overview The article explains modal editing, focusing on how Vim uses modes to assign different functions to the same keys. It argues that modal editing's popularity likely followed from vi's historical success rather than from an obviously superior feature. ### Source excerpt A while back my friend Pablo Meier was reviewing some 2024 videogames and wrote this: I feel like some artists, if they didn't exist, would have the resulting void filled in by someone similar (e.g. if Katy Perry didn't exist, someone like her would have). But others don't have successful imitators or comparisons (thinking Jackie Chan, or Weird Al): they are irreplaceable. He was using it to describe auteurs but I see this as a property of opportunity, in that "replaceable" artists are those who work in bigger markets. Katy Perry's market is large, visible and obviously (but not easily) exploitable, so there are a lot of people who'd compete in her niche. Weird Al's market is unclear: while there were successful parody songs in the past, it wasn't clear there was enough opportunity there to support a superstar. I think that modal editing is in the latter category. Vim is now very popular and has spawned numerous successors. But its key feature, modes, is not obviously-beneficial, to the point that if Bill Joy didn't make vi (vim's direct predecessor) fifty years ago I don't think we'd have any modal editors today. A quick overview of "modal editing" In a non-modal editor, pressing the "u" key adds a "u" to your text, as you'd expect. In a modal editor, pressing "u" does something different depending on the "mode" you are in. In Vim's default "normal" mode, "u" undoes the last change to the text, while in the "visual" mode it lowercases all selected text. It only inserts the character in "insert" mode. All other keys, as well as chorded shortcuts (ctrl-x), work the same way. The clearest benefit to this is you can densely pack the keyboard with advanced commands. The standard US keyboard has 48ish keys dedicated to inserting characters. With the ctrl and shift modifiers that becomes at least ~150 extra shortcuts for each other mode. This is also what IMO "spiritually" distinguishes modal editing from contextual shortcuts. Even if a unimodal editor lets you change a k ## Appending Text to Obsidian via Shortcuts DevFeed: [Appending Text to Obsidian via Shortcuts]() Original publisher: [Read original article]() Author: Rob Published: 2025-10-14T10:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [Obsidian](), [context]() Tags: [apple](), [automate](), [dialog](), [keyboard](), [mac](), [obsidian](), [schema](), [shortcuts]() ### AI overview This tutorial explains how to use Apple Shortcuts and Obsidian's obsidian:// URI schema to append text to the current Obsidian daily note. The shortcut prompts for text, adds the current time as a heading, URL-encodes the content, and opens the URI with the append parameter. ### Source excerpt Sometimes it's helpful to add some text to my current Obsidian daily note without having to switch to Obsidian, find the daily note and then type my text. To do this, we can use the magic of Obsidian's obsidian:// URI schema and automate the text capture in Apple Shortcuts, with an assigned keyboard shortcut to activate it. This is the Shortcut: There's a number of steps in the Shortcut. Firstly we Ask For some text... continue reading. ## Hidden Gems: Part 1 DevFeed: [Hidden Gems: Part 1]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2025-10-07T00:00:00Z Content type: tutorial Language: en Sources: [Zed Industries - Blog]() Topics: [Programming](), [ui](), [Vim](), [Rust]() Tags: [features](), [keyboard](), [rust](), [ui](), [workflows]() ### AI overview This article introduces hidden features and workflows in Zed, including command palette actions, customizable keybindings, Rust testing workflows, context-menu features, project-panel comparisons, and a focused writing setup. ### Source excerpt Favorite workflows and hidden features from the Zed team and community. ## Live Templates in Android Studio DevFeed: [Live Templates in Android Studio]() Original publisher: [Read original article]() Author: Segun Famisa Published: 2025-07-17T06:00:00Z Content type: tutorial Language: en Sources: [Segun Famisa]() Topics: [Android Studio](), [Kotlin](), [ide](), [IntelliJ IDEA](), [Code]() Tags: [android](), [android-studio](), [code](), [ide](), [intellij](), [jetbrains](), [keyboard](), [kotlin](), [shortcuts](), [tests](), [workflow]() ### AI overview This tutorial explains IntelliJ-based IDE live templates, with a focus on creating a custom Android Studio template for Kotlin test functions that use backticks. It describes the template settings, applicable context, abbreviation, description, and template variables. ### Source excerpt If you are already familiar with live templates, feel free to skip to the live template for kotlin tests If you use IntelliJ-based IDEs like Android Studio, WebStorm, etc., chances are that you have seen some kinds of "shortcuts" (pictured below) show up when you press some key combinations. These are called live templates. For example, if you type sout in a Java/Kotlin file, you see a pop-up like the one above. When you press tab, it autocompletes into System.out.println (in Java) or println in Kotlin. Live templates allow you to generate common code constructs by typing keywords that trigger the template. This feature is not new, and I definitely remember seeing it in the Netbeans IDE when I developed J2ME applications. If, like me, you write a lot of Android code in Android Studio, you may also know that if you type comp in a Kotlin file and press the tab key, a composable function is generated. I have personally found these templates extremely useful for developing faster, and I use them all the time. I even have a few of my own templates, and one of them is the main reason I am writing this article. -- Live Template for Kotlin tests One of the things I do almost every day when I write code is write tests. If you use Kotlin, you might know that backticks are allowed in test function names. I like to optimise my workflow, and I realised this was an opportunity to save myself a few keystrokes for every test I write. I ended up writing a live template to automatically create a test function with backticks (does anyone else find the backtick key awkwardly placed on the keyboard?). To set this up, I follow the instructions on JetBrains' website. You can do the same: CMD + , to open settings Navigate to Editor > Live Templates Select Kotlin group (the templates are usually grouped, but you can also create your own group if you so please) Click on the little + button or CMD + N , and select 1 or Live Template Now we can begin to set the details for the live template. Th ## Understanding Accessibility Focus and Keyboard Focus in Android Compose DevFeed: [Understanding Accessibility Focus and Keyboard Focus in Android Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2026-04-30T03:53:43.294000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Compose](), [Android](), [User interface design]() Tags: [accessibility](), [android](), [compose](), [interaction](), [keyboard](), [screen]() ### AI overview This tutorial explains the difference between accessibility focus used by screen readers such as TalkBack and keyboard focus used with keyboards, D-pads, and similar devices in Android Compose. It describes which elements can receive each type of focus and gives guidance on making touch-interactive components focusable. ### Source excerpt I've seen multiple questions in various Slack communities, Stack Overflow, and other places related to focus on Android and how it doesn't behave as expected. The question typically concerns the use of focusRequester and then inquires why Talkback or other assistive technologies fail to set focus correctly. The simple answer is that these APIs are different, and focus behaves differently with accessibility focus and keyboard focus. In this blog post, I'll discuss the differences and what you can do in different cases. Let's first look at what I mean when I talk about accessibility focus and keyboard focus. Accessibility Focus In this blog post, accessibility focus refers to the focus related to screen readers, such as TalkBack. It could include focus for switch access as well, but I'm leaving it out of the scope of this blog post. When using a screen reader, accessibility focus can be set to any element relevant to the user, such as interactive elements, text, images with text alternatives (content descriptions), and other meaningful elements. The focus indicator can look different on different phones, but here's an example from my phone: It's set by the system, so the app developer can't edit it, and there shouldn't be any need to do that either. Keyboard Focus Keyboard focus, on the other hand, is the focus that interactive elements receive when a user uses a keyboard, D-pad, or other keyboard-emulating device for navigation. Only interactive elements should be focusable; never, for example, headings or other text. The default focus indicator is the ripple, so it's not that visible: Later, I will write a blog post about customising and making the focus indicator pass the accessibility legal requirements with color contrast and other requirements. Making a Component Focusable So you're creating a custom component, and wondering if it's the kind that should be focusable. The short and simple answer is that every component that the user can interact with via touch in ## Sketch Athens release adds Component insertion and replacement to the Command Bar DevFeed: [Sketch Athens release adds Component insertion and replacement to the Command Bar]() Original publisher: [Read original article]() Author: Alasdair Baxter Published: 2025-05-27T03:00:00Z Content type: release Language: en Sources: [Sketch Blog]() Topics: [Sketch](), [GUI]() Tags: [components](), [interface](), [keyboard](), [latest-features](), [libraries](), [release](), [workflows]() ### AI overview Sketch's Athens release expands the Command Bar with interfaces for inserting and replacing Components, improved previews, and faster navigation through Libraries and groups. The article explains how these changes build on the Command Bar introduced in version 100. ### Source excerpt Insert and replace Components, browse better previews, move through Libraries faster -- and much more. Learn how it all came together and how to make the most of the Command Bar. ## Configure Karabiner on macOS with Kotlin DevFeed: [Configure Karabiner on macOS with Kotlin]() Original publisher: [Read original article]() Author: Kaushik Gopal Published: 2025-05-17T20:23:40Z Content type: tutorial Language: en Sources: [Kaushik Gopal's Site]() Topics: [Kotlin](), [macOS](), [configuration](), [JSON](), [TypeScript]() Tags: [configuration](), [dsl](), [how-to](), [json](), [keyboard](), [kotlin](), [macos](), [open-source](), [productivity](), [re](), [repo]() ### AI overview This tutorial introduces karabiner-kt, a Kotlin-based DSL for managing Karabiner keyboard configurations on macOS. It addresses the difficulty of maintaining large karabiner.json files and shows how Kotlin rules can generate the JSON consumed by Karabiner. ### Source excerpt If you're obsessed with productivity hacks, you've probably heard of Karabiner - the ultimate tool for keyboard customization on macOS. But maintaining Karabiner's config is a pain. In this post I'll show you a simpler, Kotlin-powered way to wrangle your Karabiner setup, so you don't have to wrestle with massive, unwieldy JSON. On Karabiner ## Here's the gist: Karabiner lets you intercept any keystroke and remap it to... well, pretty much anything. Want to turn Caps Lock into a Hyper key? Make your keyboard launch confetti? It's all possible. Take the classic usecase: remap Caps Lock to Hyper (⌘⌥⌃⇧) when held, Escape when tapped. That's easy to do but just scratches the surface. With Karabiner, you can build many more customizations that supercharge your workflow. Maintaining that karabiner.json ## I was watching a video by Max Stoiber where he uses Raycast1 & Karabiner. But what struck me was how he customized and maintained his karabiner setup. Karabiner runs off a single .json config file. But that .json configuration can become unwieldy and difficult to manage, as your rules grow in complexity. For example: I require a ~2700 line .json for all my hacks. It's impossible to maintain it as pure json. Max uses TypeScript to maintain his rules -which then compiles down to a .json file- that Karabiner can consume. I really like this approach. If you read my previous blog post, I also ran into a very similar problem and used goku, which in turn used the very esoteric and terse edn format. I like TypeScript over edn but you know what I'd like even better? Kotlin! So on a ✈ ride back home, I decided to whip up karabiner-kt. I'm really happy with my solution. Kotlin affords a much more pleasant DSL than most other2 languages. Here's what a Karabiner rule looks like in Kotlin : karabinerRule { description = "Right Cmd -> Ctrl (Enter alone)" mapping { fromKey = RightCommand toKey = RightControl toKeyIfAlone = KeyCode.ReturnOrEnter forDevice { identifiers = DeviceIdentifier.A ## Year in Review: 2024 DevFeed: [Year in Review: 2024]() Original publisher: [Read original article]() Author: hello@taniarascia.com Published: 2025-03-27T00:00:00Z Content type: article Language: en Sources: [Tania Rascia]() Topics: [coding](), [CSS](), [React](), [Web Development](), [Web platform]() Tags: [bluesky](), [burnout](), [career](), [coding](), [css](), [hooks](), [keyboard](), [meta](), [pagination](), [projects](), [react](), [redesign](), [review](), [side-projects](), [sorting](), [table](), [variables](), [year-in-review]() ### AI overview A 2024 year-in-review from a principal engineer who continues to work primarily with React and CSS. The author reflects on balancing a full-time engineering role with coding, writing, side projects, and maintaining a personal website, while highlighting several articles and a blog redesign completed during the year. ### Source excerpt I'm trying to win the award for "Latest Year in Review". 🏆 I don't know if anyone can challenge me at this point, as it's almost thirdway... ## Native Git support in Zed DevFeed: [Native Git support in Zed]() Original publisher: [Read original article]() Author: Conrad Irwin Published: 2025-03-12T00:00:00Z Content type: release Language: en Sources: [Zed Industries - Blog]() Topics: [Git](), [Command-line interface](), [Large Language Model]() Tags: [command-line](), [feature](), [git](), [keyboard](), [llm](), [native]() ### AI overview Zed 0.177 adds native Git support, including staging, commits, fetching, pulling, pushing, repository state monitoring, and keyboard-driven diff review. Zed can also ask a preferred LLM to generate commit messages. ### Source excerpt You can now stage, commit, pull, push, and more, all natively within Zed. ## Should we make it a preference?: On customization, defaults, and accessibility DevFeed: [Should we make it a preference?: On customization, defaults, and accessibility]() Original publisher: [Read original article]() Author: andyacevedo Published: 2025-01-23T18:28:29Z Content type: article Language: en Sources: [Slack Design]() Topics: [Accessibility](), [User interface design](), [Slack]() Tags: [accessibility](), [customization](), [keyboard](), [screen](), [uncategorized]() ### AI overview Slack Design explains when accessibility accommodations should be defaults rather than optional preferences. It argues that new users should receive an accessible experience out of the box, while preferences should support advanced customization and preserve familiar behavior during significant changes. ### Source excerpt Design that is inclusive and accessible almost always works better for everyone. But once in a while we reach a genuine dilemma -- the more technically accessible choice adds friction or breaks expectations for everyone else. In these moments, someone inevitably asks: Can we just make it a preference? "Make it a preference" is sometimes [...] The post Should we make it a preference?: On customization, defaults, and accessibility appeared first on Slack Design. ## Vim Roadmap 2025 DevFeed: [Vim Roadmap 2025]() Original publisher: [Read original article]() Author: Conrad Irwin Published: 2025-01-22T00:00:00Z Content type: opinion Language: en Sources: [Zed Industries - Blog]() Topics: [Vim](), [Neovim](), [User Experience]() Tags: [2025](), [keyboard](), [user-experience](), [vim]() ### AI overview The article outlines Zed's 2025 roadmap for Vim mode. It describes current improvements, including operator support, command-palette work, and Vim plugin integrations, then identifies planned work around editor-adjacent workflows, Vim compatibility, multi-cursor support, persistent state, collaboration shortcuts, and Git integration. ### Source excerpt What's next for Vim mode in Zed? ## Open source mac apps I love DevFeed: [Open source mac apps I love]() Original publisher: [Read original article]() Author: Stanko Published: 2024-11-09T00:00:00Z Content type: article Language: en Sources: [Stanko Tadić]() Topics: [Open Source](), [App](), [GUI](), [Homebrew](), [dropbox](), [keyboard]() Tags: [apps](), [bash](), [dropbox](), [gui](), [keyboard](), [mac](), [open-source](), [optimization](), [tools]() ### AI overview The article recommends a selection of free, open-source Mac applications that the author uses regularly, including menu-bar utilities, image optimization software, keyboard customization, clipboard management, Dropbox access, terminal integration, window tiling, and command-line tools. It also provides Homebrew installation commands for the listed applications. ### Source excerpt I want to share some really nice open-source applications I use on a daily basis. I did a similar post about six years ago, so I felt there is a need for an updated one. I focused on the apps that I feel are really convenient but less known. All of the applications listed are free and open source. For each app, I included a brew install command. If you happen to like and use them, please consider donating to their respective authors. Here are all of the apps in alphabetical order: GUI Applications Hidden Bar ImageOption Itsycal Karabiner-Elements Keeping You Awake Maccy Maestral OpenInTerminal Pearcleaner Pika Rectangle Bash programs dust ripgrep tio zoxide GUI Applications # Hidden Bar # GitHub brew install hiddenbar Hidden Bar allows you to hide icons from the menu bar. It seems that every app nowadays wants to be in the menu bar, and this helps declutter it. ImageOptim # GitHub | Website brew install imageoptim As its name suggests, ImageOptim optimizes images. It is a UI for a bunch of lossless image optimization tools. Just drop your images and it will compress them without losing any quality. Itsycal # GitHub | Website brew install itsycal A small calendar that lives in your menu bar. Why is this not built into the operating system? Karabiner-Elements # GitHub | Website brew install karabiner-elements I just can't get used to Apple's international keyboard layout and the tilde being in the bottom left. Karabiner solves that. It's a keyboard customizer that allows you to remap keys and create complex modifications. Keeping You Awake # GitHub | Website brew install keepingyouawake Prevents your Mac from going to sleep by clicking on its icon in the menu bar. I use it when I'm running my pen plotter to make sure the laptop doesn't go to sleep. Maccy # GitHub | Website brew install maccy A clipboard manager. It saves your clipboard history and allows you to quickly access it. Maestral # GitHub | Website brew install maestral A lightweight Dropbox client. The offic [Next page]()