Weave Code
Framework Laravel Package
hyde/framework
HydePHP is a Laravel-based static site generator that turns Markdown and Blade templates into fast, secure static HTML. Enjoy familiar Laravel tooling, zero-config defaults, and a simple, elegant publishing workflow.
HydePHP Framework is the core package behind HydePHP, a Laravel-powered static site generator for building fast, elegant websites with familiar PHP tools. It compiles Markdown and Blade content into pre-rendered HTML, combining Laravel’s developer experience with the simplicity of static hosting.
- Laravel foundation built on familiar conventions and components
- Markdown and Blade authoring with a clean, flexible content pipeline
- Static HTML output ready for any CDN or simple host
- Built-in blog and documentation support with sensible defaults
- Zero-config setup that stays easy to extend and customize
Frequently asked questions about Framework
- What is HydePHP and what is it best used for?
- HydePHP is a Laravel-powered static site generator that compiles Markdown and Blade content into static HTML. It is best suited to content surfaces such as documentation sites, engineering blogs, marketing pages, and internal knowledge bases. It is not a good fit for dynamic server behavior, authentication, or per-request logic.
- How do I install the hyde/framework Composer package?
- Hyde is typically consumed with composer create-project rather than added as a library to an existing app. You need PHP, Composer, and usually Node for the Tailwind/Vite asset pipeline. After scaffolding, run the Hyde build command to generate the static site.
- Can I use HydePHP inside an existing Laravel application?
- No, HydePHP is a framework rather than a library, so there is no meaningful embed-into-an-existing-Laravel-app story. Integration realistically means a separate repository and a separate static deploy target. Teams already using Laravel benefit from the familiar Blade and Composer mental model, but should plan a clean-room build rather than a refactor.
- Which Laravel and PHP versions does HydePHP support?
- Hyde tracks Laravel major versions, but you should verify the current support matrix in the repository before committing. Pin the PHP minor, Laravel major, Hyde version, and Node version in CI. Treat the Hyde and Laravel versions as a coupled unit and gate upgrades behind the same review as framework upgrades.
- Do I need Node.js or Tailwind to build a HydePHP site?
- Hyde uses Tailwind styling by default and the asset pipeline generally expects Node in CI. A typical pipeline is PHP plus Composer plus Node, followed by the Hyde build step. Confirm your asset requirements during the spike so CI images and deploy jobs include the right toolchain.
- How does HydePHP handle large sites and incremental builds?
- The evaluation notes that build-time behavior at hundreds versus thousands of pages should be measured before committing. It is not confirmed here whether incremental builds or caching are supported, so assume a full-site build until verified. Run a realistic page-count spike and record build times as part of the pilot exit criteria.
- How do I deploy a HydePHP site?
- Because Hyde outputs static HTML, you can publish the generated site to S3/CloudFront, Cloudflare Pages, Netlify, GitHub Pages, or Nginx on a static host. CI is straightforward: install PHP, Composer, and Node, run the Hyde build, then publish the output directory. Add build verification or link checks in CI before publishing.
- Is HydePHP production-ready and actively maintained?
- The technical evaluation flags weak ecosystem signals: low stars, zero dependents, and likely small-team or single-maintainer governance. That can be acceptable for a low-blast-radius content site, but it is not acceptable for a customer-facing surface with an SLA without further due diligence. Before committing, check maintainer responsiveness, contributor activity, and the upgrade path across one Laravel major.
- How do I migrate content to HydePHP and what is the exit cost?
- Markdown bodies port with modest front-matter remapping from Jekyll, Hugo, Eleventy, or Docusaurus, but templates and layouts must be rewritten in Blade. From an existing Laravel app, expect a clean-room build and budget for template and design-system rework, not just content moves. Because content remains Markdown, the exit cost is mainly the Hyde-specific Blade templates and theme structure.
- How does HydePHP compare to Jigsaw, Astro, or Docusaurus?
- Hyde is strongest for PHP and Laravel organizations that want Blade, Composer, and a Laravel-native mental model for static content. Polyglot teams already running a JavaScript static-site generator such as Astro or Docusaurus may gain little and would add a second toolchain and conventions. Jigsaw is another PHP option, but Hyde differentiates through its Laravel foundation and zero-config defaults; evaluate against your team's stack and ownership model.
Weaver
How can I help you explore Laravel packages today?