At a glance
During my first internship, I worked on frontend improvements for Taplytics. Most of the work was inside a custom WordPress theme: PHP templates, reusable page sections, CMS editing flows, and designer-led marketing pages.
Built
Reusable PHP templates and CMS-backed sections for marketing pages.
Impact
Marketing could edit and assemble approved page sections without needing a one-off engineering change every time.
Also
Contributed React components inside the product interface.
Context
My first frontend internship
Taplytics was my first software internship. I worked mostly on the marketing site, close to a designer and the marketing team. The goal was practical: make pages easier to build, edit, and publish without losing the design system of the site.
Work
I built reusable page sections
The site used a custom WordPress theme, so the work was not just dragging blocks in a page builder. I built PHP templates and reusable sections that marketing could configure through the CMS.
PHP templates
Built reusable layouts and section variants inside the custom theme.
CMS editing
Made copy, images, and section ordering editable by marketing.
Responsive polish
Worked through spacing, content length, and page behaviour across screens.
Product React
Also helped with React components in the Taplytics product UI.
Lesson
Good frontend work gives other teams leverage
The useful part of this internship was realizing that frontend work does not end at matching a mockup. The better outcome was giving marketing a system they could keep using after the first page shipped.
It also taught me how much detail sits between design and implementation: CMS fields, empty states, image treatment, long copy, responsive behaviour, and reusable variants.
Note
Company note
This internship was at Taplytics before the company became more associated with DevCycle and before DevCycle's later acquisition by Dynatrace.