---
title: "No Twig or HTML properties"
date: "2022-06-20T11:42:15+00:00"
summary: "Discover how Site Studio renders custom components without Twig or HTML properties. Learn about default templates, data attributes, and dropzone handling for efficient component development."
image:
type: "page"
url: "/drupal-starter-kits/add-ons/site-studio/no-twig-or-html-properties"
id: "ab574043-9611-4501-a5fd-a80cf0f622da"
---

By default if a custom component doesn’t use a [template](/drupal-starter-kits/add-ons/site-studio/custom-component-definition-reference#custom-component-template "Custom component definition reference") or [html](/drupal-starter-kits/add-ons/site-studio/custom-component-definition-reference#custom-component-html "Custom component definition reference") property, it will use the default twig that Site Studio provides. This default template will render a \`<div>\` that has a class of the id of the custom component. All field values will be accessible via a data attribute on that div \`data-ssa-custom-component\` and stored as a JSON object.

If the custom component contains any dropzone, each one of them will be rendered in a \`<template>\` inside the div and can be retrieved by a data attribute \`data-dropzone-id\` where the value will be \`dropzone-\[uuid-of-the-dropzone\]\`. You can find the uuid of a dropzone in the \`canvas\` object of the custom component form Json.