Scaling content creation with a no-code landing page builder
In early 2018, I proposed a solution to a growing bottleneck at Netology: building a landing page for each new course required 2–3 weeks of developer and designer time. With dozens of new courses launching regularly, this approach clearly wasn’t scalable.
I teamed up with an engineer Pavel Komiagin and pitched the idea of an internal landing page builder — a tool that would allow marketing and content teams to create new pages on their own, without developers and with minimal input from designers. The proposal was approved, and I took on both product and design roles throughout the project.
I teamed up with an engineer Pavel Komiagin and pitched the idea of an internal landing page builder — a tool that would allow marketing and content teams to create new pages on their own, without developers and with minimal input from designers. The proposal was approved, and I took on both product and design roles throughout the project.
The builder became a critical internal tool. 7 years later, Netology still creates dozens of landing pages per week using it — with no developers and minimal involvement from the design team.
✦ Each block could be rearranged, enabled, or disabled depending on the page’s needs.
✦ The system was built to be foolproof — even non-designers couldn’t easily break the layout, thanks to built-in rules that ensured visual consistency regardless of how much text was entered or which fields were left empty.
✦ We also added the ability to apply design or structural changes across all landing pages at once, making future updates much easier to roll out.
✦ The system was built to be foolproof — even non-designers couldn’t easily break the layout, thanks to built-in rules that ensured visual consistency regardless of how much text was entered or which fields were left empty.
✦ We also added the ability to apply design or structural changes across all landing pages at once, making future updates much easier to roll out.
As a designer, I created a system of modular, reusable blocks that looked good in any combination and on any screen size.
✦ The importance of listening to users. I learned how to collect, prioritize, and act on user needs, as well as how to communicate clearly with internal teams who relied on this tool daily.
✦ How frontend works — and how to design for it. I gained a much deeper understanding of how interfaces are built and how to structure design components so they’re easy to implement, maintain, and scale.
✦ How to think like a product manager. This project showed me what it takes to move a product idea from concept to execution — and how essential clear documentation, collaboration, and iteration are at every step.
✦ How frontend works — and how to design for it. I gained a much deeper understanding of how interfaces are built and how to structure design components so they’re easy to implement, maintain, and scale.
✦ How to think like a product manager. This project showed me what it takes to move a product idea from concept to execution — and how essential clear documentation, collaboration, and iteration are at every step.
What I learned
My roles
proDUCT manager, PRODUCT designer
proDUCT manager, PRODUCT designer
