There should be documentation for the $Block & $Line variabels and $Block['element'] and what the diffrent input are used for, e.g Type or Name

Reading this ( https://learn.getgrav.org/16/advanced/performance-and-caching#grav-core-caching ), I was under the impression that the hash method would actually hash the files (in a fast not-so-secure way as it is not the point.)

I guess that the idea is to not load the file from disk, making it faster. Here comes the issue: when deploying, you have to be careful or preserving file attributes

This version has background management can getshell

When you get the admin rights, we log in to the background.(Choose appearance)

Edit current appearance

Add a sentence

Using a reference-style link fails to automatically convert a markdown file url to its html counterpart, which is inconsistent with the documentation indicating that links should work between pages.

That is to say:

Using [a link](foo.md) to [a page][bar] or [baz][]

[bar]: bar.md
[baz]: b

contributing.md suggests to list ideas (rather than pull requests?)

you are working on a page, cant remember some command, want help, click editor help button and lose your page when you go to another website,
you find what you want but your tab has gone...

solution: open another tab, work stays in the background
v 0.8.10 change edit.js line 668

 // Process help
    processHel

Thank for the great plugin!

Describe the bug

I enabled gutenberg blocks for custom post type. But what see is classic editor. When I deactivate the plugin, the Gutenberg editor shows up for custom post types. When the plugin is active, it doesn't matter whether Markdown is enabled for given CPT or not. Gutenberg editor just doesn't appear.

To reproduce

Steps to reproduce the be

We can refer to the existing link format option https://github.com/Elephant418/Markdownify/blob/master/src/Converter.php#L78

Idea from Elephant418/Markdownify#29 (comment)

Video tutorials are a great onboarding for new users and developers. They can be integrated into the documentation as an easy starting-point for each chapter:

• Typemill setup (typemill setup, settings, plugins, themes)
• Short demonstration for authors (editors, page creation)
• Tutorial theme development
• Tutorial plugin development

My english is not good enough, so on