Your AI Agents can now act on comments added in BugSmash with our MCP. See How it works.
Collect visual feedback on a website built with Eleventy. Create a BugSmash Website project with a public URL or a site protected by Basic Auth, then share its review link for contextual comments. Other application logins, SSO, CAPTCHA, VPN and network restrictions may require the Feedback Widget or HTML workflow. This is not a native Eleventy integration: BugSmash reviews the resulting browser page and does not connect to Eleventy itself. Use the hosted static website URL. If you only have the static build files, use BugSmash's HTML review workflow instead of a localhost or filesystem URL. https://your-site.com Platform clarification: this is a generic BugSmash Website project workflow, not a native Eleventy integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your published Eleventy site
Paste the browser-accessible URL for your Eleventy deployment, send one review link, and collect comments on the pages your visitors will actually open. Every note keeps its page, browser, device and screenshot context.
Loved by1,250+Agenciesand companies in 100+ countries
Eleventy creates the static build. Review happens on its deployed output.
A standard npx @11ty/eleventy run is a production-ready build by default. Eleventy writes the finished templates to _site unless the output directory is changed, and static hosts can serve that directory.
Four build and deployment details still matter:
01
--serve starts a local development server.
Eleventy documents --serve as a hot-reloading local development server. Use a hosted URL for a durable external review.
02
The output directory is configurable.
Finished templates go to _site by default, but dir.output or --output can change that destination. Make sure the host deploys the directory used by the reviewed build.
03
Development and production are not separate internal modes.
Eleventy says a standard build is production-ready by default and does not internally change build behavior between development and production. Project-specific environment logic can still change the result.
04
A project subpath may need pathPrefix.
Eleventy's GitHub Pages guidance uses --pathprefix for a repository project site and removes it for a custom domain. Review links and assets on the actual published path.
BugSmash adds the review workflow around the deployment:
review the hosted pages in a browser, keep comments attached to the rendered output, and preserve approval outside the source repository and deployment provider.
How it works
Three steps to a reviewed Eleventy site
11
Build and deploy the intended output
Run the project build, confirm the configured output directory, and publish it to a static host or through the project's provider workflow.
22
Send one review link
Paste the deployed URL into BugSmash and share the generated link. Reviewers comment on the hosted pages without repository or deployment-dashboard access.
33
Resolve feedback page by page
Each item carries the page, selected element, screenshot, browser and device. Assign it, update its status, or send it into the team's delivery tools.
Review the Eleventy output visitors will actually browse
Comment on generated pages
Attach feedback to the rendered page instead of translating it into a template, data file or layout name.
Check responsive layouts
Review desktop, tablet and mobile states from one link and keep the viewport with each comment.
Capture browser context
Browser, device, screenshot and page URL arrive with every report.
Validate the configured output
Review the directory and build command actually deployed by the project's hosting configuration.
Check project-site paths
Exercise navigation and assets on the real published path, including a configured pathPrefix when the host requires one.
Keep release approval
Preserve the review record independently of later builds, template changes or hosting updates.
Will it work on my Eleventy site?
BugSmash reviews a browser-accessible Eleventy deployment. The build configuration, output directory, host and source-site access controls determine what reviewers can open.
Your URL
Review by URL
What to do
Public Eleventy site on a custom domain
Works
Paste the deployed URL and review the published static site.
Public Eleventy site on a static host
Works
Use the visitor-facing URL after the configured output directory is deployed.
GitHub Pages project site with pathPrefix
Works
Use the complete project-site URL and verify navigation and assets at that path.
Preview protected by supported Basic Auth
Works
Use the browser-accessible Basic Auth URL; BugSmash lists websites protected by Basic Auth as supported.
Local Eleventy --serve address
Not directly
Deploy the configured output directory to a browser-accessible host before creating the review.
Site behind an application login or SSO
Use another workflow
Install the BugSmash Feedback Widget or share a static export. A pasted URL does not bypass application login or SSO.
Using the BugSmash Feedback Widget on an Eleventy site
Add the BugSmash script through a shared Eleventy layout or template when the review must stay inside an authenticated or otherwise stateful browser flow. Confirm it is present in the configured output deployed for review.
The feedback workflow for teams using Eleventy
From blogs and documentation to content-driven marketing sites, keep content, design, engineering and QA aligned on the same generated release.
Ship faster togetherThe all-in-one workspace for product teams.
Get started free
MayaMake this hero image full-bleed
Live WebsiteURL
product-launch.mp4
0:42 / 3:15
LeoTrim the intro to 0:03
VideoMP4
sneaker.glb
AvaSmooth these edges a bit
3D ModelGLB · GLTF
Quarterly Review
Q3 Performance
Revenue up 24%1.2k new usersNPS score 62Churn down 3%
BugSmash3 / 18
SamUpdate the Q3 numbers
Slide DeckPPT
Your summer sale starts now 🌞
A
Acme Store
to you
9:24 AM
Up to 40% off
Summer essentials, restocked
Shop the sale
NoahStronger CTA copy here
EmailHTML
9:41
Good morning
Dashboard
Balance
$4,280
ZoeAlign the chart legend
Mobile AppAndroid · iOS
Annual Report2025 in review
This year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.
Fig 1. Coastal expansion, 2025
Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.
Should I share the Eleventy --serve URL with a client?
Eleventy documents --serve as a hot-reloading local development server. For external review, deploy the configured output directory to a browser-accessible host.
Which Eleventy folder should I deploy?
The default output directory is _site. If the project changes dir.output or uses --output, deploy that configured directory instead.
Do I need a separate production mode for Eleventy?
Eleventy says a standard build is production-ready by default and does not internally change behavior between development and production. Your project can still use environment variables for its own build differences.
Can any static host serve an Eleventy build?
Eleventy's deployment guide says it works with any web host that supports static files. Publish the configured output directory and use the resulting browser URL for review.
Can a hosting provider build Eleventy from my repository?
Yes. Eleventy documents providers that trigger the build command after a source-control commit and deploy the build output directory.
When does an Eleventy site need pathPrefix?
Eleventy's GitHub Pages instructions set --pathprefix to the repository name for a project site. They say to remove that parameter when the Pages deployment uses a custom domain.
Can I review an Eleventy GitHub Pages project site?
Yes. Use the complete published project URL and verify that the build's pathPrefix makes links and assets resolve from that subpath.
Do reviewers need access to the Eleventy repository?
No. They review the published browser output rather than the templates, source files or deployment dashboard.
Ship Eleventy sites without chasing feedback
Paste an accessible Eleventy deployment URL and send the first review link in under a minute.
BugSmash adds the review workflow around the deployment:
Jira
ClickUp
Monday
Asana
Trello
Slack
Linear
Todoist
Notion
Airtable
Zapier
Make
n8n
Webhooks
MayaMake this hero image full-bleed
product-launch.mp4
LeoTrim the intro to 0:03
AvaSmooth these edges a bit
SamUpdate the Q3 numbers
Up to 40% off
NoahStronger CTA copy here
ZoeAlign the chart legend
EllaTighten this paragraph
TheoBoost the warm tones
MiaCut the dead air at 1:12