Thank you for introducing and presenting Cockpit. I’m the creator and developer of the project.
I have some additional notes to the article:
-
Cockpit comes already with a Markdown compiler (Parsedown + Parsedown Extra) and provides an api for that, so there is no need to for an extra dependency in your project. http://getcockpit.com/docs#!helper/markdown
-
Paths and urls: as mentioned in the article, Cockpit saves paths with folder namespaces. e.g. “site:folder/file.jpg”. This makes it pretty easy to move the project, local dev to the live server for example. There is also an api to resolve those paths: to get an url just call get_url(‘site:folder/file.jpg’) or to get the realpath call get_path(‘site:folder/file.jpg’).
Reference: https://github.com/aheinze/cockpit/blob/master/modules/core/Cockpit/bootstrap.php#L88-L108 -
There is a “simple” REST implementation: http://getcockpit.com/docs#!helper/cockpit-js. But I have to admit that there’s a lot of documentation missing. I hope to fix that soon.
I agree with the statement that Cockpit is very developer centric. But with that comes great flexibility. Custom layouts, routing, project structure etc. you can even use Cockpit as a data provider for a mobile app if you want.
Again thank you for writing about Cockpit!