Want to stay relevant in tech for the next 5 years? 💻
Master the skills that truly matter.

👉 Check this out: https://go-techsolution.com/web-development-skills-that-matter-next-5-years/

#FutureTech #WebDevelopers #LearnToCode #TechIndustry #AITrends #Growth

Hey, #WebDevelopers... Want to use #Apple's SF Symbols in a web project? I've built something for that. No more tedious exporting from the SF Symbols app. Here's a live preview [1]. Use it right away with my sf-symbols-lib [2].

#SFSymbols

[1] https://sfsymbolslib.layered.work
[2] https://github.com/phranck/sf-symbols-lib

SF Symbols Library

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 #WebStandards #WebDevelopers

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, #WebDevelopers ?
Or at @w3c @tag #WebStandards ?

Search and Hash in URLs

Sometimes we parameterize a #URL 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 #WebStandards #WebDevelopers

1/3

Meet the W3C Technical Architecture Group

The W3C Technical Architecture Group (TAG) hosts a panel and Q&A for web developers who care about the web's architecture and direction.

W3C

📆 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
https://www.w3.org/events/happenings/2026/meet-the-w3c-technical-architecture-group/

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.