Laravel + Statamic - control panel?

[AimForNaN]

Let's say we install laravel, then we install Statamic into our existing laravel. Now, how would we go about setting up our laravel app to work with Statamic without having to setup a user and without having to use the control panel? The documentation appears to assume the control panel throughout and that your app is already fully configured for Statamic after installation, while briefly mentioning that the control panel "can be" optional. Am I forced to look through the source code of the control panel?

[afonic]

That depends on what you mean by "work with Statamic". You can definately work without the CP (like a headless CMS), which usually means populating the needed files in /content and /resources by other means. Statamic is a flat file CMS, so all you need to start working are a couple of yaml and md files.

Example: You can create a Collection and it's Blueprint manually and then use the Entry facade to create entries inside your Laravel application. If this sounds similar to what you're trying to achieve, check the available Repositories: https://statamic.dev/reference/repositories

[AimForNaN]

That's what I thought, but it doesn't seem to happen so smoothly.

Let's say I have the following collection:
/content/collections/blog.yaml

template: blog.blade.php
route: '/blog/{slug}'

And the following entry:
/content/collections/blog/test.md

---
id: ca22c1ef-0e8b-46fa-abc4-afddec9bc8a9
title: Test
---

test

And the template at /resources/views/blog.blade.php.

Why would navigating to /blog/test exit out with the error?

View [blog.blade.php] not found.

[AimForNaN]

Nevermind, I got it all working now.

[jackmcdade]

Take the .blade.php out of the route definition in the tank config.

…

On May 4, 2022, at 8:55 PM, truefusion ***@***.***> wrote:  That's what I thought, but it doesn't seem to happen so smoothly. Let's say I have the following collection: /content/collections/blog.yaml template: blog.blade.php route: '/blog/{slug}' And the following entry: /content/collections/blog/test.md --- id: ca22c1ef-0e8b-46fa-abc4-afddec9bc8a9 title: Test --- test And the template at /resources/views/blog.blade.php. Why would navigating to /blog/test exit out with the error? View [blog.blade.php] not found. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.