This page is for partners who want a practical build path: design the marketing site in Pinegrow, publish normal HTML, and drop in Nilo widgets wherever the business needs a customer-facing action.
Pinegrow handles the page structure and design. Nilo widgets add the actions that help the business collect, guide, or move customer requests forward.
The simplest setup is to treat Nilo as an enhancement layer on top of the site you already build in Pinegrow.
Create the layout, sections, forms, visuals, and responsive behavior the same way you normally would.
Decide where the business needs an action such as contact, qualification, booking, request intake, or follow-up.
Add the widget bundle in the page head or before the closing body tag so the custom elements are available on the page.
Insert the widget tag where you want the action to appear. Pinegrow still treats the page like normal HTML.
Pass the widget settings through HTML attributes such as environment, business ID, widget ID, locale, or theme values.
Export or publish the site through your normal workflow. The widget behavior comes from the script plus the custom element markup.
The practical model is simple: include the script once, then place the widget tags where they belong. That is what makes this fit well with Pinegrow.
The bundle defines the custom elements in the browser.
You place a widget tag in the part of the layout where the action should appear.
Each widget instance can read configuration directly from the tag attributes.
Your typography, layout, sections, hosting, and Pinegrow workflow do not need to change.
Replace the placeholder values below with the script URL and widget attributes your Nilo setup uses.
Put this in the page head or before the closing body tag. Do not duplicate it for every widget instance.
<script
type="module"
src="https://YOUR-WIDGET-HOST/nilo-widgets.js"></script>Use a normal HTML block in Pinegrow where the customer action should appear.
<nilo-widget
business-id="YOUR_BUSINESS_ID"
widget-id="YOUR_WIDGET_ID"
locale="en-US"
theme="light">
</nilo-widget>The same bundle can support multiple customer actions on the same page.
<script
type="module"
src="https://YOUR-WIDGET-HOST/nilo-widgets.js"></script>
<nilo-widget
business-id="YOUR_BUSINESS_ID"
widget-id="contact-intake"
locale="en-US">
</nilo-widget>
<nilo-widget
business-id="YOUR_BUSINESS_ID"
widget-id="quote-request"
locale="en-US">
</nilo-widget>You do not need to rebuild your workflow around the widgets. You just need a reliable place to insert the script and the custom element markup.
If Pinegrow is managing a shared head or footer, place the script there so every page can use the components without repeating work.
Drop the web component into a custom HTML block, code block, or the page source where you want the action to render.
Handle headings, spacing, background, and supporting copy in Pinegrow. Let the widget focus on the action itself.
Because web components are browser behavior, confirm the rendered result in the browser preview rather than relying only on static design view.
If you may move the widget later, keep the surrounding Pinegrow section self-contained so the whole block can be reused on another page.
Write down the few attributes your client setup actually needs so future edits are simple for you or another partner.
Place a widget below the hero or service section when the business needs more inquiries.
Use a widget after pricing or service details to gather the right customer context before follow-up.
Put a widget on service pages where the owner currently loses detail in email or phone back-and-forth.
The widget is not the website. It is the action layer inside the website. That distinction helps partners keep the page simple and place widgets only where they add real business value.
This keeps the offer easy to explain: the site is yours, the design is yours, and Nilo adds customer-facing actions without forcing a rebuild.
Design and content can move on your normal Pinegrow timeline.
You can add the next widget later without changing the whole site architecture.
The project still looks like a normal website with a small integration layer.
Tell us what kind of site you build, what customer action you want the widget to handle, and what kind of handoff you need for the client.