Pimp Modx

Hi,

What is a handicap of ModX now, in comparison to WP & Drupal:
- a solid and fully automated visual online form builder & management system
- "in-text-editing". Just hovering over the real site, and clicking on a "pen" to edit text or image (like Drupal panels)
- a pre-build arsenal of re-usable code-reservoirs:
--> a bootstrap slider, with less than 20sec to config
--> an automated "TV-generator", based on some clicks. Or just pressing right mouse button in the code "add quick TV here with dropdown"
--> an online community library, with alle commonly used code-combo's easily searchable and copy-pasted
--> something which looks like "Drupal Views" !
--> an advanced Calendar and event-module, fully automated and out-of-the box
--> an online video-library, may be for a monthly cost, with advanced Tutorials (like "Drupalize me")
--> an extensive library with pre-build, empty templates (like bootstrap with banner, etc). With a drag-and-drop functionality, it preconfigures


But don't get me wrong, I love ModX !
Just don't let it get pimped out by other, faster evolving frameworks who are breathing down your ModX neck

Thanks

Honestly, a lot of those things I wouldn't want, and the rest MODX already has.
One reason I like MODX is that often extras are designed to be as flexible as possible and not a turn-key solution limiting what you can do.
This is the same reason anyone besides a Luddite does not want to use Wix or Weebly.

- MODX has Formit. I don't want a restrictive visual version. http://modx.com/extras/package/formit
- For front-end editing there's NewsPublisher (although I've never used it). http://modx.com/extras/package/newspublisher
- There are multiple bootstrap extras. http://modx.com/extras/browse/?search=bootstrap
- Automated TV generator? No thanks. Clicking "New Template Variable" is straight-forward enough for me.
- Community library? The docs are extensive and there are many blogs with different code examples. How would this differ?
- We have getResources instead of views. http://modx.com/extras/package/getresources
- There are calendar extras although I admit a better one could be made. (There's rumour of an official one in the works)
- Online video library? Yeah that would be good.
- There's some templates with backend functionality on themeforest for MODX. Otherwise, a developer could certainly make one for you.

Thanks for your reply !

- MODX has Formit. I don't want a restrictive visual version. http://modx.com/extras/package/formit

This I know, and I can work with it. It just would be useful for endusers, with no coding knowledge, to be able to make their own forms, as many as they, need, without writing code.
Is this it ?
==>mxFormBuilder
visual form builder
http://rtfm.modx.com/extras/revo/mxformbuilder/

For front-end editing there's NewsPublisher (although I've never used it). http://modx.com/extras/package/newspublisher

This I tried once, but it isn't a real front-end editor. Just a "form" that one fills in, not drectly on the page as it is.

- Community library? The docs are extensive and there are many blogs with different code examples. How would this differ?

pre-made code-examples, which are now dispersed in the depths of forum threads.

- We have getResources instead of views. http://modx.com/extras/package/getresources

Doesn't have quite the power of Drupal Views, I've worked with Drupal Views for several projects, and it has like 100 times more possibilities (with Panel views, etc )



- There's some templates with backend functionality on themeforest for MODX. Otherwise, a developer could certainly make one for you.

I learnt a new word today, Luddite.

Yea, this theoretic enduser is a real rare kettle. In fact I used to be enduser until I was tired of being fed microwaved fish.

Sushi all the way!!!

There is something raw about MODx which I like. The Manager alone, with all its supposed magical ExtJS drawbacks, is incomparable.
Wordpress hurts my brain. Drupal injured my ego!
I guess MODx is MODx; if it in-corpo-rated these other features as implemented by other CMS(F), then identity crisis will have been reached.

This said, when MODx is updated, please look at this hyper modern CMS(F), Octobercms. I spy greatness thrust in its path.

Like donshakespeare I appreciate the 'raw' and minimal nature of MODX. Its definitely more orientated towards developers though so I agree with having a front-end editor - that would sell it for a lot of clients. I have to work with Drupal 7 a lot because of this.

Drupal 7 views are horrible for anything relatively complex. I've spent hours ticking different boxes trying to get the query it generates to be what I want. I also end up having to spend way too much time in the admin interface which bugs me.

Quote from: Gibbs at Jul 31, 2015, 07:11 AM

Drupal 7 views are horrible for anything relatively complex. I've spent hours ticking different boxes trying to get the query it generates to be what I want. I also end up having to spend way too much time in the admin interface which bugs me.

It has been statistically proven, that Drupal amplifies the tendency to suicide, rage and madness.

When we speak of MODx lacking a frontend editor, what exactly we be saying?
I have done some pretty sick tweaks to make editing resemble medium.com's
All you need is to get the resource's quiddities out there in forms. Then the rest is client-side browser turf

RE: sriananda

This I tried once, but it isn't a real front-end editor. Just a "form" that one fills in, not drectly on the page as it is.

The fact that NewsPublisher does not stay on the same page does not detract from its front-editing prowess.
You could replicate the look of the resource in NewsPublisher edit mode.
You could convert these forms to contenteditable divs - introtext / description / pagetitle / template variables - not one of these needs to look like a FORM to the enduser

Example:

On page load:
- .hide all textareas/inputs
- $each textarea/ input: dynamically create contenteditable div (use CSS and whatnot to make them look exactly like resource in published view mode)
- $each textarea/ input: copy $this.val() over to respective contenteditable div.
- After copy is done, initiate your RTE of choice, (in this case latest TinyMCE is the best) on each contenteditable div
- In the RTE init code of each instance, on keyup (or whatever) update textarea/input.val() with corresponding contenteditable-div.html()

To make ya life easier - when you create the divs, give them a data-name that is the id of the corresponding textarea. The more JS targetable patterns the merrier