# dev-tools Published articles for dev-tools. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Workflow lab: Moving between design and code with agents DevFeed: [Workflow lab: Moving between design and code with agents]() Original publisher: [Read original article]() Author: Riccardo Erra Published: 2026-08-26T22:00:00Z Content type: tutorial Language: en Sources: [Figma Blog]() Topics: [Figma](), [AI-assisted coding](), [dev-tools](), [Code](), [Pull Request]() Tags: [agents](), [ai](), [code](), [coding](), [design-systems](), [dev-tools](), [developers](), [figma](), [ui](), [workflow]() ### AI overview This workflow lab shows how designers and developers can use Figma, Figma dev tools, and coding agents to keep design and code aligned. It follows a feature from wireframes through implementation and review, emphasizing approved components, design tokens, and richer context to improve generated code and reduce rework. ### Source excerpt Coding agents are reshaping how developers build, but they're only as good as the input they're given. This workflow explores how context keeps code and canvas in sync. ## Internal Developer Portal: How Do I Get Started? DevFeed: [Internal Developer Portal: How Do I Get Started?]() Original publisher: [Read original article]() Author: Sooraj Shah Published: 2026-07-30T10:23:42Z Content type: article Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [internal developer portal](), [Developer experience](), [Platform Engineering](), [dev-tools](), [Microservice](), [Cloud Native Ecosystem](), [.NET MAUI]() Tags: [catalog](), [cloud-native](), [dev-tools](), [developer-experience](), [developer-portal](), [internal-developer-portal](), [jobs](), [microservices](), [onboarding](), [platform](), [platform-engineering](), [user-stories]() ### AI overview This article explains how platform engineering teams can start an internal developer portal by building a focused minimum viable product. It recommends reducing developer complexity, grounding the portal in real use cases and user stories, gathering stakeholder feedback, and improving the portal iteratively. ### Source excerpt You're using more dev tools that solve different problems, and now your breaking the developer experience. Learn the first steps to get started. ## Developers are attached to tools because tools encode trust DevFeed: [Developers are attached to tools because tools encode trust]() Original publisher: [Read original article]() Author: Ryan Donovan Published: 2026-07-29T14:06:38Z Content type: opinion Language: en Sources: [Stack Overflow Blog]() Topics: [Developer Tools](), [AI-assisted coding]() Tags: [agentic](), [buiilding-software](), [dev-tools](), [developer-tooling](), [developers](), [ide](), [se-stackoverflow](), [se-tech](), [tools]() ### AI overview An opinion piece on how developers build trust in customizable tools and workflows, contrasting established tools such as Vim and Emacs with rapidly changing coding agents. ### Source excerpt The tools themselves are new and their capabilities are in constant flux. If your kitchen knife kept changing shape, weight, and edge, you'd have to relearn it every time; that's a hard tool to build trust in. But it also points to a flaw in how you use that tool, the process around it, and the way the tool reinforces the process. ## Partnerships can keep open source sustainable DevFeed: [Partnerships can keep open source sustainable]() Original publisher: [Read original article]() Author: Phoebe Sajor Published: 2026-07-24T07:40:00Z Content type: article Language: en Sources: [Stack Overflow Blog]() Topics: [Open Source](), [Cloudflare](), [JavaScript](), [Developer experience](), [distributed-systems]() Tags: [acquisition](), [cloudflare](), [dev-tools](), [developer-experience](), [developer-tools](), [distributed-systems](), [javascript](), [leaders-of-code](), [open-source](), [partnerships](), [podcast](), [se-stackoverflow](), [se-tech](), [typescript]() ### AI overview Ryan welcomes VoidZero's Evan You and Cloudflare's Dane Knecht to discuss Cloudflare's acquisition of VoidZero, the implications for JavaScript development, and how partnerships can help open-source projects remain maintained and sustainably monetized. ### Source excerpt Ryan welcomes VoidZero's Evan You and Cloudflare's Dane Knecht back to the show to discuss Cloudflare's recent acquisition of VoidZero and what it means for JavaScript development, how partnerships like theirs can help open-source projects stay maintained and sustainably monetized, and how Cloudflare's distributed systems are helping to improve developer experience in Vite and beyond. ## Automating cross-repo documentation with GitHub Agentic Workflows DevFeed: [Automating cross-repo documentation with GitHub Agentic Workflows]() Original publisher: [Read original article]() Author: David Pine Published: 2026-07-08T21:11:56Z Content type: article Language: en Sources: [GitHub]() Topics: [GitHub](), [GitHub Actions](), [pull-requests](), [Documentation](), [Automation]() Tags: [agentic-workflows](), [ai-ml](), [architecture-optimization](), [automation](), [dev-tools](), [devops](), [documentation](), [engineering](), [generative-ai](), [github](), [github-agentic-workflows](), [github-copilot](), [llms](), [machine-learning](), [pull-requests]() ### AI overview The Aspire team describes using GitHub Agentic Workflows to automate documentation across separate product and documentation repositories. The workflow turns merged product changes into documentation pull requests that are reviewed by the engineer who shipped the feature; the article reports 82 such pull requests for Aspire 13.3 and 13.4, with a median delay of 44.8 hours after the related product pull request. ### Source excerpt Explore how the Aspire team turns merged product changes into SME-reviewed docs pull requests, closing the gap between release and documentation. The post Automating cross-repo documentation with GitHub Agentic Workflows appeared first on The GitHub Blog. ## OpenAI Eng & Dev Tools Founder: How Software Engineering Is Changing | Charlie Marsh DevFeed: [OpenAI Eng & Dev Tools Founder: How Software Engineering Is Changing | Charlie Marsh]() Original publisher: [Read original article]() Author: Ryan Peterman Published: 2026-06-22T09:45:53Z Content type: article Language: en Sources: [The Developing Dev]() Topics: [dev-tools](), [Development](), [Python](), [Software Engineering](), [engineering-culture]() Tags: [dev](), [dev-tools](), [engineering](), [go](), [javascript](), [linter](), [openai](), [python](), [rust](), [software-engineering](), [tooling](), [tools]() ### AI overview An interview with Charlie Marsh, founder of Astral, examines how software engineering and developer tooling are changing. Marsh discusses his experience building Python systems, limitations in Python tooling, and the influence of performance-focused native tools in the JavaScript ecosystem. ### Source excerpt Charlie Marsh is the founder of Astral, the Python devtool startup that was acquired by OpenAI. ## What's new in Svelte: May 2026 DevFeed: [What's new in Svelte: May 2026]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2026-05-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [Svelte](), [TypeScript](), [Command-line interface](), [releases](), [Caching](), [Forms](), [dev-tools]() Tags: [caching](), [cli](), [dev-tools](), [forms](), [release](), [svelte](), [typescript]() ### AI overview A May 2026 roundup of Svelte and SvelteKit updates, including TypeScript 6.0 support, remote function and form improvements, caching changes, experimental Svelte CLI community add-ons, and selected community projects. ### Source excerpt This month we got a ton of improvements to SvelteKit's remote functions, TypeScript 6.0 support and the experimental release of community plugins in the Svelte CLI. Svelte was also featured in ThoughtWorks Technology Radar! Big month, bigger showcase... so let's dive in! What's new in SvelteKit SvelteKit now supports TypeScript 6.0 (2.56.0, Docs, #15595) form fields can now specify a default value using field.as(type, value), reducing boilerplate for pre-populated forms (2.56.0, Docs, #15577) Remote function transport now uses hydratable, enabling richer data types in query results (2.56.0, #15533) Form submit now returns a boolean to indicate submission validity for enhanced form remote functions (2.57.0, Docs, #15530) Remote Function Breaking Changes (2.56.0) Client-requested query refreshes must obtain permission from the server (#15562) Stabilize remote function caching by sorting object keys (#15570) Add run() method to queries, disallow awaiting queries outside render (#15533) Isolate command-triggered query refresh failures per-query (#15562) requested now requires limit and yields { arg, query } entries rather than validated args (#15739) Looking for more details on the many bug fixes and performance optimizations from this month? Check out the SvelteKit / Adapter CHANGELOGs. What's new in Svelte and Svelte Dev Tools Community add-ons are now available in sv as an experimental feature (sv@0.1.0, Docs, #1020) The sv and sv-utils packages are now separate in the CLI package - leading to a more explicit public API and a deprecation pass for old features (sv@0.2.0, Docs, #1046) sv will now more reliably detect if Vitest v3 is installed when configuring projects (sv@0.15.2, #1073) Types for TweenOptions, SpringOptions, SpringUpdateOptions and Updater are now available as exports from svelte/motion (svelte@5.55.0, Docs, #17967) For a full list of changes - including all the important bugfixes that went into the releases this month - check out the Svelte compiler's ## Karpathy's microGPT, Jeff Dean's Pareto Frontier, and the LLM Course - 📚 The Tokenizer Edition #18 DevFeed: [Karpathy's microGPT, Jeff Dean's Pareto Frontier, and the LLM Course - 📚 The Tokenizer Edition #18]() Original publisher: [Read original article]() Author: Sairam Sundaresan Published: 2026-02-19T13:34:15Z Content type: article Language: en Sources: [Gradient Ascent]() Topics: [Large Language Model](), [agentic-coding](), [LLM evaluation / benchmarking](), [Claude](), [dev-tools](), [Learning]() Tags: [agentic-coding](), [ai](), [benchmarking](), [benchmarks](), [claude](), [code](), [dev-tools](), [llm]() ### AI overview A curated AI newsletter highlights research, videos, tools, and learning resources. It discusses the gap between agent performance on bug fixes and complex feature development, task handoff versus authority transfer, Jeff Dean's Pareto frontier, and Karpathy's 243-line dependency-free microGPT. ### Source excerpt This week's most valuable AI resources ## 2025 - Year in review DevFeed: [2025 - Year in review]() Original publisher: [Read original article]() Author: Chris Hager Published: 2026-01-01T00:00:00Z Content type: opinion Language: en Sources: [Chris Hager]() Topics: [Transactions](), [Code](), [Artificial Intelligence](), [Large Language Model](), [Ethereum](), [ChatGPT](), [Claude](), [GitHub Copilot](), [trusted-execution-environment](), [Development]() Tags: [2025](), [ai](), [chatgpt](), [claude](), [copilot](), [dev-tools](), [ethereum](), [year-in-review]() ### AI overview A personal review of 2025 covering published writing, reading, projects, Ethereum infrastructure work, and expanded use of LLMs including Claude, ChatGPT, Gemini, and Copilot. It also notes practical considerations such as isolating AI tools and using linters in development workflows. ### Source excerpt This post is a look back at 2025: projects, writings, code, books, and a few thoughts on AI, social media, and life. ## Sandbox Your AI Dev Tools: A Practical Guide for VMs and Lima DevFeed: [Sandbox Your AI Dev Tools: A Practical Guide for VMs and Lima]() Original publisher: [Read original article]() Author: Chris Hager Published: 2025-11-25T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [AI-assisted coding](), [developer tooling](), [virtual machines](), [sensitive data](), [API keys](), [ssh](), [npm](), [pip]() Tags: [ai-assisted-coding](), [api-keys](), [dev-tools](), [npm](), [python](), [sandbox](), [sensitive-data](), [ssh]() ### AI overview A practical guide to sandboxing AI coding assistants and other development tools in isolated virtual machines using Lima. It explains how isolation helps protect SSH keys, API tokens, credentials, environment variables, and other sensitive data from arbitrary code, scripts, and package installation behavior. ### Source excerpt AI coding assistants, npm, pip, and other development tools can run arbitrary code and scripts on your machine, potentially stealing SSH keys, API tokens, wallet keys, sensitive credentials and other private data without you noticing. This guide shows you how to sandbox these tools in isolated VMs using Lima, so you can experiment and develop freely without putting your sensitive data at risk. Jump straight to the guide, or read on for a bit of personal context. ## Introducing the DigitalOcean AI Ecosystem DevFeed: [Introducing the DigitalOcean AI Ecosystem]() Original publisher: [Read original article]() Author: Meghan Grady Published: 2025-10-06T20:07:17Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Artificial Intelligence](), [AI Development](), [Cloud](), [LangChain](), [litellm]() Tags: [ai](), [amd](), [build](), [cloud](), [deepseek](), [dev-tools](), [digitalocean](), [gradient-platform](), [integrations](), [meta](), [models](), [nvidia](), [openai](), [partner]() ### AI overview DigitalOcean announced an expansion of its AI Ecosystem and introduced the DigitalOcean AI Partner Program. Through the Gradient AI Agent Cloud, the ecosystem brings together infrastructure, AI models, development tools, integration frameworks, and specialist partners for building AI applications. ### Source excerpt Last week at Deploy London, we announced a significant expansion of our offerings within the DigitalOcean AI Ecosystem and introduced the DigitalOcean AI Partner Program. A platform is only as strong as its ecosystem, and these initiatives are designed to create a comprehensive, flexible, and powerful environment for startups, builders, and developers to create the next generation of AI applications. Explore What's Possible with the DigitalOcean AI Ecosystem We're collaborating with industry leaders and innovative startups to provide access to all of the AI products and services you need through the Gradient AI Agent Cloud. DigitalOcean's comprehensive AI Ecosystem empowers startups and enterprises to build next-gen AI applications, offering choice and flexibility through embedded partner integrations and workflows. DigitalOcean's AI Ecosystem provides access to: Powerful Infrastructure: Efficient AMD and NVIDIA GPUs to power your applications. Advanced Models: Access to leading models from companies like OpenAI, DeepSeek, Meta, and Mistral. Applications & Frameworks: Popular AI dev tools and integration frameworks such as LangChain, LiteLLM, and dStack. Integrators: A network of AI specialists to help you migrate workflows and build robust new AI implementations. The DigitalAI Ecosystem "At the heart of AI's progress are the developers who are turning ideas into reality. The Gradient AI Ecosystem is a powerful force multiplier for them, proving that the future isn't just about silicon--it's about software and the collaborative community built on top of it," said Anush Elangovan, VP of AI Software at AMD. "By providing high-performance AMD GPUs through DigitalOcean's Gradient AI Agentic Cloud, we ensure the ecosystem is powered by world-class, open-standard hardware. We're not just providing infrastructure; together we're powering the software and the community that will invent tomorrow's AI." Through the dynamic Gradient AI Ecosystem, AI startups and digital native ## From Liège to Laravel: The Artisan of the Day Is Adrien Leloup. DevFeed: [From Liège to Laravel: The Artisan of the Day Is Adrien Leloup.]() Original publisher: [Read original article]() Author: Ana Tavares Published: 2025-08-23T12:16:30Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [PHP](), [Development](), [Tool](), [shaders](), [Vite](), [debugging](), [Bluesky](), [Livewire]() Tags: [community](), [debugging](), [dev](), [dev-tools](), [laravel](), [launch](), [macos](), [php](), [vite](), [web]() ### AI overview This developer profile features Adrien Leloup, a full-stack developer in Liège who has built more than 100 Laravel-based web projects at Whitecube. It also covers his PHPxBrussels community work, Hiker.dev tool, Laravel Ignition plugin, and experiments with shaders, Vite, Livewire, middleware, and macOS developer tools. ### Source excerpt Belgian developer Adrien Leloup builds with Laravel at Whitecube, co-leads PHPxBrussels, and is launching Hiker.dev in early access. ## Building a VSCode Chat Extension to Order Lunch DevFeed: [Building a VSCode Chat Extension to Order Lunch]() Original publisher: [Read original article]() Author: Andrew Hamilton Published: 2025-03-07T02:21:47Z Content type: tutorial Language: en Sources: [Blog -- Neon Docs]() Topics: [dev-tools](), [AI Chat]() Tags: [api](), [building](), [community](), [copilot](), [dev-tools](), [extension](), [extensions](), [llm](), [reverse-engineering](), [typescript]() ### AI overview A tutorial on building a VS Code Chat extension that lets Copilot order lunch through LLM tool calls. It describes reverse engineering Grubhub's ordering requests and introducing the TypeScript-based extension architecture. ### Source excerpt Are you ever so deeply in the developer grindset that you forget to eat? Me neither. But like most VC-backed companies, I wanted to solve a problem that does not exist 🙂 (not yet at least!) So, we decided to build an extension able to order us cheesburguers for lunch. The Stack... ## Issue no.7: Building better DevFeed: [Issue no.7: Building better]() Original publisher: [Read original article]() Author: Figma Published: 2024-10-17T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Developer experience](), [dev-tools](), [Figma](), [vs-code]() Tags: [amazon](), [atlassian](), [best-practices](), [design](), [dev](), [dev-tools](), [developer-experience](), [streaming](), [vs-code](), [workflows]() ### AI overview Figma's seventh Share issue examines developer experience as a company-wide practice shaped by cross-functional culture, principles, and processes. It presents perspectives from Atlassian, Linear, and VS Code on protecting developer flow, cultivating developer joy, guiding product experiences with strong opinions, and improving design-development collaboration through Dev Mode and design systems. ### Source excerpt The conversation around developer experience has changed. ## DevTools Academy: An Open Source Blog for Developer Tool Insights DevFeed: [DevTools Academy: An Open Source Blog for Developer Tool Insights]() Original publisher: [Read original article]() Author: TheAnkurTyagi Published: 2024-10-03T13:28:54Z Content type: article Language: en Sources: [ByteSizedBets]() Topics: [dev-tools](), [Open Source](), [GitHub](), [Nextra](), [Tailwind CSS](), [Prisma]() Tags: [blog](), [css](), [dev-tools](), [developers](), [next-js](), [open-source](), [prisma]() ### AI overview An update from ByteSizedBets introduces DevTools Academy, a blog focused on helping developers choose tools for SaaS projects through reviews and comparisons. The post also describes its technology stack, early traffic, open-source participation, and planned comparison articles. ### Source excerpt A special blog made for Developers ## What's new in Svelte: December 2023 DevFeed: [What's new in Svelte: December 2023]() Original publisher: [Read original article]() Author: Dani Sandoval Published: 2023-12-01T00:00:00Z Content type: release Language: en Sources: [Svelte blog]() Topics: [releases](), [dev-tools]() Tags: [changelog](), [dev-tools](), [release](), [svelte](), [typescript]() ### AI overview Svelte's December 2023 update announces a Svelte 5 preview, native TypeScript support, new effect runes, and SvelteKit updates including image preprocessing and Node.js 20 support through the Vercel adapter. ### Source excerpt Svelte Summit Fall 2023 was epic! Featuring talks from across the ecosystem and the launches from the core team of new Svelte Dev Tools, image optimization, and a preview version of Svelte 5.0! The whole talk can be found here (timestamps below): 0:00 Hype music! 18:20 Exploring Svelte DevTools - Ignatius B (4 minutes) 25:27 How does SvelteKit fare as a SPA Framework - Henry Lie (25 minutes) 53:00 enhanced:img - Ben McCann (6 minutes) 1:03:44 inlang-paraglide JS for SvelteKit i18n - Samuel Stroschein (10 minutes) 1:17:32 How Svelte & GraphQL plays well together - Jean-Yves Couet (31 minutes) 1:53:10 svelte-ecosystem-ci - Dominik G (10 minutes) 2:23:06 Svelte for Creative Development - Steven Stavrakis (10 minutes) 2:35:33 Translating the docs - Romain I'Ourson (11 minutes) 2:49:48 ENHANCE! - Paolo Ricciuti (25 minutes) 3:18:25 Accessibility tips with Svelte solutions - Enrico Sacchetti (25 minutes) 3:49:11 svelte@next - Rich Harris (18 minutes) Today is also the first day of Advent of Svelte: A Svelte challenge for each day of December. Join the festivities and participate in a daily frontend challenge using Svelte! Now let's dive into the updates... What's new in Svelte (5.0 Preview!) Svelte 5 preview is now available at svelte@next while Svelte 4's current version (@latest) is 4.2.7. All the changes below are from the preview's branch: TypeScript is now supported natively via acorn-typescript (5.0.0-next.9, #9482) The new $effect.active rune returns a boolean to indicate if an effect is active. This lets you set up subscriptions when a value is read (in an effect, or in the template) but also read values without creating subscriptions (5.0.0-next.10, Docs, #9591) The new $effect.root rune creates a non-tracked scope that doesn't auto-cleanup. This is useful for nested effects that you want to manually control (5.0.0-next.14, Docs, #9638) For all the release notes going forward, check out the CHANGELOG on main. For the highlights, take a look below! What's new in S ## Making Figma better for developers with Dev Mode DevFeed: [Making Figma better for developers with Dev Mode]() Original publisher: [Read original article]() Author: Kris Rasmussen Published: 2023-06-21T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [dev-tools](), [Front end]() Tags: [bridging](), [dev-tools](), [developer](), [development](), [development-tools](), [figma]() ### AI overview Figma introduces Dev Mode, a dedicated workspace that helps developers inspect designs, access implementation details, export assets, and connect design concepts with code, icons, and tokens. It is intended to reduce friction between design and development workflows. ### Source excerpt How can a design tool work better for developers? It's a question we've been asking ourselves and our community. Today, we're excited to introduce Dev Mode, a new workspace in Figma that's designed to get developers what they need, when they need it, harnessing the tools they use every day. ## From Tweetbot and Twitter to Mastodon and Ivory DevFeed: [From Tweetbot and Twitter to Mastodon and Ivory]() Original publisher: [Read original article]() Author: Erik Runyon Published: 2023-01-26T00:00:00Z Content type: opinion Language: en Sources: [Erik Runyon]() Topics: [Mastodon](), [X (Twitter)](), [dev-tools]() Tags: [apps](), [communications](), [dev-tools](), [social-media](), [twitter]() ### AI overview The author explains why Tweetbot had been their preferred way to use Twitter and describes moving to Mastodon after Tweetbot disappeared. Access to Tapbots' Ivory has made the author feel they no longer miss Twitter, although they hope for a Mac version of Ivory. ### Source excerpt To the best of my memory Tweetbot has been my window into Twitter since pretty close to when it was released. I open Twitter's web interface from time to time when I had to, but it has not been my primary way to use the service for well over a decade. There are multiple reasons I was fine with living as a second-class Twitter citizen. Primarily no ads, no algorithmic timeline, and syncing between mobile/desktop clients. I use a three monitor setup at both home and the office. The left is always my laptop, and the right is a vertical 24-inch monitor. That right monitor is used for two purposes. A browser with dev-tools docked to the bottom (the extra vertical space is quite nice). All my social/communications apps. This typically includes Slack, Messages, Discord, and up until recently Tweetbot. Having them all together on one screen (and covered by a browser the majority of the time) cuts down on distractions coming from any of them. However, for the last two weeks there has been no Tweetbot. It's former home now a glaring absence showing the desktop below. And gone with it is my consumption of Twitter. To say I dislike the Twitter web interface and native apps is an understatement. So for the past two weeks I've been exclusively on Mastodon. And since I've gained access to Ivory (by Tapbots) I've found I don't miss Twitter. The community on Mastodon has been growing rapidly, so if you've been putting off trying it out, I would encourage you to at least set up an account and start lurking. So like many others, outside of posting to my teams work account, I'm done with Twitter. The new management have made it place I no longer want or need to be. So if you need me, I'll be over on webperf.social Mastodon. And hopefully soon there will be a Mac version of Ivory to take up residence in that glaring Tweetbot shaped hole. ## Use Firefox for accessibility testing DevFeed: [Use Firefox for accessibility testing]() Original publisher: [Read original article]() Author: Todd Libby Published: 2022-07-17T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [Firefox](), [dev-tools](), [browsers](), [Web]() Tags: [accessibility](), [accessibility-tools](), [audits](), [browsers](), [dev-tools](), [developer](), [firefox](), [testing](), [web]() ### AI overview This article explains how to use Firefox's built-in accessibility tools for web accessibility testing. It covers the Accessibility tab, accessibility-tree inspection, color-contrast, keyboard and form-label checks, visual simulations for different color-vision conditions, tabbing-order visualization, and Checks and Properties panels. ### Source excerpt Firefox has become one of the best tools for accessibility audits. Let's go over Firefox's accessibility features that you can use today. Built-in accessibility tools In this article I'll discuss The Accessibility Tab, where we will begin and then move through to each component of the Accessibility Tab. First, the Check for issues tab, the Simulate menu, and end with the Show Tabbing Order checkbox. I'll finish with the Checks and Properties panel. The Accessibility tab Whenever you right-click on an element in a page, you can select Inspect Accessibility Properties to directly view that element in Firefox's accessibility tools. Similarly, if you're using the Inspector pane in Firefox's dev tools, you can right-click on any node and choose Show Accessibility Tools to view that node in Firefox's accessibility tools. Firefox's built-in accessibility tool is probably one of the best features in browsers' dev tools out there now. It shows you the current web page's accessibility tree, and it has panels for color-contrast checks and the current node's accessibility-tree properties. You can traverse the accessibility tree, and as you hover over each node, Firefox will show a tooltip over that node in the viewport with the name of the node and some basic properties. And the Checks and Properties panels can show you all the pertinent information for that node like its color and contrast ratio, name, role, and value. The Check for issues menu If you enable this handy feature, Firefox can check for color-contrast issues,it can do its best to try to find keyboard issues, and it can try to find form-label issues. There's also an All Issues option that will run all of those checks for the page. Each issue will show you the role and name of the element that has an issue, and the Checks and Properties panels will provide some information and values to help you resolve the issues. The Simulate menu This is a great tool for simulating visual differences. This can simulate: Protanopi ## Apollo Explorer can now be embedded with private graph variants DevFeed: [Apollo Explorer can now be embedded with private graph variants]() Original publisher: [Read original article]() Author: Parul Schroff Published: 2022-06-07T10:44:27Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [ide](), [apollo-client](), [dev-tools]() Tags: [apollo-client](), [dev-tools](), [documentation](), [graphql](), [ide](), [tooling]() ### AI overview Apollo announces that Explorer can be embedded on websites, documentation, and developer portals with public or private graph variants. Embedded Explorer stays synchronized with the Apollo Studio schema, and visitors can authorize access or sign up and receive invitations when permitted. ### Source excerpt Embed private graphs, use embeds to invite new users, and use improved Apollo Client Dev Tools. Explorer is an incredible GraphQL IDE that makes it quick and easy to browse schemas and run operations against them. It's so awesome, that our community asked us to make it embeddable so that it could be used anywhere - and last year, we did just that! But at the time, you could only embed public graph variants. ## Should I Open Source my Company? DevFeed: [Should I Open Source my Company?]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2022-03-25T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Open Source](), [Software](), [Code quality](), [dev-tools]() Tags: [code-quality](), [dev-tools](), [open-source](), [security](), [software]() ### AI overview The article discusses Supabase's experience of being open source from the beginning and argues that building a company in public can produce unexpected benefits. It addresses concerns about messy code, security vulnerabilities, and intellectual-property theft, then explains how community involvement can improve code quality, attract contributors, and help developers learn from existing projects. ### Source excerpt The unexpected upsides of building in public ## How we launch at Supabase DevFeed: [How we launch at Supabase]() Original publisher: [Read original article]() Author: Ant Wilson Published: 2021-11-26T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Databases](), [dev-tools](), [hosting](), [Web](), [Cloud]() Tags: [auth](), [bugs](), [company](), [course](), [databases](), [demo-day](), [dev](), [dev-tools](), [feature](), [growth](), [home-page](), [hosting](), [launch](), [open-source]() ### AI overview Supabase explains the history and methodology behind its Launch Week as part of a product-led growth strategy. The article describes how open development, public launches, community exposure, and rapid iteration helped Supabase grow its hosted databases and respond to demand with products such as Supabase Auth. ### Source excerpt The history and methodology of Supabase Launch Week. ## EU Funding for Dev Tools for the Decentralized Web DevFeed: [EU Funding for Dev Tools for the Decentralized Web]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2021-09-15T12:00:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [dev-tools](), [ZeroNet](), [IPFS](), [WebRTC](), [Ethereum](), [interception](), [debug](), [Testing](), [Logging](), [Script]() Tags: [announcements](), [applications](), [decentralized-web](), [dev-tools](), [development](), [ethereum](), [funding](), [interception](), [logging](), [open-source](), [webrtc]() ### AI overview HTTP Toolkit received EU Horizon funding through the Next Generation Internet initiative to expand its interception, debugging, and testing capabilities for decentralized-web applications. The project will focus on IPFS, WebRTC, and Ethereum, with results released under free and open-source licenses. ### Source excerpt Through the Next Generation Internet (NGI) initiative, HTTP Toolkit has been selected for funding from the EU's Horizon research & innovation program, to expand beyond HTTP and offer the same interception, debugging & testing functionality for applications built on top of the decentralized web. This is going to be a huge opportunity to invest in expanding HTTP Toolkit to support some very exciting new technologies, and extending existing core functionality to do so along the way. For this project I'm going to be specifically focusing on 3 main protocols that today form the backbone of the decentralized web: IPFS, WebRTC & Ethereum. For each of these protocols, the essential technologies are usable now, but the wider ecosystem and uptake is still in their infancy. I think it's clear that most mainstream web developers are not currently using these technologies to build production-grade decentralized applications. There are many reasons for this, but one is a lack of high-quality developer tooling. Moving from traditional client/server architectures to building decentralized applications requires developers to replace many day-to-day debugging & testing tools with manual logging, custom scripts and guesswork. This tooling gap makes decentralized development significantly more difficult. The goal here is to fix that, by providing modern tools for the future of the web. This is funded as part of the NGI Pointer project, funding me as an individual to work on this for a year, with all the resulting output to be available under free & open-source licenses (of course, HTTP Toolkit is conveniently already 100% open-source, so that's no change at all). If you're interested in the future of the web and you think developer tooling matters, I hope this is very exciting! If you're an existing HTTP Toolkit user though and you're only interested in HTTP, don't worry. This is equity-free R&D funding, so HTTP Toolkit remains a completely independent open-source project, and although ## Open Sourcing Intervene DevFeed: [Open Sourcing Intervene]() Original publisher: [Read original article]() Published: 2020-05-05T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Intervene](), [Mocking](), [TypeScript](), [BFF](), [Web](), [Processes](), [browser](), [JavaScript](), [API]() Tags: [api](), [bff](), [browser](), [code](), [configuration](), [dev-tools](), [documentation](), [frontend](), [http](), [http-server](), [intervene](), [javascript](), [mocking](), [node-js](), [open](), [process](), [proxy](), [tools](), [typescript](), [web](), [web-development]() ### AI overview SoundCloud open-sources Intervene, a Node.js process that acts as a single-host proxy for altering requests and responses during frontend development. It supports endpoint overrides, TypeScript or JavaScript configuration, automatically trusted self-signed HTTPS certificates, and repository-shared mocks. ### Source excerpt A little while back, the web team at SoundCloud got an urgent report that our upload page looked weird in the US. Web engineering is based... [Next page]()