About
My name is Alessandro Di Terlizzi and I taught myself to code. CODEDGE came out of that: while I was learning I kept twenty tabs open and rewrote the same notes three times, so I started putting things in one place, written the way I would have wanted to find them.
I work on front-end and everything that orbits it. What I know I learned by building things, breaking them and building them again, and this site is where that work takes a shape someone else can read.
How I work
I always start from something that runs. I'd rather have a component that genuinely works than a flawless explanation of how it would work: the code I publish is code I wrote to use, not to illustrate. When I explain something I explain it once, in the right place, and link to it from then on — which is why the glossaries and the tutorials point at each other instead of repeating each other.
The other half of the method is less fun and matters more: checking. A change that "should work" isn't finished as far as I'm concerned — it has to be opened in the browser, looked at on a large screen and a small one, and checked for what it might have broken that used to be fine. Most of what's here has been through that loop at least twice.
How this site is built
The most honest way to show you how I work is to let you look inside the thing I built. CODEDGE is written by hand, with no framework: HTML, CSS and JavaScript, with Vite putting the pages together. There's no React, no CMS, no bought theme.
The tools run entirely in your browser: when you compress an image no request goes out and the file never leaves your computer. The components are written with ARIA attributes and keyboard focus handling built in, not bolted on afterwards. The site is bilingual, and the alignment between English and Italian is watched by a script that flags it when a page changes on one side only. The code is public on GitHub: if something doesn't add up, you can go and see how it's done.
What you'll find here
Right now there are 418 entries across the three glossaries for HTML, CSS and JavaScript, to check when a property or a method won't come back to you. There are 12 tutorials on Git and GitHub, browser DevTools, accessibility, deployment, technical SEO and the fundamentals of the three languages. There are 4 tools for everyday work and 4 components with their full code, plus a snippet library ready to paste.
Working together
I'm available for collaborations and commissioned work: sites and landing pages, custom components, work on projects that already exist. If you have something in mind, get in touch and we'll talk it through — even just to work out whether I'm the right person for the job.
If you'd rather have something ready-made, the Templates section holds my finished portfolio projects, for sale in my Etsy shop. And if you've spotted a mistake on a page or want to contribute, an issue on GitHub is the quickest way to let me know.