Mark Hamstra

The fact you need to email MODX to get access to edit a specific section is a big barrier, too. ;) Agreed though, the recommendation could possibly explain the motivation...

I've suggested changes to the draft on matdave/mab-recommendations: https://github.com/matdave/mab-recommendations/pull/1

Just for the public record, I've been working on this. [The converted markdown source can be found here](https://github.com/Mark-H/Docs) and [the custom slim app to serve it up can be found...

Anyone can change the label 😁 What I'd like to know before this goes to a vote is what these preferences are. To my knowledge there aren't any in MODX...

Fair enough. Thanks for the clarification. 😄 Maybe the recommendation itself should be clarified a bit too. I took a stab at rewriting the first couple of paragraphs to be...

Thanks @jpdevries, can see how that could be confusing. As for the editor/author terminology... they are and can perhaps be swapped around in some cases, but author might suggest their...

Vasily commented in slack that his extras don't have (public) bug trackers because they attracted too many support questions. Instead bugs are typically reported via email or comments on new...

If it's only lexicons and docs that are in assets that doesn't really matter much to be honest and your solution is great. The main reason I can think of...

I've posted a bounty for this issue on bountysource: https://www.bountysource.com/issues/26863670-usage-on-third-party-extras-i-e-modx-loadrte-requires-double-save-for-content-to-be-available 

It also looks like ``` php $app->get('/hello/{name}', function ($request, $response, $args) { $this['view']->render('profile.html', [ 'name' => $args['name'] ]); })->setName('profile'); ``` should be something along the lines of this: ``` php...