Using YAML opens up a world of possibilities and the way in which standard key:values are handled like Title and Date clean up nicely from how they were handled in version 2x.
However, the YAML requirement to have all block content continuously proceeded by a two space indentation is rather troublesome.
I manage content through a text-editor (IA Writer), which is where I draft, write, and save my files. The way in which I manage my content makes it very easy to compose, and then publish, and I can stay in "writer" mode and out of "developer" mode.
Following this convention, means I now need to compose, then go through and indent all paragraphs by two spaces, (which is a mess for editing since paragraph indentations are a print habit and not a digital one. This also poses an issue for sites with an ample amount of content coming from 2x.
On the surface, it seems like a small thing, but in use it causes the content creation and management process to become clunky. An extra step is now added, where I am either going through and "preparing" my content after composing, or I have to indent my paragraphs as I compose (which is rather unconventional).
The point I'm getting at really, is before I could just write my content in any text editor, and all I had to worry about were key value separators, which made things as easy or easier than a form based CMS.
Now I have to modify my content from its intended format before it will work. Adding indentation is clunky and troublesome for the use-case here. It's a step that even most CMSs don't require me to do with form based editing systems. I write my content, I paragraph break, I save, boom, no having to prep the content by indenting it a certain amount.
My suggestion would be to modify this default behavior to allow the content to work without the constant indentation, or rethink this approach entirely.
I'm not saying to scrap YAML right off the bat, but the biggest failure of YAML, is that YAML needs a way to accept literal blocks that have nothing to do with any indentation. This utterly destroys the ease of use and simplicity Stacey has been built upon thus far.
User input after the key and one newline should be preserved exactly, there should be no worrying about proper indentation.
The goal of Stacey seems to be a simple, non-db CMS. The most important goal of that is making managing the content user friendly and intuitive or else it fails at being a CMS. Forcing the YAML convention on the content creation process conflicts with that goal.
Using YAML opens up a world of possibilities and the way in which standard key:values are handled like Title and Date clean up nicely from how they were handled in version 2x.
However, the YAML requirement to have all block content continuously proceeded by a two space indentation is rather troublesome.
I manage content through a text-editor (IA Writer), which is where I draft, write, and save my files. The way in which I manage my content makes it very easy to compose, and then publish, and I can stay in "writer" mode and out of "developer" mode.
Following this convention, means I now need to compose, then go through and indent all paragraphs by two spaces, (which is a mess for editing since paragraph indentations are a print habit and not a digital one. This also poses an issue for sites with an ample amount of content coming from 2x.
On the surface, it seems like a small thing, but in use it causes the content creation and management process to become clunky. An extra step is now added, where I am either going through and "preparing" my content after composing, or I have to indent my paragraphs as I compose (which is rather unconventional).
The point I'm getting at really, is before I could just write my content in any text editor, and all I had to worry about were key value separators, which made things as easy or easier than a form based CMS.
Now I have to modify my content from its intended format before it will work. Adding indentation is clunky and troublesome for the use-case here. It's a step that even most CMSs don't require me to do with form based editing systems. I write my content, I paragraph break, I save, boom, no having to prep the content by indenting it a certain amount.
My suggestion would be to modify this default behavior to allow the content to work without the constant indentation, or rethink this approach entirely.
I'm not saying to scrap YAML right off the bat, but the biggest failure of YAML, is that YAML needs a way to accept literal blocks that have nothing to do with any indentation. This utterly destroys the ease of use and simplicity Stacey has been built upon thus far.
User input after the key and one newline should be preserved exactly, there should be no worrying about proper indentation.
The goal of Stacey seems to be a simple, non-db CMS. The most important goal of that is making managing the content user friendly and intuitive or else it fails at being a CMS. Forcing the YAML convention on the content creation process conflicts with that goal.