# custom Published articles for custom. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Support Time to Take Action with Compose DevFeed: [Support Time to Take Action with Compose]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2024-12-28T09:46:59.418000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [Accessibility](), [Android](), [Compose](), [User interface design](), [Code]() Tags: [accessibility](), [android](), [blog-post](), [components](), [compose](), [custom](), [developers](), [how-to](), [settings](), [users]() ### AI overview This tutorial explains Android's Time to take action accessibility setting, which controls how long temporary messages remain visible. It describes why users may need additional time and shows why custom Compose components must explicitly support the setting. ### Source excerpt While working on my master's thesis and the Android Accessibility Checklist, one of the answers to my survey mentioned an accessibility setting called time to take action. Since then, I've been curious about it and wanted to write a blog post as I feel it's one of the undersupported accessibility settings and really useful for those who utilize it. So, what is time to take action, and why would someone use it? And why should we, as developers, care? Let's talk about that first. Time to Take Action Time to take action is a setting that controls the minimum time in which temporary messages asking a user to take action are shown. So, for example, when you press the volume buttons on your Android phone, you should see the volume controls next to the volume buttons, and this setting controls how long they're visible. This setting has different options: Default, 10 seconds, 30 seconds, 1 minute and 2 minutes. You can find them from Settings -> Accessibility Settings -> Timing controls -> Time to take action (Accessibility timeout). The screen looks something like this, depending on your phone's version and manufacturer: And why would someone need this setting? Well, the source code and documentation for a method we're going to use in a moment puts it pretty well: Some users may need extra time to review the controls, or to reach them, or to activate assistive technology to activate the controls automatically. Okay, now we've established what the time to take action is. However, the question of relevance remains: Why should we care as developers? Isn't it something that the operating system handles automatically? The answer is yes and no. Most components on the operating system level and Material3 components respect this setting. However, when you're building a custom component, it's not automatically respected, and you'll need to add support for it. That's why the settings page mentions that not all apps support the setting. The thing is, developers usually don't know abo ## Function Types in Nix DevFeed: [Function Types in Nix]() Original publisher: [Read original article]() Published: 2024-08-27T00:00:00Z Content type: article Language: en Sources: [Garnix Blog]() Topics: [Nix](), [function]() Tags: [custom](), [function](), [functions](), [types]() ### AI overview A short note about custom typing for functions in Nix. ### Source excerpt A short note about custom typing for functions in Nix ## Launch Week II Day 4: Custom JS DevFeed: [Launch Week II Day 4: Custom JS]() Original publisher: [Read original article]() Author: Joshua Kim Published: 2024-01-10T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Documentation]() Tags: [analytics](), [announcements](), [custom](), [documentation](), [integrations](), [js](), [launch](), [launch-week](), [tracking]() ### AI overview Mintlify introduced Custom JS for Growth plan customers during Launch Week II Day 4. The feature enables custom integrations, analytics, user tracking, and advanced documentation customizations such as platform-specific tab auto-selection. ### Source excerpt Day 4 of Launch Week 2 brings Custom JS to your documentation πŸš€. ## Announcing Custom Domains on Fermyon Cloud DevFeed: [Announcing Custom Domains on Fermyon Cloud]() Original publisher: [Read original article]() Author: MacKenzie Olson Published: 2023-07-26T16:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Cloud](), [domain]() Tags: [announce](), [cloud](), [custom](), [domain]() ### AI overview Fermyon Cloud now supports custom domains, allowing users to bring their own domain while Fermyon manages the rest. ### Source excerpt Today, we are excited to announce support for custom domains on Fermyon Cloud - bring your domain, and we'll handle the rest. ## Indexing by Custom Field in Craft CMS DevFeed: [Indexing by Custom Field in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2023-06-28T17:13:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Database](), [migration]() Tags: [article](), [cms](), [content](), [craft](), [custom](), [custom-fields](), [database](), [fields](), [how-to](), [indexes](), [indexing](), [insights](), [learn](), [make](), [migration](), [performance]() ### AI overview A tutorial on adding database indexes for custom fields in Craft CMS through a content migration. It explains that Craft CMS does not automatically index custom fields, so queries filtering on those fields may not scale well as datasets grow. ### Source excerpt Learn how to make a content migration to add database indexes for custom fields in Craft CMS ## Logging to a File with Craft CMS 4 DevFeed: [Logging to a File with Craft CMS 4]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2022-12-21T19:35:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Logging](), [log management](), [PHP]() Tags: [article](), [cms](), [craft](), [custom](), [easily](), [file](), [how-to](), [insights](), [learn](), [logging](), [logs](), [module](), [php](), [plugin](), [send](), [separate]() ### AI overview A tutorial showing how to configure Craft CMS 4 plugins or modules to send their logs to separate files using Monolog and a FileLog helper class. It explains log levels, category matching, namespaces, and storage/logs output. ### Source excerpt Learn how to easily send logs from your custom module or plugin to a separate file in Craft CMS 4 ## Bottom sheet: Custom transitioning DevFeed: [Bottom sheet: Custom transitioning]() Original publisher: [Read original article]() Author: Kotenagitare (ΠšΠΎΡˆΠ΅Π»Ρ‘ΠΊ) Published: 2022-11-17T14:46:51Z Content type: tutorial Language: ru Sources: ["ΠšΠΎΡˆΠ΅Π»Ρ‘ΠΊ" RU]() Topics: [iOS](), [Swift]() Tags: [animation](), [bottom-sheet](), [bottom-sheet-behavior](), [bottomnavigationview](), [bottomsheet](), [custom](), [ios](), [presentation](), [swift](), [tag-08a48a9394c3](), [uikit]() ### AI overview This tutorial explains how to implement a custom transitioning delegate in an iOS application to present controllers as bottom sheets. It covers presentation and animation controllers, content-sized layout, and the example payment screen in the "ΠšΠΎΡˆΠ΅Π»Ρ‘ΠΊ" app. ### Source excerpt Π‘ΠΎΠ²Ρ€Π΅ΠΌΠ΅Π½Π½Ρ‹Π΅ трСбования ΠΊ Π΄ΠΈΠ·Π°ΠΉΠ½Ρƒ ΠΌΠΎΠ±ΠΈΠ»ΡŒΠ½Ρ‹Ρ… ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΉ всё Ρ‡Π°Ρ‰Π΅ ΠΏΠΎΠ΄ΠΊΠΈΠ΄Ρ‹Π²Π°ΡŽΡ‚ Π·Π°Π΄Π°Ρ‡ΠΈ ΠΏΠΎ ΠΎΡ‚ΠΎΠ±Ρ€Π°ΠΆΠ΅Π½ΠΈΡŽ ΠΊΠΎΠ½Ρ‚Π΅Π½Ρ‚Π° со слоТным ΠΏΠΎΠ²Π΅Π΄Π΅Π½ΠΈΠ΅ΠΌ. Для Π΅Π³ΠΎ Ρ€Π΅Π°Π»ΠΈΠ·Π°Ρ†ΠΈΠΈ Π½Π΅ΠΎΠ±Ρ…ΠΎΠ΄ΠΈΠΌΠΎ ΠΏΠΎΠ½ΠΈΠΌΠ°Π½ΠΈΠ΅ Ρ‚ΠΎΠ³ΠΎ, ΠΊΠ°ΠΊ Ρ€Π°Π±ΠΎΡ‚Π°ΡŽΡ‚ кастомныС прСзСнтация ΠΈ Ρ‚Ρ€Π°Π½Π·ΠΈΡˆΠ΅Π½Ρ‹. Π’ этой ΡΡ‚Π°Ρ‚ΡŒΠ΅ я расскаТу, ΠΊΠ°ΠΊ ΠΌΡ‹ Ρ€Π΅ΡˆΠΈΠ»ΠΈ Π·Π°Π΄Π°Ρ‡Ρƒ ΠΏΠΎ созданию экрана ΠΎΠΏΠ»Π°Ρ‚Ρ‹ Π² ΠΏΡ€ΠΈΠ»ΠΎΠΆΠ΅Π½ΠΈΠΈ "ΠšΠΎΡˆΠ΅Π»Ρ‘ΠΊ" с ΠΏΠΎΠΌΠΎΡ‰ΡŒΡŽ кастомной Π½Π°Π²ΠΈΠ³Π°Ρ†ΠΈΠΈ ΠΌΠ΅ΠΆΠ΄Ρƒ ΠΊΠΎΠ½Ρ‚Ρ€ΠΎΠ»Π»Π΅Ρ€Π°ΠΌΠΈ, ΠΊΠΎΡ‚ΠΎΡ€Ρ‹Π΅ ΠΎΡ‚ΠΎΠ±Ρ€Π°ΠΆΠ°ΡŽΡ‚ΡΡ ΠΊΠ°ΠΊ bottom sheet. Π§ΠΈΡ‚Π°Ρ‚ΡŒ Π΄Π°Π»Π΅Π΅ ## Introducing Bartholomew DevFeed: [Introducing Bartholomew]() Original publisher: [Read original article]() Published: 2022-02-15T19:12:25Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Content Management System](), [wasm](), [WebAssembly](), [Handlebars](), [Markdown]() Tags: [cms](), [content](), [custom](), [functions](), [lightweight](), [markdown](), [templates](), [wasm](), [webassembly]() ### AI overview Fermyon introduces Bartholomew, a lightweight WebAssembly content management system with Handlebars templates, custom scripted functions, and Markdown support. ### Source excerpt Fermyon is proud to introduce our new lightweight WebAssembly (Wasm) content management system (CMS) that we call Bartholomew. With support for handlebars templates, custom scripted functions, and markdown, it's a svelte way to run a CMS. ## Designing Harmony into Dynamic Color DevFeed: [Designing Harmony into Dynamic Color]() Original publisher: [Read original article]() Published: 2022-02-10T13:00:00Z Content type: article Language: en Sources: [Material.io - Material Design]() Topics: [color]() Tags: [color](), [custom](), [design](), [user]() ### AI overview Material explains how makers can design with custom colors while respecting user choice in dynamic color systems. ### Source excerpt How Material enables makers to design with custom colors while respecting user choice ## Searching Craft CMS Matrix Blocks DevFeed: [Searching Craft CMS Matrix Blocks]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-11-26T05:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Query (disambiguation)](), [Content Management System]() Tags: [based](), [behavior](), [blocks](), [cms](), [contain](), [contents](), [craft](), [custom](), [easily](), [elements](), [entries](), [insights](), [little](), [matrix](), [php](), [query](), [twig]() ### AI overview A tutorial on querying Craft CMS Entries by the content of their Matrix blocks. It explains how to find matching Matrix blocks, collect their owner IDs, and use those IDs to filter an Element query, including a generalized approach usable in Twig. ### Source excerpt With a little custom Behavior, we can easily query for Elements such as Entries in Craft CMS based on the contents of the Matrix Blocks they contain ## A HashiConf art collab DevFeed: [A HashiConf art collab]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2021-10-15T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [color](), [Requirements](), [iteration]() Tags: [art](), [conference](), [custom](), [design](), [generative](), [hashicorp](), [iteration](), [printer](), [printing](), [requirements](), [things]() ### AI overview The article describes creating custom generative-art prints for HashiConf Europe speakers. Each print combines the speaker's name, talk title, and the relevant HashiCorp product color in a randomly generated geometric grid, following conference design guidelines. ### Source excerpt A couple of months ago my friend Jana helped organize HashiConf Europe, and asked me to work on generating custom artwork for each of their speakers. This was my first experience with creating art for someone else, and especially art that had to match someone else's artistic guidelines. I've said this before, but I live and nap by the idea that rules (and editing) are at the core of the artistic process and not having to do that myself was brilliant. I wanted to write a bit about it because a) I did a bunch of work that I'm really proud of and I never got to talk about it and b) I am vain and I want to talk about it. This was the final poster: And this is what we wrote about it on the card that accompanied it: Enclosed you will find an art print made for you by generative artist and engineer Monica Dinculescu. This individual print is unique to you and you alone, as Monica has incorporated your name, the title of your talk, and the color of the HashiCorp product that you are talking about at this year's conference. Each cell in the grid has been randomly generated to contain either a letter from your name, or a pattern in the product color. Cells located towards the middle of the grid are more likely to contain a letter rather than a pattern, and this likelihood decreases in the cells towards the edges. This print is the only iteration of its kind. Were it to be generated again, it would look slightly different each time. I print everything in my art store myself, because I sell very limited editions and third-party printing companies only make sense financially when you're printing in the several dozen. This does mean that sometimes I'll fight with my printer thinking that its colour profile is whack, only to discover that it was Doing Just Fineβ„’ and my MacBook oversaturates things like it's an Instagram filter in 2011. Every day is a school day. Here are all the prints drying on their totes profesh drying rack that is definitely not just a string I hung around in ## Random Animating Pie Button DevFeed: [Random Animating Pie Button]() Original publisher: [Read original article]() Published: 2021-06-16T21:36:11Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Compose](), [Canvas](), [Code]() Tags: [animate](), [canvas](), [code](), [color](), [component](), [compose](), [custom](), [data-class](), [exploring](), [fun](), [functions](), [jetpack](), [jetpack-compose](), [random](), [val](), [var]() ### AI overview A Jetpack Compose sample demonstrates a custom pie-chart component that draws with Canvas and animates to a random percentage when a button is clicked. ### Source excerpt I am exploring animations with small sampler functions using Jetpack Compose. This one is a custom component that draws a little pie chart. It will animate a random pie value on the click of the button. data class PieData( val foreground: Color = Color.White, val strokeWidth: Dp = 4.dp, val percentage: Float ) @Composable fun PieStatus( modifier: Modifier = Modifier, pieData: PieData ) { var animationPlayed by remember { mutableStateOf(false) } val currentPercentage = animateFloatAsState( targetValue = if (animationPlayed) pieData.percentage else 0f, animationSpec = tween(1000) ) LaunchedEffect(key1 = true) { animationPlayed = true } Canvas( modifier = modifier ) { val canvasWidth = size.width val canvasHeight = size.height drawCircle( color = pieData.foreground, center = Offset(x = canvasWidth / 2, y = canvasHeight / 2), radius = canvasWidth / 2 - pieData.strokeWidth.toPx(), style = Stroke(width = pieData.strokeWidth.toPx()) ) val arcPadding = pieData.strokeWidth.toPx() * 2 drawArc( color = pieData.foreground, startAngle = -90f, sweepAngle = currentPercentage.value * 360, useCenter = true, topLeft = Offset(arcPadding, arcPadding), size = Size(size.width - (arcPadding * 2f), size.height - (arcPadding * 2f)) ) } } code ## Custom Matrix Block Peer Validation Rules DevFeed: [Custom Matrix Block Peer Validation Rules]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-05-24T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Website]() Tags: [authoring](), [better](), [blocks](), [builder](), [cms](), [content](), [craft](), [custom](), [errors](), [experience](), [insights](), [leverage](), [matrix](), [module](), [peer](), [rules](), [validation]() ### AI overview A tutorial on extending Craft CMS Matrix block content builders with custom peer validation rules. The example validates sundae blocks by limiting scoop and topping counts, requiring at least one scoop, and rejecting a specific flavor combination. ### Source excerpt Leverage a Craft CMS module to add custom peer validation rules to your content builder Matrix blocks for a better content authoring experience ## Creating a custom field in Craft CMS DevFeed: [Creating a custom field in Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-08-27T04:00:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Code]() Tags: [cms](), [code](), [craft](), [create](), [custom](), [field](), [how-to](), [insights](), [learn](), [leveraging](), [little](), [platform](), [possible](), [writing]() ### AI overview A tutorial on creating a custom field in Craft CMS whose dropdown options come from Craft Commerce country data. It recommends subclassing the built-in Craft Dropdown field and changing only the required behavior to reduce code and maintenance. ### Source excerpt Learn how to create a custom field in Craft CMS, writing as little code as possible by leveraging the platform. ## Randomized Selective Color: A Post List Study DevFeed: [Randomized Selective Color: A Post List Study]() Original publisher: [Read original article]() Published: 2020-04-27T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [color](), [CSS](), [JavaScript](), [modern web development](), [Code](), [interactive website](), [Vanilla JavaScript]() Tags: [code](), [color](), [css](), [custom](), [design](), [flexbox](), [javascript](), [properties](), [website]() ### AI overview A study of selective color from a predefined palette for a website redesign. It demonstrates randomized color combinations using CSS custom properties, JavaScript, gradients, flexbox, and progressive enhancement with CSS Houdini. ### Source excerpt A study on selective color from a predefined list, using CSS custom properties, a little bit of JavaScript, and some progressively enhanced CSS Houdini. ## Post-Mortem: Outbreak Database DevFeed: [Post-Mortem: Outbreak Database]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2020-03-03T05:00:00Z Content type: article Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [migration](), [Content Management System](), [PHP](), [Front end](), [Vue.js](), [GraphQL](), [axios](), [Website](), [Back end](), [API]() Tags: [aging](), [axios](), [cms](), [content](), [craft](), [custom](), [frontend](), [graphql](), [hybrid](), [management](), [migration](), [modernizing](), [php](), [post-mortem](), [post-mortems](), [twig-vue-js](), [vue](), [vuex](), [website]() ### AI overview A post-mortem on modernizing the aging custom PHP Outbreak Database website by migrating it to Craft CMS and planning a hybrid Twig/Vue.js frontend using Vuex, Axios, and GraphQL. The project aimed to improve content maintenance, researcher and journalist usability, and long-term technical foundations. ### Source excerpt Modernizing an aging custom PHP website with Craft CMS for content management, and a hybrid Twig/Vue.js + Vuex + Axios + GraphQL on the frontend ## Creating a Custom Logger for Craft CMS DevFeed: [Creating a Custom Logger for Craft CMS]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2019-07-21T17:52:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Content Management System](), [Logging](), [configuration](), [Dependency injection](), [Software as a service](), [Code]() Tags: [built-in](), [cms](), [code](), [configuration](), [craft](), [custom](), [dependency-injection](), [insights](), [logger](), [logging](), [logs](), [need](), [needs](), [saas](), [send](), [service](), [sufficient](), [third-party](), [want]() ### AI overview A tutorial on customizing Craft CMS logging through Yii-based configuration and code, including changing built-in behavior and sending logs to third-party aggregation services such as PaperTrail or Sentry. ### Source excerpt The built-in Craft CMS logging system is sufficient for most needs, but what if you need custom logging, or want to send your logs to a third-party service? ## Eschewing Shadow DOM DevFeed: [Eschewing Shadow DOM]() Original publisher: [Read original article]() Author: Heydon Pickering Published: 2019-06-14T00:00:00Z Content type: article Language: en Sources: [The Every Layout Blog]() Topics: [Web Components](), [CSS](), [modern web development](), [React](), [styled-components]() Tags: [css](), [custom](), [element](), [react](), [styled-components]() ### AI overview An examination of styling problems encountered with Shadow DOM, including inconsistent universal styles, limited inheritance, slot restrictions, and specificity issues. The author proposes an experimental alternative for web components that namespaces and embeds prop-derived instance styles in the document head. ### Source excerpt Regarding styling, Shadow DOM is really good at one thing: preventing per-component styles from leaking out and affecting other parts of the document. Unfortunately, Shadow DOM also has a very opinionated way of preventing styles being applied from the parent document. Here is a roundup of the quirks and associated issues I've encountered: Shadow DOM styling issues Universal styles Some universal styles (using the * selector) are applied, and others are not. The color property appears to pierce shadow boundaries, but I've had no luck with box-sizing. Having to set box-sizing: border-box for each component is redundant. Inheritance Document styles are inherited in Shadow DOM. But inheritance only gets you so far, especially since not all properties are inheritable by default anyway. I've tried hacking things together with the explicit inherit keyword, but that seems to have no effect. Using the following is no good, because it forces every node to inherit every property from the parent. If had display: flex applied, every one of the component's descendants would adopt it. * { all: inherit; /* yikes */ } Slot restrictions For performance reasons, the ::slotted() selector, which allows you to style the Light DOM content of your component from within your Shadow DOM, only lets you affect child elements and not descendants at depth. This is a bit restrictive. Worse, you cannot seem to use sibling combinators like + or ~. None of the following works: ::slotted(*) + * /* Nope */ ::slotted(* + *) /* Nope */ ::slotted(*) + ::slotted(*) /* Nope */ Specificity In making layout components, I like to take a progressive approach: style the component and its Light DOM nodes in my document stylesheet, then enhance with instance-specific styles via props (attributes) in Shadow DOM. For a component instance that looks like this... ...I would apply the itemWidth value in the Shadow DOM using interpolation: `