[FEATURE] YAML Frontmatter Plugin for Meta data and for making it easier for users other systems to migrate to PhileCMS? about phile

[NeoBlack]

Hi @bzerangue
sorry for the late response, I haven't seen this issue before.
Would you use the YAML for configuration stuff or for the meta section on each page?
Can you provide some example code or projects where YAML is used for meta configuration?

[bzerangue]

@NeoBlack, no worries. I would use the YAML for the Meta Section YAML Front Matter and for separate YAML Data Files (if possible). This would make it quite easy to migrate from a Jekyll site or possibly a Statamic site.

With YAML Front Matter (YAML Meta Data)... this is would be acceptable for meta data...

---
title: Skyfall
published: true
layout: post
tags:
- skyfall
- james bond
- 007
- daniel craig
podcast:
  file: http://domain.com/podcasts/skyfall.mp3
  length: 0:46:01
  filesize: 36370560
---

Also, in regard to YAML Data Files, I envision it how Jekyll has it setup... for instance if you have a staff list.

[NeoBlack]

@bzerangue sorry again for the late response, I was very busy the last months.

I think we could change the meta parser to service, this way it is be possible to replace the meta parser by a plugin.

I will talk to @james2doyle about this issue, but I think a service is a good solution and make phile more flexible.

[james2doyle]

I'm down for the meta-parser as a service. Makes sense. Maybe there are other ways to do meta. Like a same-filename json or something

[NeoBlack]

ok, I will open an issue for the global changes in the architecture.
I will take a look at it tomorrow. Maybe the change is easy, then I would implement it shortly, so we could add this change to 0.9.3 and release this version next week.
The codings for a YAML Front Matter Config plugin can be done after the release of 0.9.3

[james2doyle]

"Someone" will have to make a phileYAMLMeta plugin now after #76 and #77. So I will close this.