Hey @c.schoech,
thanks for your comments. Let me try to answer them below.
Documentation - Point taken. The main excuse for the current situation is that both Fidus Writer, the languages used, Python and JavaScript, and the packaging systems were changing rapidly and so any documentation would have been entirely outdated by the release of the next version.
This situation has changed now and it will probably be a good idea to write a dedicated manual that can be downloaded as a PDF, maybe after the release of the next version around Spring 2020.
Code blocks - we did have those at one time. The main issue with them was that they caused problems when users didn’t put in line breaks in very long lines. We can probably put them back but have automatic line breaking in those cases that a line is exceptionally long.
Word counter - good idea!
Payment - the main issue is currently that the payment gateway Stripe that we are using (the most common payment system for independent software-as-a-service offerings) is strangely incomplete/buggy. Missing features are things like handling of European VAT and handling users changing their payment information. I have seen others have kind of gotten this to work by hacking it on their side, but they still have issues like the first invoice not including VAT. The fact that Germans – one of the larger communities of Fidus Writer users – don’t tend to use credit cards much is not helping either. I’m currently looking at other alternatives. Preferably something where everything is integrated so that users can choose from more payment options, it takes care of either handling VAT directly or of calculating the correct VAT rate in all of the EU, and users can update their payment details directly. Once something like that is in place, it would make sense to update the page with better information as well.
If anyone has suggestions for payment solutions to review that fulfill some of the above requirements, I’d be interested.