-
-
Notifications
You must be signed in to change notification settings - Fork 615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow parse content using Twig (.html files). #110
Conversation
👍 it would be awesome if this was accepted upstream... |
This fork works with getting Twig functioning, but plugins don't appear to work 😦 |
I was recently thinking about this idea while working on Pico 2.0 (#334) and thinking about Pico 3.0 (#317), but came to the decision, that we shouldn't explicitly allow replacing Markdown with other "content processors" (like Twig). If you want to use Twig for some "more complex" pages you can already do that. Simply create a ---
Template: my_complex_page
--- and a matching If you want to create a larger number of such "complex" pages and don't want to create both a (basically empty) If you rather want to extend the Markdown processor (i.e. the If you want to completely replace Markdown, YAML and/or Twig with something different, you can extend Pico's class and replace the respective methods as you want (Pico is open source). We obviously will neither officially support this nor will this work with all existing plugins or themes out there, but you definitely can do this if you want to. Thank you for your feedback anyway! 👍 |
No description provided.