Which part of Drupal back-end Needs a better glance ?

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
amjad1233's picture
Administration Themes
33% (1 vote)
UX Elements
0% (0 votes)
WYSWYG
33% (1 vote)
Menu System
33% (1 vote)
Visual Appearance
0% (0 votes)
Total votes: 3

Comments

Back-end?

Riaan Burger's picture

I'd not call those back-end... Do you mean front-end administrative UI?

For my own needs, I'd say the menu router (back-end) can do with uncomplicating it, if it is really possible. I've messed that up pretty badly or inherited sites which were messed up quite badly before.

I know the community is putting a lot of work into things like WYSIWYG that isn't up my alley, but also know how important that is for Drupal to complete on an enterprise level. There's been a few shifts in development in that regard and I've not checked in of late (few months), but if I recall correctly, they went with CKEditor, which is great for me - I always opted for CKEditor over WYSIWYG module because the generic one just didn't do things like source formatting as easily and as well for it's CKEditor plugin.

But we have few core developers in SA, so I'm not sure this is the right place for this question unless you just need local opinion for some reason?

Yes you can say Administrative Front-end

amjad1233's picture

The thing is I have just developed a wordpress site for one client. And I was stunned by it's "Administrative Front-end"

I mean in terms of functionality to achieve a "simple blog". (if you take wordpress to second level, then you are actually "raping" that CMS).

But in terms of User Experience for Drupal like if you want to administer "Admin Menu" I am sure you want find it obvious.(which doesn't exists in many of CMS at all so whatever is there it's already a blessing) but I mean still we can make it better.

I had a look at Spark Installation Profile, the same thing should be in the core. And thus I am running this poll to see what actually developer thinks is important.

In nutshell, If I would to give a wordpress site and forgot to include "user-guide" it would be very obvious to learn. In terms of Drupal I might need to do "tweaks" you know what I mean.

I am re-reading the whole thing and I am thinking of having a Big cup of coffee from woolies... lol

Regards,
Amjad

Wordpress UI does rock

Riaan Burger's picture

As part of training someone on Drupal I always have a day where we install some other web apps. Joomla!, Wordpress, phpbb, SMF the like. We also have a couple of Wordpress sites for clients. It's really good at what it does, very good. Very pretty, very user friendly.

The right tool for the right job. Up to a while ago I always recommended Joomla! to friends that don't have a budget and want to learn to build their own site. Still might (we also have those in our clients' sites).

Once you want to customize more than Wordpress and Joomla! allow, and have a budget or the skills or have Timothy.sea as a friend (tough friend) it's time to break out Drupal. It can do with some UI and UX improvements and Spark demonstrated just how nice Drupal 8 will be in many of those regards. I'm just always a bit weary in being led a certain way into a boxed solution that may limit the scope of what I can do (like the purpose-developed Wordpress).

I know you can pretty much customize all of these any which way. It's just that Drupal is more easily customizable for intricate websites.

For clients we mostly do not give them an admin menu (the admin_menu module's admin menu). Most functionality would be built into the site UI. We expose admin_menu only to clients that are Drupal shops themselves that are selling on to an end-client or to clients that have in-house Drupal talent and even then, it's probably more used for login accounts with elevated privileges and on development / staging sites. Anything you find that your site users use often in there should be moved to the site UI in stead.

Excellent Reply

amjad1233's picture

Hi Riaan,

I really learnt a new thing from this reply. Right tool for right job.

Yet I want to take Drupal to second level, today I was looking at some and "User friendly", twitter bootstrap type themes.

And I finally decided to jump on it and creating Super Friendly theme. No matter even if I have to run this project for whole next year. Of course my only worry is Drupal 8 is moving to twing and I am afraid that I might loose all the work I did.

Anyways the best way to go ahead is to start. Here is the link of the "scaffold" I am thinking for using "Charisma". You might want to have a look at.
http://usman.it/themes/charisma/

Thanks for your comment.

Bootstrap and Twig

Riaan Burger's picture

Bootstrap module already has some Twig work in development, and remember, your D7 site now will likely have a lifetime that is at least 18 more months and likely more like two more years. So go right ahead and dig in.

The only reason I'm not using Twig is that I have so much else I like to learn about and in the theming layer, I prefer Sass/Compass tot he LESS that Bootstrap uses. I know there's a github-hosted Sass solution for Bootstrap, but the majority of additional stuff out there for Bootstrap will be LESS.

I learned about this site from last night's Drupal user group meet-up in Johannesburg, from Robin, if I recall correctly int he unconferencing session: https://wrapbootstrap.com and when I was looking for Sass alternatives for something like Bootstrap I came across this Flat UI http://designmodo.github.io/Flat-UI that you may also find interesting.