Great effort and looks very solid for the beta release. I went through the documentation and noticed that in some parts YAML is used, in some it's INI, in some you have
<? $foo; ?> and in others
<?php $foo; ?>. Why not settle on one or two standards? For example, ALL configuration options will be in INI, and all PHP code injection will be in the
<? $foo; ?> format.
Hi! It's not a good idea to use php short open tags, though I'm agree that it is better to use one standard for all configs. Why not to use the standard laravel uses for configs?
<?php return [ 'foo' => 'bar', ]
Exactly! Since October uses Laravel, it would be consistent to use Laravels standards. Also, they are quite nice ;)
<? ?> tags are only used in CMS templates for aesthetic reasons (for the code editor syntax highlighting) and are optional.
INI is a forgotten treasure, it supports sections, a beautiful and simple syntax for defining components. It is intentionally basic to prevent the templates from becoming too scary.
YAML is made for humans and is a superset of JSON, so technically you can go ahead and use JSON and it will work. It is intentionally robust enough to handle many requirements.
All were carefully selected from a scale of happiness :-)
1-4 of 4