You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Standards-compliant.
Optimized for mobile. I take a mobile-first approach to building front-ends.
Fully responsive, and tested across various devices and browsers.
Cross-browser compatible. While I don't optimize for older browsers (especially the IEs), the interfaces I build are usually usable in those browsers. A Web site doesn't need to look the same in all browsers. (If you need a developer to create the exact same experience in all browsers, you're probably better off working with someone else.)
Accessible. A product needs to be usable by users of assistive technologies by default. This is a requirement and something I don't compromise on.
Progressively enhanced. This means that the front-end is crafted using semantically marked up content, styled with modern CSS, and enhanced with JavaScript for interactivity. My approach ensures that, whenever possible, the content remains accessible and consumable even if the JavaScript doesn't run.
Uses the latest in the front-end field. Shiny new CSS, with appropriate fallbacks for older browsers as per the previous two points.
Vanilla. I don't use any JavaScript frameworks in my work.
Optimized for performance. The product experience needs to feel lightweight and fast
The text was updated successfully, but these errors were encountered:
Add some info covering what aspects of web building I focus on
Great example from https://www.sarasoueidan.com/hire/
The text was updated successfully, but these errors were encountered: