erisds

Good question, the short answer is no :)

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

It hasn't changed (see https://ghost.org/docs/api/v3/migration/)

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.

Take a look at our docs repo: https://github.com/TryGhost/docs, built with Ghost+GitHub+Gatsby.

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.

I totally understand that you feel ignored, however I can assure you our support team never ignores emails - so something must've gone wrong either with the original email or our reply.

We're always happy to provide another free trial - or you can signup again with an email address variation.

> Is this a business decision to turn as many people as possible to the hosted version? Or is this just the state of node and modern web apps?

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.

We're loading all public-facing resources - so posts, tags, authors and importantly the relations between them - in as few queries as possible, using fairly typical where...in queries in order to build the relations. SQLite uses variables for in queries, and so sites with a lot of content triggered the "more than 999 variables" error.

Solvable, of course, but quite an interesting limitation to discover!

Also a big fan of tldr :) But love the idea of writing my own.

I answered this question in as much detail as possible in the blog post I wrote at the time (which was also linked in the above comment) https://dev.ghost.org/dropping-support-for-postgresql/

First of all, this looks truly awesome! I've spent a lot of time recently looking at the available open source editors, and with the exception of specifically 'code editors' there isn't much out there that supports markdown.

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?

The default database is SQLite, which is a file and doesn't need to be setup or dealt with :)

WordPress already has a "hidden" options page which lets you tweak a tonne of things. Therefore I think you're hitting the nail on the head with hiding the lesser used options away. It'd be nice if, should you change a setting, it would automatically become part of your main options screen & not the hidden one. It would also need to be heavily documented.

I think this is probably preferable to the overhead of tonnes of plugins??

The most amazing browser-based game EVER made!