Building for the content, not just the canvas
One component, different content
werwerew
erwerw
wrwer
Build it for whoever comes after you
What I took away
gizkidesigns@gmail.com
/in/Samuel Nwankwoala
X.com
gizkidesigns
Gizkidesigns
© 2026 All rights reserved.
London Pharmacist Network Website
Company:
London Pharmacist Network
London Pharmacist Network helps foundation trainee pharmacists prepare for the GPhC registration assessment. There's a lot the website needs to communicate before someone decides to enrol: what the programme covers, how it works, who teaches it, what courses are available, why trainees trust it, and what happens after they join. I developed the website in Framer. The job wasn't just getting a finished design onto the web. It was making sure the design continued to work when the viewport changed, the content changed, and the team needed to update it after launch.
Building for the content, not just the canvas
London Pharmacist Network helps foundation trainee pharmacists prepare for the GPhC registration assessment. There's a lot the website needs to communicate before someone decides to enrol: what the programme covers, how it works, who teaches it, what courses are available, why trainees trust it, and what happens after they join. I developed the website in Framer. The job wasn't just getting a finished design onto the web. It was making sure the design continued to work when the viewport changed, the content changed, and the team needed to update it after launch.
One component, different content
werwerew
erwerw
werwerwer
wrwer
Build it for whoever comes after you
It's easy to optimise a website for the person building it. Everything makes sense when you know where every layer lives. The better test is what happens when someone else needs to change it. I organised reusable elements and content structures so common updates wouldn't require reconstructing sections from scratch. That matters for LPN because the website isn't finished when it launches. Courses change, programme information evolves, and new content needs somewhere to go. The website needed to be something the team could continue using, not something they were afraid to touch.
What I took away
Framer development sits much closer to product design than I used to think. You're constantly making design decisions. What happens when this text becomes twice as long? What disappears first when the screen gets smaller? Should this be a component? Should this interaction exist on touch devices? What needs to be editable? What happens when another course is added six months from now? None of those questions are visible in the final screenshot. But the answers determine whether the website still works once it leaves the designer's canvas. That's what I took from building LPN. A good Framer build doesn't just reproduce the design. It protects the design when real life starts changing it.
London Pharmacist Network Website
Company:
London Pharmacist Network
London Pharmacist Network helps foundation trainee pharmacists prepare for the GPhC registration assessment. There's a lot the website needs to communicate before someone decides to enrol: what the programme covers, how it works, who teaches it, what courses are available, why trainees trust it, and what happens after they join. I developed the website in Framer. The job wasn't just getting a finished design onto the web. It was making sure the design continued to work when the viewport changed, the content changed, and the team needed to update it after launch.
Building for the content, not just the canvas
London Pharmacist Network helps foundation trainee pharmacists prepare for the GPhC registration assessment. There's a lot the website needs to communicate before someone decides to enrol: what the programme covers, how it works, who teaches it, what courses are available, why trainees trust it, and what happens after they join. I developed the website in Framer. The job wasn't just getting a finished design onto the web. It was making sure the design continued to work when the viewport changed, the content changed, and the team needed to update it after launch.
One component, different content
werwerew
erwerw
werwerwer
wrwer
Build it for whoever comes after you
It's easy to optimise a website for the person building it. Everything makes sense when you know where every layer lives. The better test is what happens when someone else needs to change it. I organised reusable elements and content structures so common updates wouldn't require reconstructing sections from scratch. That matters for LPN because the website isn't finished when it launches. Courses change, programme information evolves, and new content needs somewhere to go. The website needed to be something the team could continue using, not something they were afraid to touch.
What I took away
Framer development sits much closer to product design than I used to think. You're constantly making design decisions. What happens when this text becomes twice as long? What disappears first when the screen gets smaller? Should this be a component? Should this interaction exist on touch devices? What needs to be editable? What happens when another course is added six months from now? None of those questions are visible in the final screenshot. But the answers determine whether the website still works once it leaves the designer's canvas. That's what I took from building LPN. A good Framer build doesn't just reproduce the design. It protects the design when real life starts changing it.