Support the ongoing development of Laravel.io →
Views Packages Architecture

hi guys,

I have been building some app-sites with Laravel and find myself repeatedly in the situation of adding static content pages for documentation, presentation etc. in a manual in-effective way.

Just discovered getgrav.org (by a joomla developer) which seems to be an incredible elegant tool to manage content in Markdown pages. I have been struggling with wordpress for years now and really only want a simple, easy way to display content integrated with my laravel apps - grav seems to provide that functionality for managing and generating content.

Now am thinking about how to integrate grav with laravel? am not an expert on the internals of laravel but think a loose integration through http could be a simple way of integrating?

  • install grav independently from laravel
  • grav serves content pages through http into laravel
  • the content pages served by laravel could contain blade template code
  • the content pages are handled as blade templates and can be enriched with dynamic data from larval
  • the content is delivered through laravel and therefor in context of laravel
  • the result would be rich content pages delivered through laravel as part of the laravel app

advantages

  • grav can be maintained as it is

disadvantages

  • two repositories (grav content / laravel app)
  • eventually two backend once grav gets one

tasks to solve:

  • how to load grav content through http and provide is as an layout blade template in laravel
  • how to cache to avoid requesting the content with each page view
  • how to map grav urls into laravel routes
  • ...

Any idea how to approach this? Or any other way of integrating grav into laravel?

cheers cord

Last updated 2 years ago.
0

I don't know about grav, but integrating such a system seems to raise a lot of problems.

Wouldn't it be simpler to implement something like https://github.com/thephpleague/commonmark for your static content ?

0

Hi Remi,

grav is worth to have a closer look, it’s a markdown parser on steroids.

When saying content am thinking of documentation libraries where it should be easy to set up chapters and pages. all that would be handled by grav.

cord

0

looks like a way of putting things together could be done by using grav to generate remote views, found a nice approach here:

http://stackoverflow.com/questions/28769358/parse-a-string-instead-of-a-file-for-a-laravel-blade-template

0

I know, but my experience with these kind of monolitic system that are not nativelly build to be integrated can be painful.

Usual method is to host it on a subdomain

0

Sign in to participate in this thread!

Eventy

Your banner here too?

cord cord Joined 22 Apr 2014

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2025 Laravel.io - All rights reserved.