Parse Markdown before parsing blade syntax? about laravel-markdown HOT 6 CLOSED

Instead, I'd recommend moving your markdown parts to separate .md.blade.php file, then including that from a .blade.php file.

from laravel-markdown.

Just in case anyone wants to reference this. Here is what I ended up implementing (as @GrahamCampbell suggested). I'm specifically doing this for a release notes page but aiming to reuse the code for other static markdown pages in the future as well, hence the structure...

routes.php:

Route::controller('pages', 'MarkdownPagesController');

MarkdownPagesController.php:

<?php

class MarkdownPagesController extends \App\Http\Controllers\Controller
{
    public function getReleaseNotes()
    {
        return $this->markdownView('pages.release-notes');
    }

    protected function markdownView($markdownViewName)
    {
        return view('layouts.markdown', [
            'markdownViewName' => $markdownViewName,
        ]);
    }
}

views/layouts/markdown.blade.php:

<h1>Default content here</h1>

<div>
    @include($markdownViewName)
</div>

views/pages/release-notes.md:

## My markdown content

The code above generates a page like this for http://localhost/pages/release-notes:

<h1>Default content here</h1>

<div>
    <h2>My markdown content</h2>
</div>

from laravel-markdown.

We don't do this because blade syntax itself could be recognised by mistake as markdown, and thus, the file broken.

from laravel-markdown.

Right, I see. I'll see if I could make a blade syntax e.g. @markdown @endmarkdown instead.

from laravel-markdown.

That would work for sure. Would be pretty easy to implement.

from laravel-markdown.

Hmm, well, actually, not quite. Only if there was no other blade in between those annotations.

from laravel-markdown.