#webdevelopers

Heribert Schützhcschuetz
2026-02-15

3/3

Well, I can put both the routing parameters and the scroll target in the hash and implement the scrolling in JS. But that feels more complex than necessary.

Is there a standard solution for this? Or should we have yet another URL component that
- is only available to the client and
- does not interfere with the scrolling functionality of the hash component?

@w3c @tag

Heribert Schützhcschuetz
2026-02-15

2/3

Now I have a use case with client-side routing parameters where
A. I would prefer to keep the parameters in the client for data-protection reasons, and
B. I would still like to use the hash for scrolling within the page.

So where to put the parameters? Due to (A) I don't want them in the search and due to (B) I don't want them in the hash.

Any ideas, ?
Or at @w3c @tag ?

Heribert Schützhcschuetz
2026-02-15

Search and Hash in URLs

Sometimes we parameterize a to specify in detail what to display.
- The "search" (after a "?") can be used by the server but also by the client, e.g., for routing in a single-page application.
- The "hash" (after a "#") is only available to the client, where it is normally used to scroll to a particular element of a page. But it can also be used for client-side routing.

@w3c @tag

1/3

World Wide Web Consortiumw3c@w3c.social
2026-02-12

📆 4 March 2026 Meet the W3C Technical Architecture Group, London UK 🇬🇧

Are you a web developer, or content author, with questions about why the web is the way it is, how it's evolving, or suggestions on how it should evolve? Do you want to know more about how the standards that govern how the platform works are being developed? Have you ever wondered how your input can shape the web platform?

Learn more about the @tag panel and Q&A
#WebStandards #WebDevelopers
w3.org/events/happenings/2026/

W3C logo
In this episode of Do the Woo, hosts Katie and James discuss WooCommerce and AI with guest James LePage, exploring new features, tools, protocols, and the future of e-commerce.
Zach Stepek and Carl Alexander discuss winter challenges, work-life balance, and AI’s impact on coding. They emphasize the importance of diversifying skills and adapting to tech changes for career longevity.
In this episode of Do the Woo, guest Beau Lebens and hosts James and Katie chat about key WooCommerce topics, including community concerns, competitive advantages, AI developments, and the future of the WooCommerce ecosystem.
2026-01-29

@londondreamtime @tiggy

There's a Web Developer somewhere in #Meta who is looking at the 'some' in that headline and treating it as a bug report.

At least it's not a yes/no question, though. (-:

@ianbetteridge
#QuestionHeadlines #Facebook #Instagram #SkyNews #WebDevelopers #ConsentOrPay

In this episode of Open Web, host Anne chats with Juliette, the sole maintainer of PHP_CodeSniffer. They dive into the challenges of maintaining crucial open-source projects, funding issues, and AI's impact on software development.
In this episode, Anne Bovelett chats with Gehirngerecht founders Nina Jameson and Tobias Roppelt, discussing their mission to promote digital accessibility through engaging workshops and tools.
Didacahedronsubr00t
2025-12-25

Being a good backend developer is like being the healer in a DnD group: you get none of the credit for impressing the program owners, and you doing a good job is dependent on you constantly supressing your own ego in order to do what is best for the group.

NERDS.xyz – Real Tech News for Real Nerdsnerds.xyz@web.brid.gy
2025-12-20
2025-12-16

Relaunching Do the Woo Podcast for the WooCommerce Ecosystem

The Do the Woo podcast is relaunching as a dedicated platform for the WooCommerce community, focusing on unique challenges and innovations, hosted by James Kemp and Katie Keith.

openchannels.fm/relaunching-do

James Kemp and Katie Keith co-hosting a discussion about WooCommerce at a conference, with a presentation screen in the background.
The "Do the Woo" podcast is returning, focusing on WooCommerce insights, featuring industry leaders. It will include lively discussions, audience Q&As, and monthly episodes with hosts James Kemp and Katie Keith.
Zach Stepek and Carl Alexander recap their 2025 experiences, highlighting personal growth, industry events, business developments, and health journeys. They emphasize gratitude and reflect on goals for a promising 2026.
In this episode, host Anne Bovelett sits down with Troy Chaplin, a well-known figure in the WordPress community and an advocate for web accessibility. Together, they dive into the importance of accessibility in web development, sharing personal stories about what sparked their passion for the topic and how it has influenced their careers. You’ll hear practical advice on fostering accessibility within development teams, insights on the challenges faced by newcomers, and why breaking down barriers to accessible resources is crucial. The conversation also explores Troy Chaplin’s hands-on experience building an accessibility plugin for a major Canadian university, discussing not only the technical hurdles but also the organizational benefits such as saving time and money by making web content easier for everyone to use. Anne and Troy touch on the role of AI in accessibility work, the importance of community-driven resources, and why a positive, collaborative approach is key to educating developers and designers alike. If you’re interested in making the web a more inclusive place or just curious about the intersection of WordPress, accessibility, and real-world impact, this is an episode you won’t want to miss. […]

Why Diverse Teams and Early Accessibility Matter in Web Development

Accessibility in web dev shouldn’t be an afterthought. Involving diverse teams from the start uncovers issues early, making products better for all. Early focus on accessibility is key.

openchannels.fm/why-diverse-te

2025-11-03

Could it be modern #webdevelopers feel uneasy, uncertain, unsafe when they don't wrap their stuff with a <div class="lengthy-class-name">? Like when you don't use a seatbelt in the car maybe, or go naked to work. Just add a wrapper, and then a wrapper around the wrapper, just in case.

We have an in-depth conversation on custom tables including a recent experience with them migrating from Joomla to WordPress and WooCommerce.

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst