#webdevelopers — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #webdevelopers, aggregated by home.social.
-
📆 21 May 2026 - tomorrow!
"What Are Web Developers Doing About Security?" by @torgo at the Open Source SSF Community Day, Minneapolis, MN, USA 🇺🇸
In this talk Dan Appelquist, Samsung Open Source Group, will give a brief introduction to SWAG, an overview of the surprising results, what it means for the work ahead and how web developers and web browser developers are responding to the requirements of the CRA
#WebStandards #WebSecurity #WebDevelopers #OpenSSFCommunityhttps://www.w3.org/events/talks/2026/what-are-web-developers-doing-about-security/
-
Dear #WebDevelopers what is so damn hard in just showing the error message from the backend on the UI instead of "Something went wrong."?
-
Dear #WebDevelopers what is so damn hard in just showing the error message from the backend on the UI instead of "Something went wrong."?
-
Dear #WebDevelopers what is so damn hard in just showing the error message from the backend on the UI instead of "Something went wrong."?
-
Dear #WebDevelopers what is so damn hard in just showing the error message from the backend on the UI instead of "Something went wrong."?
-
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].
[1] https://sfsymbolslib.layered.work
[2] https://github.com/phranck/sf-symbols-lib -
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].
[1] https://sfsymbolslib.layered.work
[2] https://github.com/phranck/sf-symbols-lib -
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].
[1] https://sfsymbolslib.layered.work
[2] https://github.com/phranck/sf-symbols-lib -
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].
[1] https://sfsymbolslib.layered.work
[2] https://github.com/phranck/sf-symbols-lib -
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].
[1] https://sfsymbolslib.layered.work
[2] https://github.com/phranck/sf-symbols-lib -
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? -
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? -
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? -
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? -
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? -
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 ? -
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 ? -
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 ? -
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 ? -
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
-
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
-
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
-
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
-
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
-
📆 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/ -
📆 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/ -
📆 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/ -
📆 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/ -
📆 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 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.
-
Relaunching Do the Woo Podcast for the WooCommerce Ecosystem
Today we are officially announcing the relaunch of Do the Woo as a fully dedicated WooCommerce podcast under the Open Channels network. The show returns with a new mission, a refined focus, and a commitment to becoming the central place where the entire WooCommerce ecosystem can learn, share, and connect. More information about the relaunch is available at dothewoo.com. WooCommerce has grown into a large, diverse, and fast-moving ecosystem. It powers millions of stores, supports thousands of […]https://openchannels.fm/relaunching-do-the-woo-podcast-for-the-woocommerce-ecosystem/
-
Relaunching Do the Woo Podcast for the WooCommerce Ecosystem
Today we are officially announcing the relaunch of Do the Woo as a fully dedicated WooCommerce podcast under the Open Channels network. The show returns with a new mission, a refined focus, and a commitment to becoming the central place where the entire WooCommerce ecosystem can learn, share, and connect. More information about the relaunch is available at dothewoo.com. WooCommerce has grown into a large, diverse, and fast-moving ecosystem. It powers millions of stores, supports thousands of […]https://openchannels.fm/relaunching-do-the-woo-podcast-for-the-woocommerce-ecosystem/
-
Relaunching Do the Woo Podcast for the WooCommerce Ecosystem
Today we are officially announcing the relaunch of Do the Woo as a fully dedicated WooCommerce podcast under the Open Channels network. The show returns with a new mission, a refined focus, and a commitment to becoming the central place where the entire WooCommerce ecosystem can learn, share, and connect. More information about the relaunch is available at dothewoo.com. WooCommerce has grown into a large, diverse, and fast-moving ecosystem. It powers millions of stores, supports thousands of […]https://openchannels.fm/relaunching-do-the-woo-podcast-for-the-woocommerce-ecosystem/
-
Relaunching Do the Woo Podcast for the WooCommerce Ecosystem
Today we are officially announcing the relaunch of Do the Woo as a fully dedicated WooCommerce podcast under the Open Channels network. The show returns with a new mission, a refined focus, and a commitment to becoming the central place where the entire WooCommerce ecosystem can learn, share, and connect. More information about the relaunch is available at dothewoo.com. WooCommerce has grown into a large, diverse, and fast-moving ecosystem. It powers millions of stores, supports thousands of […]https://openchannels.fm/relaunching-do-the-woo-podcast-for-the-woocommerce-ecosystem/
-
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. […] -
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. […]
