erisds
Joined 16 years ago
Joined 16 years ago
But also, https://wordpress.org/plugins/ghost/ has been overhauled to export from WP into a format you can import straight into Ghost 3.0.
All of our API docs are maintained by developers who are happiest in git and markdown - so those files live in GitHub, with the added benefit of being available for anyone to contribute to.
Meanwhile, our Ghost(Pro) documentation is maintained by our support team, and integrations & tutorials are maintained by our marketing team - all people who are happiest with the editor and workflows provided by Ghost.
The beauty of JAMstack is just how simple it is to combine multiple sources of data into a single site. Power, flexibility, and most of all choice.
We're not ramming Ghost down anyone's throat. If you don't like it - you really don't have to use it. The decoupling work we are doing intends to make it possible for people to pick and choose bits of Ghost that they do like, and use them however they want.
We're always happy to provide another free trial - or you can signup again with an email address variation.
Ghost-CLI is an open source project, led and built almost entirely by contributors from the community.
The process is rigid because they don't have enough hands to support more variations in environment.
Solvable, of course, but quite an interesting limitation to discover!
I have been reading about the recently announced content-kit: http://madhatted.com/2015/7/31/announcing-content-kit-and-mo... and am wondering if you have considered the 'card' style concept for ProseMirror? I see ProseMirror has an interface for adding images, and says that it will support different document models in future and I'm wondering how extensible that will be.
What sort of APIs are going to be available, will it be possible to create custom 'blocks' or 'cards' of data - e.g. defining a block for adding a table / spreadsheet - similar to what you see in things like Quip or readme.io?
I think this is probably preferable to the overhead of tonnes of plugins??
The long answer is it's absolutely everywhere in our codebases, with some code relying on catch-predicates, meaning we have to pull it out in exactly the right order else things will break in weird ways... and we haven't gotten around to tackling that yet.
Would love to get some help to get it out though - I raised an issue here: https://github.com/TryGhost/Ghost/issues/14882