# front-end-development Front-end development builds user-facing interfaces using technologies such as HTML, CSS, and JavaScript. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Tailwind UI is now Tailwind Plus DevFeed: [Tailwind UI is now Tailwind Plus]() Original publisher: [Read original article]() Published: 2025-03-04T16:00:00Z Content type: release Language: en Sources: [Tailwind CSS Blog]() Topics: [Tailwind CSS](), [ui](), [front-end-development](), [Documentation]() Tags: [components](), [content](), [documentation](), [events](), [front-end-development](), [project](), [resources](), [tailwind](), [ui](), [update]() ### AI overview Tailwind UI has been rebranded as Tailwind Plus without changing its one-time pricing, lifetime access, existing content, or upgrade terms. The announcement describes possible future additions such as saved Tailwind Play experiments, editor themes, color palettes, typography themes, a private community, beta documentation access, and early event registration, alongside continued investment in components, templates, and Catalyst. ### Source excerpt We just shipped a huge rebrand project, turning what was previously known as Tailwind UI into Tailwind Plus. Tailwind Plus is the all same high-quality resources you know from Tailwind UI, but with all-new possibilities and potential. ## The skills, complexity, and learning curve of modern front-end development DevFeed: [The skills, complexity, and learning curve of modern front-end development]() Original publisher: [Read original article]() Author: Mads Brodt Published: 2024-05-01T15:01:34Z Content type: opinion Language: en Sources: [Front-End Focus]() Topics: [front-end-development](), [Front end](), [JavaScript](), [Web Development](), [React](), [Vue.js](), [web applications]() Tags: [complexity](), [development](), [front-end](), [front-end-development](), [javascript](), [learning](), [react]() ### AI overview Modern front-end development has expanded beyond HTML and CSS to include JavaScript, frameworks, architecture, tooling, accessibility, and related skills. This broader ecosystem enables richer web experiences but also increases complexity and the learning curve for developers. ### Source excerpt Front-end development has evolved a lot over the years. ## Lift-off: The MDN Curriculum launch DevFeed: [Lift-off: The MDN Curriculum launch]() Original publisher: [Read original article]() Author: hermina-condei Published: 2024-02-27T00:00:00Z Content type: release Language: en Sources: [MDN Blog]() Topics: [front-end-development](), [Web Development](), [Learning](), [Accessibility](), [Responsive Design]() Tags: [accessibility](), [article](), [front-end-development](), [launch](), [learn](), [web-development]() ### AI overview MDN has launched its freely accessible Curriculum, a structured guide to the essential topics and trusted learning resources for front-end web developers. The article explains the curriculum's purpose, organization, and intended use. ### Source excerpt The long-awaited MDN Curriculum is now live on MDN, providing a structured guide to the essential front-end development skills and best practices for industry newcomers. Learn all the key details in this article. ## From Junior to Lead Front-End Developer: A Six-Year Career Journey and Lessons DevFeed: [From Junior to Lead Front-End Developer: A Six-Year Career Journey and Lessons]() Original publisher: [Read original article]() Author: Mads Brodt Published: 2024-01-10T16:01:18Z Content type: opinion Language: en Sources: [Front-End Focus]() Topics: [front-end-development](), [Front end](), [Development]() Tags: [career-progression](), [developer](), [front-end-development](), [junior-developer]() ### AI overview A front-end developer describes progressing from a first coding job in 2018 to Lead front-end developer in 2024. The article shares personal lessons on communicating career goals, understanding expectations for the next level, and working toward promotions. ### Source excerpt I got my first coding job in 2018, and I've just now been promoted to Lead front-end developer in 2024. This is my journey and lessons to help you to do the same. ## My Career Pivot: From Retail to Engineering DevFeed: [My Career Pivot: From Retail to Engineering]() Original publisher: [Read original article]() Author: Skyscanner Engineering Published: 2022-06-22T09:59:02Z Content type: opinion Language: en Sources: [Stories by Skyscanner Engineering on Medium]() Topics: [Software Engineering](), [Development](), [Front end](), [Bootcamp](), [front-end-development]() Tags: [career](), [career-change](), [course](), [developer](), [front-end-development](), [software-engineer](), [software-engineering](), [women-in-tech]() ### AI overview Louise Reid describes moving from retail and system support into software engineering. She discusses online courses, a 16-week CodeClan bootcamp, her time as an instructor, and her eventual focus on front-end development before joining Skyscanner. ### Source excerpt Louise Reid, Software Engineer As we celebrate International Women in Engineering Day this week, we're profiling female-identifying engineers across Skyscanner's business. Here, Louise Reid tells us how she took the leap from retail to software engineering, what her day to day looks like, her advice for anyone looking to career change, and how the perception of engineering being male-dominated is changing. Louise, you didn't set out to be an engineer -- what was the path that took you from retail to where you are now? I didn't: I have a honours degree in Business and Management. Honestly, going through school, the concept of working as a software developer was so far off my radar. During my degree I worked in hospitality and really enjoyed it, so for a while saw myself working in hospitality management in some shape or form. After uni I travelled in Australia for a bit and then went back to my role in retail with a large well-known shoe retailer, before moving to head office there and working in system-support for the stores. At 29 I found myself in a job that didn't excite me and wasn't really going anywhere. I was really good at my job, but there wasn't a huge amount much transferable knowledge I could take from it into other roles, as a lot of it was in house-built systems. I was also at the level that any progression was reliant on someone above me leaving or the company expanding in some way. It wasn't until I started working with developers there that I started to think of software engineering as a path I could take too. I dipped my toe in the water a little, doing some free online courses with Code Academy, which I really enjoyed. I was then pointed in the direction of CodeClan by my line manager and introduced to their 16 week software development bootcamp. After completing the course I still had a sense of "I don't know what I want to do" and whilst I got offered a few development roles, none of them really excited me. I ended up staying at CodeClan as a cla ## Enabling keyboard culture with No Mouse Days DevFeed: [Enabling keyboard culture with No Mouse Days]() Original publisher: [Read original article]() Author: Marcy Sutton Published: 2020-10-15T00:00:00Z Content type: article Language: en Sources: [The A11Y Project]() Topics: [Accessibility](), [inclusive design](), [front-end-development](), [npm](), [CSS]() Tags: [accessibility](), [css](), [front-end-development](), [inclusive-design](), [npm](), [processes](), [tooling](), [web]() ### AI overview The article advocates regular mouse-free testing to reveal keyboard and screen reader accessibility problems in websites and applications. It introduces No Mouse Days, an npm package that hides the mouse cursor with CSS, and encourages teams to use the practice to identify inaccessible controls and missing focus outlines early. ### Source excerpt Wouldn't it be great if designers and developers tested their digital experiences for keyboard accessibility on the regular? And by extension, screen reader accessibility? That's where the #NoMouse challenge and No Mouse Days come in. The DO-IT Center at University of Washington originally started the No Mouse challenge, complete with its own website, logo, and hashtag to spread awareness about the need for keyboard-accessible websites and applications. The challenge is pretty straight-forward: Step 1. Use the Web without a mouse. Can you access all features? Can you reach and operate all interactive controls? Can you easily tell where you are on the page? Step 2. Learn more about accessible web design. Step 3. Spread the Word! Building on that initiative came No Mouse Days, an npm package that disables the mouse cursor on web pages with CSS. It started as a cheeky joke, and then it actually became popular. The idea of No Mouse Days was to make it easy to hide the mouse cursor so it would become extremely obvious when a user interface didn't support the keyboard, perhaps disabling it automatically for front-end development one day a week. If you have further ideas for No Mouse Days or other culture-changing techniques, contributions are always welcome on GitHub and Twitter! No matter how you go about it, establishing a mouse-free development day at least once a week could work wonders for people who can't use a mouse at all. You might find interactive controls that aren't actually interactive for large segments of the population and lacking visible focus outlines which make keyboard navigation difficult. Surfacing issues with keyboard-support early and often will give teams something to react to, and hopefully dedicated tooling and processes can make it second nature through more inclusive design and development. ## Tell Your Stories: The Benefits of Strategic Engineering Communications DevFeed: [Tell Your Stories: The Benefits of Strategic Engineering Communications]() Original publisher: [Read original article]() Author: Jaime Woo Published: 2017-10-25T19:30:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Shopify](), [Production Engineering](), [front-end-development](), [data-engineering](), [GraphQL](), [Rails]() Tags: [articles](), [data-engineering](), [developers](), [development](), [engineering](), [front-end-development](), [production-engineering](), [shopify](), [technical]() ### AI overview Shopify established a formal engineering communications function as the company grew across offices and technical teams. The initiative shared engineering knowledge internally, communicated Shopify's work externally, supported recruitment, reduced duplicated work and mistakes, and encouraged cross-team idea sharing through technical talks, newsletters, and approachable articles. ### Source excerpt In early 2016, we faced a problem at Shopify. We were growing quickly, and decisions could no longer be made across the room, so to speak. Four offices became five, accommodating that growth raised interesting questions like: how would new people know the history of the company, and how could existing Shopifolk keep up with new developments? In addition to sharing knowledge inside the company, we also wanted to let people outside Shopify know what we were working on to give back to the community and to support recruitment efforts. Engineering communications was born to solve a specific problem. A valued saying here is "do things, tell people," but, while we're very good at the first part, we weren't living up to expectations on the second. Ad hoc worked when we were smaller, but with technical stories now coming from teams as varied as production engineering, mobile, front-end development, and data engineering, we needed something more formalized. Strong communications inside the engineering team could help prevent the overlap of work by different teams or the duplication of mistakes, and it could support cross-pollination of ideas. ## Lessons Learned at IBM Design DevFeed: [Lessons Learned at IBM Design]() Original publisher: [Read original article]() Published: 2016-04-12T00:00:00Z Content type: article Language: en Sources: [Una Kravets]() Topics: [ibm](), [Front end](), [front-end-development](), [Testing](), [Sass](), [Git]() Tags: [engineering](), [front-end](), [front-end-development](), [git](), [ibm](), [sass](), [testing]() ### AI overview A retrospective on lessons learned during nearly two years at IBM Design, focusing on enthusiasm for collaboration, interdisciplinary rapport, and an iterative design process of building, testing, and refining solutions. ### Source excerpt I've learned so much during my time at IBM Design! This is a little wrap up post and an announcement about my next adventure. ## Why FINN.no adopted Node.js and npm for front-end development DevFeed: [Why FINN.no adopted Node.js and npm for front-end development]() Original publisher: [Read original article]() Author: espen Published: 2013-12-03T10:38:00Z Content type: opinion Language: en Sources: [Finn.no]() Topics: [npm](), [Front end](), [front-end-development](), [Development]() Tags: [front-end](), [front-end-development](), [maven](), [npm](), [technology-stack]() ### AI overview FINN.no describes its transition from Java-only front-end tooling to a Node.js and npm-based toolset, motivated by the Node ecosystem and its available modules. The article also discusses using Karma and frontend-maven-plugin to integrate Node projects into existing Java projects, and supporting npm through its scale campaign. ### Source excerpt What? Why is FINN.no donating to scale NPM? I thought you guys were a pure Java shop? It is true, we used to be a pure Java-shop. However over the past three years we have adopted new technologies to solve specific problems. We have used Ruby and Cucumber for some time to make a platform for continuos delivery and it has worked out beautifully! Our front-end developers have been forced to deal with out dated and not suitable tools for doing their job. This is largely due to the fact that all innovation when it comes to front-end development does not happen in the Java community. Most of the exciting tools are written in Node and this has become a frustration and a challenge for us. In the past year FINN have been gradually making a transition away from using only Java-based tools for front-end development and towards a NodeJS powered tool set. We are now at a point were we are on the brink of rolling this out for our projects. Having worked with Node for a while we have learned to appreciate the Node ecosystem which is NPM. Being part of such a vibrant ecosystem of modules makes the transition easier and it also inspires us to become better at giving back. Therefore we are trying to give back to NPM, when we can. When the scale NPM campaign was launched it was obvious that this was something we wanted to be apart of. It is an investment in our own happiness in a sense, as NPM is becoming a very important part for our technology portfolio. Nodeify all the things So were is it that we use Node in our technology stack today? Earlier this year we moved away from JsTestDriver in favor of Karma-runner. This meant that we needed to create a trojan horse containing the goodness of Node/NPM into existing Java projects without causing too many problems for developers with no knowledge of Node. A part of this scheme was the frontend-maven-plugin, which enables us to have control of which Node projects use and allows developers without Node previously installed to build project ## Developers We Admire. DevFeed: [Developers We Admire.]() Original publisher: [Read original article]() Author: Paul Irish Published: 2012-08-17T18:46:00Z Content type: article Language: en Sources: [Paul Irish]() Topics: [front-end-development](), [Open Source](), [Front end](), [CSS](), [HTML5](), [SVG](), [Document Object Model (DOM)](), [debug](), [API](), [browsers](), [Graphs](), [data]() Tags: [accessibility](), [api](), [articles](), [css](), [developers](), [front-end](), [front-end-development](), [graphs](), [html5](), [javascript](), [open-source](), [svg](), [web-browsers]() ### AI overview An appreciative survey of front-end developers whose teaching, open-source contributions, research, and evidence-based opinions have benefited the web development community. It highlights work involving Modernizr, polyfills, DOM APIs, source maps, HTML5 Boilerplate, CSS, browser compatibility data, accessibility, JavaScript libraries, and SVG. ### Source excerpt One of the good things about having the eyeballs of many people is that you now have the ability to throw other people into the limelight that completely deserve to be in it. Divya Manian and I have been, for a while now, putting together a list of people in the front-end development community who, in our opinion, could use more broad acknowledgment and attention. They're also inspiring because... They are excellently skilled in their area of expertise and go out of their way to teach others how to gain these skills They participate in open source projects that fuel the community's knowledge and productivity They have independent opinions that are derived out of testing, and evidence-based fact finding worthy of learning from So, here is a list of people we admire: Ryan Seddon: @ryanseddon aka the CSS Ninja develops Modernizr, writes polyfills, and explores the edge of DOM APIs. His recent exploration of source maps lays a lot of groundwork for future web debugging potentials. Hans Christian Renl: @drublic started contributing extensively to HTML5 Boilerplate and has been actively engaged in other projects we have worked on. He also maintains a blog where he shares his learning experiences and explorations of advanced CSS features. Alexis Deveria: @fyrd maintains caniuse.com, and contributes to svg-edit, the open source svg editor. He also created & maintains the canonical timeline of web browsers which has been the basis of other browser history graphs since. He also upstreams all the data from caniuse.com to its API, is used to power sites such as api.html5please.com and html5rocks.com Jason Kiss: @jkiss's notes on accessibility are like a breath of fresh air into the dense field of accessibility. He tests in as many accessibility technology tools as available and bases his opinions on findings from his research. His articles are extremely valuable to web developers who have long had to base how to do the right thing on superstition and fact-free opinions. Kit Cambr