Eleventy layouts, edited whatever the template language

By its config file, and the list is exact: .eleventy.js, eleventy.config.js, eleventy.config.cjs or eleventy.config.mjs at the project root. A TypeScript config is not in that list, so a project using one is not detected as Eleventy today — worth knowing rather than discovering. Everything downstream, including which lane the project gets and where a page title is written, follows from that detection.

No, and that is the point of this lane on Eleventy specifically. PortBay locates the element you clicked by matching its markup in your source rather than by parsing a template grammar, so a Nunjucks layout, a Liquid include and a plain HTML page in the same project all behave identically. An editor built around one grammar would work on part of a mixed site and silently skip the rest.

Eleventy template expressions and tags are left alone. A value printed by an expression is not present in the file as words, so rewriting it would mean turning your template logic into a literal and changing every page that renders through it. PortBay refuses those edits and, where the value has a real home, points at it — a page title belongs in that page's front matter, so that is where the Page settings panel writes it.

Yes. What matters is which file contains the markup, not what role Eleventy assigns that file. If the element you clicked came from an include, the include is what changes; if it came from the base layout, the layout changes; if it was written inline in the page, the page changes. Anything that resolves to more than one place is put to you before it writes, rather than being applied to the first match.

No. Structural edits are refused on this lane rather than guessed at, because without a source coordinate there is no way to be certain which occurrence of a piece of markup you meant, and a wrong structural change to a shared layout breaks every page using it. Text, class and attribute edits, plus page settings, all write — that is proven against a real Eleventy fixture in PortBay's cross-stack test, which edits _includes/base.njk and reads the changed bytes back off disk.

Into that page's own portbay_head_code and portbay_body_code front-matter keys. PortBay installs one small include in the project so the base template prints them into the real head and before the closing body tag. It is per-page rather than site-wide, and it lives in your content file, so it is part of the same commit as the rest of your change.

No. It is a PortBay Pro feature, still in early access behind an opt-in toggle in Settings, and it is not compiled into the open-source build. It refuses to run while the site is shared over a public tunnel, and the edit bar works only on local .test hosts. Serving Eleventy on a real .test domain with trusted HTTPS is in the free app.