PulseDev for Jekyll.Click it, fix the layout.
Click any element in your running Jekyll site and say what’s wrong. Your agent opens the layout or include behind it, and a rebuild shows the edit before you approve the diff.
One minute of setup.
None of it ships.
Paste one tag into _layouts/default.html and start your dev server. Keep the PulseDev app open while you work; it runs the server the widget talks to.
- Add
Paste the script tag.
Put it in _layouts/default.html, the layout every page shares. Jekyll builds for production set JEKYLL_ENV, so the tag drops out.
_layouts/default.html {% if jekyll.environment == "development" %} <script src="http://localhost:3899/widget.js" data-token="YOUR_TOKEN"></script> {% endif %} - Run
Start Jekyll as usual.
The widget shows up in the corner of every page. Click it, then click the element you want changed.
terminal $bundle exec jekyll serve➜Local:http://127.0.0.1:4000/➜PulseDev:widget connected
It fits how
Jekyll works.
A click carries more than a selector. The page, the element and its selector go to your agent, which follows them to the right file.
Include Inspector
View which includes are used on the current page and their parameters.
Front Matter Viewer
Inspect YAML front matter and site data used to render the current page.
Collection Debugging
Browse Jekyll collections and see how data flows into your templates.
Liquid Filter Tracing
See which Liquid filters transform data and their input/output values.
Jekyll questions.
- Does it work with GitHub Pages?
- Yes! PulseDev works with your local Jekyll server. Debug locally, deploy to GitHub Pages.
- Can I debug Liquid templates?
- Absolutely. PulseDev traces Liquid execution and shows which template rendered each element.
- Does it support custom plugins?
- Yes, PulseDev works alongside any Jekyll plugin without conflicts.
- Is there a performance overhead?
- PulseDev only runs in development. It does not affect your production builds.
Your Jekyll site is running.Go point at the bug.
Windows coming soon. Free to start.