Community Concerns

That's because it doesn't do anything. It's just an HTML/CSS table grid for a date picker. You can attach Javascript to it, or, as I was thinking, make the table grid into a form with the individual dates as input fields.

@Bobray I've been using this it works great on mobile and has many options/features.

This: https://github.com/Nicola1971/BSxFLAT


MODX EVO

Quote from: dan971 at Apr 27, 2015, 11:03 AM

As for content managers who might or might not have any real technical skills, this is a perfect way to split off the rocket science from the clerical duties.

What I'm saying is, we can keep the laboratory in the basement where all us mad scientist can lurk and geek out, but keep a nice clean office space for the people that will actually be using all the tools we create in every day situations. I guess the succinct way to say it is, keep the "web" and "mgr" context, and create a totally new "admin" context where the end-user tools are housed.

I would like to support this to the extent it means, have a core of extras which work and allow basic setup and running to go quickly and smoothly for core functions, build out a space around modx to extend it in common directions. Perhaps the user classes and permissions issue would be the best example, but I feel that way about login which can be quirky at best and is not some smooth and simple step in a much bigger process.

So, I suppose the focus is a little different. You are saying focus on the context because there are different users, but I am saying more broadly make it easier to use for a larger class of users. But we are both talking about the people in the office context.

Quote from: BobRay at Apr 27, 2015, 10:50 PM

Good points. Personally, I'd like to see a pure HTML/CSS Manager for starters with sensible classes and very little styling. Themes could then be created with an overlay of CSS, JQuery, Angular, Ember, or whatever. Almost everything in the Manager, except maybe the file/image browser and datepickers, could be done without JS...

Bob, what makes me a little nervous about this, and please correct me if I misunderstand you, is that starting with very little styling for the control panel might add more development time to a site.

Where I work, my boss has been pushing us more and more toward using WordPress because he believes we can shave man hours off each project, despite all my arguments against this. Having to add control panel styling to the work flow can really work against many of us who depend on cranking sites out as quickly as possible. In the area my company operates, we cater to a lot of small mom and pops with small budgets.

Did I get your comment correctly?

It would come with at least one default theme. The base would have minimal styling, making it very easy to create custom themes.

Quote from: nuan88 at May 01, 2015, 07:07 AM

You are saying focus on the context because there are different users, but I am saying more broadly make it easier to use for a larger class of users. But we are both talking about the people in the office context.

I think I disagree a little with this statement, because that's the issue to begin with. MODx already tries to cater to every possible user group, while I contend that Design and Development are MUCH different activities than Content Management. The end users (our clients, our copywriters, etc.) don't give a flip about how it’s done, just that it's easy and efficient for them to use - thus the popularity of WP (excuse me while I go throw up). The D&D of Wordpress happens behind the scenes within the Themes themselves. Content Managers never have to worry about or even see that stuff, because the Admin area is built for them.

While MODmore’s Content Blocks takes MODx a step in the right direction, it doesn’t solve the real problems of having no built in preview, no versioning system, no auto-save, and no approval process. I absolutely HATE the fact that if a client wants to ”preview” what they’ve done, they have to save the page, thus clearing the site’s cache, and putting a potentially messed up page out there for the world to see. Yes, you can uncheck Empty Cache and Published, but you’ll need to educate them to do that, and then explain why. This is why MODx is a complete deal-breaker for any kind of syndication, which is sad, because we could create a really feature-rich system for a publisher.

Add to that the incredibly tedious effort it takes to create a permission-schema slash manager-customization to hide all the unnecessary or off-limit stuff from Content Managers. I think it just makes sense to have a separate work-flow (context?) for them.

+1 for what Dansig said

The end users (our clients, our copywriters, etc.) don't give a flip about how it’s done, just that it's easy and efficient for them to use - thus the popularity of WP (excuse me while I go throw up). The D&D of Wordpress happens behind the scenes within the Themes themselves. Content Managers never have to worry about or even see that stuff, because the Admin area is built for them.

Agree completely. I'd always rather develop in MODX. I'd rather show a customer Wordpress (although that comes with its own baggage).

Taking this slightly off the backend topic, any consideration being given to improving/automating the upgrade process? If WordPress can do it, and I'm really wanting to steer the boss away from that thing, then is it at all possible with MODx?