Shopify tooling should have accountable authors. This page is the public roster for HTML to Liquid Converter — Dhruv Goyani and Nishad Kikani, the Shopify developers who write our guides, maintain the converter, and ship client sections at K2 Devworks. We publish our names on blog posts, knowledge guides, and company pages because developer tooling deserves real profiles — not anonymous marketing copy.
Dhruv Goyani
Role: Shopify Developer
Experience: 3 years web design, 3 years Shopify theme development (3 years web design + 3 years Shopify development experience)
Dhruv combines web design and Shopify theme development — converting Figma and static HTML into merchant-editable OS 2.0 sections for client stores. He focuses on schema structure, section presets, and clean handoffs between design and Liquid.
Core skills
- HTML to Liquid conversion
- Online Store 2.0 sections
- Section schema & presets
- Figma-to-Shopify workflows
- Theme editor UX for merchants
Selected highlights
- Shipped custom sections for fashion, beauty, and DTC brands
- Built repeatable HTML-to-section pipelines for agency clients
- Co-architected HTML to Liquid Converter schema detection
Follow Dhruv on LinkedIn for Shopify section workflows, Figma handoffs, and theme editor UX notes.
Dhruv leads the design-to-section pipeline: taking Figma and static HTML, deciding which nodes become settings versus blocks, and ensuring presets give merchants a sensible first insert in the theme editor. He co-architected schema detection in the converter workspace and writes guides like hero conversion and HTML to Shopify section workflows.
Before Shopify full-time, Dhruv shipped marketing sites and component libraries — experience that shows up in scoped CSS conventions and editor-friendly setting labels. On client projects he is the developer agencies call when handoff HTML needs to become OS 2.0 sections without breaking merchant workflows.
Nishad Kikani
Role: Lead Shopify Developer
Experience: 2 years web design, 6 years Shopify theme development (2 years web design + 6 years Shopify development experience)
Nishad has six years of Shopify theme engineering — Dawn migrations, JSON templates, performance tuning, and complex block-based sections. He leads client delivery, code review, and the production standards behind every export from HTML to Liquid Converter.
Core skills
- Shopify theme architecture
- Liquid performance & debugging
- Dynamic blocks & JSON templates
- Dawn & premium theme customization
- Client store migrations
Selected highlights
- Migrated legacy Liquid themes to OS 2.0 for multiple merchants
- Optimized theme performance on high-traffic Shopify Plus stores
- Defined validation rules used in HTML to Liquid Converter
Follow Nishad on LinkedIn for Dawn migrations, Liquid performance, and JSON template architecture posts.
Nishad owns theme architecture and production standards: Dawn and premium theme customization, JSON template hygiene, Liquid performance, and migration paths from legacy section files. He defined many validation rules in the converter after debugging real merchant issues — empty image fallbacks, block max limits, nested loop warnings.
With six years on Shopify, Nishad has seen OS 2.0 adoption from early JSON templates through today's block-heavy themes. He leads code review on client repos and writes deeper technical posts on Liquid patterns, performance, and dynamic blocks.
Connect with us on LinkedIn
We publish Shopify development notes, section workflow tips, and platform observations on LinkedIn — not as growth spam, but as practitioner updates. Follow Dhruv Goyani and Nishad Kikani to see what we are shipping on client themes and how that feeds back into the converter.
How we work together
Dhruv optimizes the front of the pipeline — HTML structure, schema ergonomics, merchant editor UX. Nishad optimizes the back — theme integration, performance, migrations, and release quality. Overlap is intentional: both of us review exports before they ship in the public converter, and both of us still touch client themes weekly so the product does not drift from reality.
- Combined 9 years Shopify theme delivery (3 + 6).
- Combined 5 years web design / front-end layout work.
- Agency and DTC client projects delivered; Custom OS 2.0 sections from client Shopify work.
- Zero fabricated testimonials — see educational client scenarios instead.
We founded K2 Devworks as a builder studio, not a growth-at-all-costs startup. That shows up in product decisions: free core conversion, public checklists, and transparent company story pages.
Where our bylines appear
Team bylines appear on knowledge hub articles (section tutorial, how sections work, Liquid for beginners), selected blog posts, and company story pages. The development experience page summarizes project types; this page names the people accountable for that experience.
Contact: k2devworks@gmail.com for agency partnerships, section delivery questions, or corrections to published technical content.
Day-to-day responsibilities
On a typical week, Dhruv might convert three hero variants from agency Figma files, tune block detection for a logo strip, and write a guide section explaining preset defaults. Nishad might review a Dawn migration PR, profile Liquid loops on a collection template, and add a validation rule when a client theme editor crashes on empty image_picker output. Both of us still open Shopify admin and theme code — we do not manage the product from slides alone.
Dhruv — design handoff to section file
Dhruv's workflow starts when HTML lands in a brief. He tags editable nodes, decides Flat versus Block, runs the converter, then edits schema labels for merchant clarity. He checks theme editor screenshots with non-technical stakeholders before merge. His web design background shows up when spacing tokens from prototypes need mapping to theme CSS variables instead of hardcoded pixels.
Nishad — theme integration and release quality
Nishad's workflow starts at the theme repo. He verifies JSON template references, runs theme check patterns manually where needed, and tests sections beside app blocks on product and cart templates. He owns the checklist junior developers follow: presets present, max_blocks set, no global CSS leaks, image_url filters guarded for blank picks. When something fails in production, he traces whether the bug is schema, Liquid logic, or merchant data — then feeds fixes back into converter validation.
Tools and themes we work in
- Shopify CLI, GitHub, and theme editor code view for section deployment.
- Dawn, Prestige, Broadcast, and Impulse — see theme-specific guides.
- Figma and static HTML exports as converter inputs — see workspace.
- Shopify admin for merchant-side QA and editor UX review.
- Schema Generator for quick JSON experiments before full HTML conversion.
How we think about teaching
We write content the way we wish client handoff docs existed when we were junior developers: named authors, concrete steps, links to primary Shopify docs where relevant, and honest limits (always test in your theme). That is why blog posts and knowledge guides carry team bylines and why we publish pages like why we built the converter instead of anonymous SEO articles.
If you are evaluating whether to trust exports from htmltoliquidconverter.com, start here — real names, real years, real roles — then validate output yourself in a staging theme. Trust is earned by reproducible quality, not marketing adjectives.
Background before Shopify full-time
Dhruv Goyani's three years of web design work included marketing sites, landing page systems, and component handoffs where designers expected pixel fidelity. That background explains his obsession with scoped CSS and merchant-readable setting labels — he has seen what happens when non-developers face cryptic schema IDs. Nishad Kikani's two years of general web work before Shopify focused on front-end templates and CMS-like editable regions, foreshadowing Online Store 2.0's section model before the platform fully embraced JSON templates.
Neither of us came from enterprise software sales or growth marketing. We are implementers who learned Shopify by shipping on deadlines — Black Friday launches, wholesale catalog refreshes, migration weekends. That implementation history is why our content emphasizes checklists, validation, and theme editor screenshots instead of abstract platform praise.
Commitments we make publicly
- Named authors on technical content — no ghostwritten SEO farms.
- Educational case studies instead of invented customer quotes.
- Free core conversion so juniors and freelancers are not paywalled from learning OS 2.0 structure.
- Honest limits: always review exports in your target theme before production.
- Corrections welcome via k2devworks@gmail.com when guides drift from Shopify platform changes.
Questions we get from agencies
Agencies often ask whether juniors can rely on converter output without senior rewrite. Our answer: output accelerates structure — schema, blocks, scoped CSS — but seniors still review theme fit, accessibility, and performance. Another frequent question is whether we endorse white-labeling the tool; you may use exports in client work, but please do not rebrand the hosted converter as your own product.
Agencies also ask how we stay current with Shopify platform changes. We follow the official Shopify developer changelog, test on client staging themes, and update blog posts when filters or schema conventions shift. If you spot drift between a guide and current Shopify docs, email us — corrections help every reader, not just one agency. We typically respond within a few business days.