InMemoryPages

Introduction#

This class is a special page class that is not backed by a file on disk, but rather generated at runtime. While it will probably not be useful for the majority of users, it's a great class to know about if you are a package developer, but feel free to skip this section if you're not interested in this.

When to use#

This class is especially useful for one-off custom pages. But if your usage grows, or if you want to utilize Hyde autodiscovery, you may benefit from creating a custom page class instead, as that will give you full control.

About discovery#

Since the InMemoryPages are not present in the filesystem, they cannot be found by the auto-discovery process. Instead, it's up to the developer to manually register them. If you are working on your own project, you can do this in the boot method of a service provider, such as the AppServiceProvider which is already present in your app/ directory.

If you are developing a package, you may instead want to register the page in your package extension class, within the page collection callback. In either case, if you want your page to be able to be fully processed by Hyde, you need to make sure you register it before the full application is booted so that routes can be generated.

To see how to register the page, see the examples below. But first we must look at how to actually create the page.

Creating the Page#

To create an InMemoryPage, you need to instantiate it with the required parameters.

The constructor supports three content strategies: literal string contents, lazy closure contents, and Blade view rendering.

Pass a string to the $contents parameter when the page contents are already available. Hyde saves the string literally.

$page = new InMemoryPage('robots.txt', contents: "User-agent: *\n");

Pass a closure when the contents should be generated lazily during compilation. The closure is invoked again for each compilation, which makes it useful for pages generated from the current application state.

use Hyde\Framework\Features\XmlGenerators\SitemapGenerator;
use Hyde\Pages\InMemoryPage;

$page = new InMemoryPage(
    'sitemap.xml',
    ['navigation' => ['hidden' => true]],
    fn (): string => app(SitemapGenerator::class)->generate()->getXml(),
);

When contents are provided as a closure, Hyde invokes it when compiling the page and passes the current page as the closure's first argument. Since PHP ignores arguments a closure does not declare, closures that don't need the page context can simply declare no parameters, as seen in the sitemap example above.

$page = new InMemoryPage(
    'example.txt',
    ['title' => 'Example'],
    fn (InMemoryPage $page): string => $page->matter->get('title'),
);

Alternatively, pass a Blade view name or arbitrary .blade.php file to the $view parameter. Hyde renders the view with the supplied front matter during the static site build process.

$page = new InMemoryPage(
    identifier: 'hello',
    matter: ['title' => 'Hello'],
    view: 'pages.hello',
);

An arbitrary Blade file can be rendered without registering its namespace or directory:

$page = new InMemoryPage(
    identifier: 'hello',
    matter: ['title' => 'Hello'],
    view: resource_path('views/pages/hello.blade.php'),
);

The $contents and $view parameters are mutually exclusive. Choose one content source for each page;

Pass null (or omit the parameter) when a page does not use a content source. An empty string is a valid literal for $contents. An empty $view is normalized to no view, so the page uses its configured contents instead.

$page = new InMemoryPage('empty', contents: ''); // Valid: an explicitly empty page
$page = new InMemoryPage('empty', view: '');     // Valid: equivalent to omitting the view

Use closure contents for lazy dynamic output. If the page needs custom methods or behavior beyond the supported content strategies, extend InMemoryPage. You can add methods normally and override compile() when you need complete control.

class ReportPage extends InMemoryPage
{
    public function reportTitle(): string
    {
        return (string) $this->matter->get('title');
    }
}

Registering the Page#

In a Hyde project#

Register the page in the boot method of your AppServiceProvider. The booting callback runs before Hyde's discovery process, allowing the route to be generated automatically.

namespace App\Providers;

use Hyde\Hyde;
use Hyde\Pages\InMemoryPage;
use Hyde\Foundation\HydeKernel;
use Illuminate\Support\ServiceProvider;

class AppServiceProvider extends ServiceProvider
{
    public function boot(): void
    {
        Hyde::booting(function (HydeKernel $hyde): void {
            $hyde->pages()->addPage(new InMemoryPage(
                identifier: 'hello',
                matter: ['title' => 'Hello'],
                contents: '<h1>Hello World!</h1>',
            ));
        });
    }
}

The page will be written to _site/hello.html and can be referenced using the hello route key.

In a package extension#

Package extensions can register the page directly in the page discovery callback. Pages added at this stage are subsequently discovered as routes.

use Hyde\Pages\InMemoryPage;
use Hyde\Foundation\Concerns\HydeExtension;
use Hyde\Foundation\Kernel\PageCollection;

class ExampleExtension extends HydeExtension
{
    public function discoverPages(PageCollection $collection): void
    {
        $collection->addPage(new InMemoryPage(
            identifier: 'hello',
            matter: ['title' => 'Hello'],
            contents: '<h1>Hello World!</h1>',
        ));
    }
}

API Reference#

To see all the methods available, please see the InMemoryPage API reference.