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 Jekyll. 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 Jekyll integration: BugSmash reviews the resulting browser page and does not connect to Jekyll 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 Jekyll integration. Public URLs and supported Basic Auth sites can use the Website project workflow.
Get client feedback on your published Jekyll site
Paste the browser-accessible URL for your Jekyll 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
Jekyll builds static output. The review target is the deployed site.
Jekyll writes a build to _site by default. Its deployment tutorial uses JEKYLL_ENV=production bundle exec jekyll build for a production build, whose static output can then be copied to a web host or published through an automated deployment workflow.
Four build and URL details still matter:
01
jekyll serve is for local development.
It rebuilds the site as source files change and serves it locally. Jekyll explicitly says the _site output produced by jekyll serve is not suited for deployment.
02
The generated site is written to _site by default.
Jekyll's documented production command is JEKYLL_ENV=production bundle exec jekyll build. Publish the generated directory to a static host or through an automated deployment process.
03
url and baseurl affect generated links.
Jekyll's url setting represents the production domain, while baseurl represents the path between that domain and the site root. Review on the same published location those settings describe.
04
GitHub Pages is a publishing choice, not a Jekyll requirement.
GitHub Pages can publish from a branch or a GitHub Actions workflow. Jekyll's static _site output can also be transferred to other hosting providers.
BugSmash adds the review workflow around the deployed result:
review the hosted pages in a browser, keep comments attached to the rendered output, and preserve approval outside the source repository and publishing service.
How it works
Three steps to a reviewed Jekyll site
11
Create and deploy the production build
Run JEKYLL_ENV=production bundle exec jekyll build with the production URL and base path intended for release, then publish the generated _site directory to the chosen host.
22
Send one review link
Paste the deployed URL into BugSmash and share the generated link. Reviewers comment on the hosted site without repository or publishing-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 Jekyll site visitors will actually browse
Comment on generated pages
Attach feedback to the rendered page instead of translating it into a Markdown file, layout or Liquid template.
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 production paths
Review links and assets on the deployed domain and base path rather than relying on localhost behavior.
Cover the complete static output
Move through posts, pages and collections included in the production build and keep feedback tied to each URL.
Keep release approval
Preserve the review record independently of later builds, source changes or hosting updates.
Will it work on my Jekyll site?
BugSmash reviews a browser-accessible Jekyll deployment. The build configuration, publishing source, host and source-site access controls determine what reviewers can open.
Your URL
Review by URL
What to do
Public Jekyll site on a custom domain
Works
Paste the deployed URL and review the published static site.
Public Jekyll site on GitHub Pages
Works
Use the published Pages URL after the configured branch or Actions deployment completes.
Public preview supplied by a hosting provider
Works
Use the preview URL after confirming it opens without repository or dashboard access.
Preview protected by supported Basic Auth
Works
Use the browser-accessible Basic Auth URL; BugSmash lists websites protected by Basic Auth as supported.
Local jekyll serve address
Not directly
Create the production build and deploy the generated _site directory to a browser-accessible host.
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 a Jekyll site
Add the BugSmash script through a Jekyll layout or include when the review must stay inside an authenticated or otherwise stateful browser flow. Confirm the script appears in the production build deployed for review.
The feedback workflow for teams using Jekyll
From blogs and documentation to project sites, keep content, design, engineering and QA aligned on the same production build.
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.
Jekyll documents jekyll serve as a local development workflow and states that the _site output it creates is not suited for deployment. Create a production build and deploy it to a browser-accessible host for external review.
Which Jekyll folder should I deploy?
Jekyll's production tutorial uses JEKYLL_ENV=production bundle exec jekyll build, which writes the generated site to _site by default. Its manual deployment guide says to transfer that directory's contents to the web root on the host.
What is the difference between url and baseurl?
The url setting is the canonical production domain without a trailing slash. The baseurl setting is the path between that domain and the site's landing page; Jekyll combines them when generating absolute URLs.
Does a Jekyll site have to use GitHub Pages?
No. Jekyll documents manual, automated and third-party deployment methods. GitHub Pages is one publishing option for the static site.
Can I review a Jekyll site on GitHub Pages?
Yes, after the site is published and its visitor-facing URL is accessible. GitHub Pages can publish from a configured branch and folder or through a GitHub Actions workflow.
Why do links work locally but fail on the published site?
Check the production url and baseurl values and rebuild with the intended destination. jekyll serve sets url to its local host, which differs from a production domain or project subpath.
Can I review a Jekyll site hosted below a subdirectory?
Yes. Use the full deployed path and set baseurl to the path between the domain root and the site's landing page.
Do reviewers need access to the Jekyll repository?
No. They review the published browser output rather than the source files, build environment or hosting dashboard.
Ship Jekyll sites without chasing feedback
Paste an accessible Jekyll deployment URL and send the first review link in under a minute.
BugSmash adds the review workflow around the deployed result:
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