# Eleventy / Build Awesome review: template-based sites and package-name continuity Canonical: https://globaltechreview.org/tech-reviews/eleventy Author: Global Tech Review Published: 2026-10-22 Updated: 2026-10-22 Sources checked: 2026-10-22 Evidence: documentation-only ## AI Summary and verdict > **AI Summary:** Eleventy / Build Awesome documents template-based sites and package-name continuity. The current README name and package examples differ from older Eleventy tutorials. This documentation-only review supports a scoped evaluation, not a product test; sources checked 2026-10-22. [eleventy-docs] ### Verdict For Eleventy / Build Awesome, evaluate the documented template-based sites and package-name continuity against the target need: a content site with existing templates and a limited amount of browser interaction. The current README name and package examples differ from older Eleventy tutorials. No successful product trial is implied. [eleventy-docs] ## Product facts Product: Eleventy / Build Awesome Vendor / project: 11ty/eleventy project contributors Category: coding Version / scope: Documentation snapshot 2026-10-22; source revision 3ed8eb30fb9a, not an installed or tested release Website: https://www.11ty.dev Evidence basis: documentation-only Sources checked: 2026-10-22 Verification scope and unknowns: see Evidence and methodology. - The pinned Eleventy repository README is headed Build Awesome (Eleventy). (vendor-documented) [eleventy-docs] - The project describes transforming a directory of templates into HTML. (vendor-documented) [eleventy-docs] ## Capabilities and workflows ### Documented workflow - The README lists HTML, Markdown, JavaScript, Liquid and Nunjucks among supported authoring types. (vendor-documented) [eleventy-docs] - The installation example lists @awesome.me/buildawesome and also labels @11ty/eleventy as backwards compatible. (vendor-documented) [eleventy-docs] ### Proposed acceptance trial - For Eleventy / Build Awesome: Proposed trial, not performed: Copy a small existing template set, including one Markdown page, a layout and a navigation include. Record the exact package and version used. Rebuild using the current installation guidance in an isolated branch, compare generated URLs and HTML, and check every required plugin. Retain a working previous lockfile and output artifact until the comparison is complete. (editorial-opinion) [eleventy-docs] ## Strengths, limitations, and trade-offs ### Strengths - The pinned Eleventy repository README is headed Build Awesome (Eleventy). (vendor-documented) [eleventy-docs] - The README lists HTML, Markdown, JavaScript, Liquid and Nunjucks among supported authoring types. (vendor-documented) [eleventy-docs] ### Limitations and trade-offs - Eleventy / Build Awesome: The current README name and package examples differ from older Eleventy tutorials. (editorial-opinion) [eleventy-docs] ### Decision boundary - For Eleventy / Build Awesome: The current README name and package examples differ from older Eleventy tutorials. Backwards-compatible wording is not proof that every plugin, configuration file or custom template will behave identically. Keep the documented naming change visible in any migration recommendation. (editorial-opinion) [eleventy-docs] ## Best for, not for, and alternatives ### Best for - Eleventy / Build Awesome: An existing Eleventy maintainer can use the current README to investigate package naming while preserving template behavior. A new project with mixed template formats can evaluate whether those formats produce the required HTML without treating a familiar package name as a complete compatibility guarantee. [eleventy-docs] ### Not for / requirements not established - Eleventy / Build Awesome: do not rely on this review alone when the following requirement needs a demonstrated result. Keep the documented naming change visible in any migration recommendation. [eleventy-docs] ### Alternatives - For Eleventy / Build Awesome, evaluate another workflow if it cannot satisfy the actual need: a content site with existing templates and a limited amount of browser interaction. Define required outputs, operator responsibilities and the content or task relationships that must survive migration. Use the same sample and acceptance checklist for each candidate. More documentation is not by itself better delivered behavior, and this review establishes no named alternative as superior. (editorial-opinion) [eleventy-docs] ## Evidence and methodology Official project documentation was retrieved on 2026-10-22 (Asia/Saigon), retained with integrity hashes and matched to literal excerpts under Editorial Standard 1.3, revision r1. Product assertions are attributed documentation; suitability and proposed trials are editorial reasoning from those premises. Repository commits identify source scope, not an installed release. No product account or hands-on test was used; site-build checks verify publishing output only. ### Evidence gaps and scope - Eleventy / Build Awesome: The current README name and package examples differ from older Eleventy tutorials. - Current commercial prices, service quotas, paid support and total operating cost were not verified. Source availability does not establish a free hosted service or zero operating expense. - No installation, account access, hands-on task, benchmark, security review or recovery experiment was performed. Proposed trials are recommendations, not observed outcomes. - Sources are project-controlled documentation at recorded revisions. A source-matched description is not independent behavior verification; absent evidence is not proof that a capability is absent. [Evaluation framework](/methodology) ### Disclosure Sponsored: false. Affiliate links: false. On 2026-10-22, the publisher confirmed no sponsorship or commercial relationships for this batch; direct official links carry no affiliate tracking. Codex assisted research, writing and automated editorial review; no product access, product testing or independent human review is claimed. ### Sources - [eleventy-docs] 11ty/eleventy — official documentation snapshot: https://raw.githubusercontent.com/11ty/eleventy/3ed8eb30fb9a596abed6feee6822cdd822fae1bd/README.md (accessed 2026-10-22) ## FAQ and further reading ### Should an Eleventy tutorial assume the README still uses only the old package name? - For Eleventy / Build Awesome: No. The checked README uses Build Awesome (Eleventy) and includes both package examples. Verify the intended package and compatibility against the actual project rather than silently mixing instructions. (editorial-opinion) [eleventy-docs] ### What evidence would justify a stronger recommendation? - For Eleventy / Build Awesome, retain the exact product version, environment, input sample and observed outputs from the proposed trial. Resolve the stated boundary before generalizing to production: The current README name and package examples differ from older Eleventy tutorials. Documentation and successful website rendering do not substitute for those product artifacts. (editorial-opinion) [eleventy-docs] ### Further reading - [Official Eleventy / Build Awesome product or project](https://www.11ty.dev) - [All Tech Reviews](/tech-reviews) - [Eleventy vs Astro: template continuity and server-first content sites](/tech-comparisons/eleventy-vs-astro) [eleventy-docs]: https://raw.githubusercontent.com/11ty/eleventy/3ed8eb30fb9a596abed6feee6822cdd822fae1bd/README.md