Is there a way to make the Commerce Kickstart Admin Theme responsive ? Currently, Wordpress, Joomla 3.0 and Magento Mobile had done a pretty good job making both front-end & back-end responsive even with their own Mobile Apps.

Commerce Kickstart is impressive but the store owner still can't properly manage their store even viewing reports on their Mobile Devices, everything is out and looks cluttered, tks.

#3 commercekickstart.PNG54.14 KBjetwodru
Members fund testing for the Drupal project. Drupal Association Learn more


jsacksick’s picture

Project: Commerce Kickstart » Shiny (Administration theme)
Version: 7.x-2.4 » 7.x-1.x-dev
Priority: Critical » Normal

The admin theme has it's own project, switching to the Shiny issue queue.

bojanz’s picture

The drupal admin itself is not responsive in D7 (things like the toolbar, overlay, etc).
I don't think we can fix this in a theme.
Leaving it open for Aaron to make the final call.

jetwodru’s picture

Version: 7.x-1.x-dev » 7.x-1.0
Priority: Normal » Critical
54.14 KB

Yes, you're right, it's not responsive at all with the Overlay as attached. Indeed, I don't like the Admin Overlay, always blocked part of the header session when in theming. I still prefer the way how Wordpress & Joomla Admin work, more intuitive.

Well, in conclusion, Drupal is still not ready in Mobile world yet and I'll propose Joomla 3.0 & Magento Mobile for customers.


bojanz’s picture

Category: feature » support
Priority: Critical » Normal
Status: Active » Fixed

Either that, or build a custom app for the targeted admin tasks that you need.
In general, exposing an admin UI of the current complexity to mobile users is non-trivial.

jetwodru’s picture

Not really, it's very common already, Joomla 3.0 had done that in both Front-end & Back-end since last year, very appealing & user-friendly on Mobile Management. Same to Wordpress For Mobile Apps & Magento Mobile.
I think Drupal is considered late at least 1 year behind embarking on the mobile trend among the top CMSes, tks.

dudenhofer’s picture

Have you taken a look at the D8 Mobile initiative? A lot of work has already gone into making Drupal 8 mobile friendly. But bojanz is right, it would not be a simple task to make the whole admin interface of Commerce Kickstart in Drupal 7 mobile at this point.

jetwodru’s picture

Yes, I'd read thru the Spark project on Dries's Blog last year, very excited with it. However, I don't think D8 will become popular by 2015 due to the lack of support of 3rd-party modules initially.
Based on the past experiences, many modules would only support the latest release of Drupal after 1-2 years. As expected, D8 might NOT be my choice before 2015 or even 2016 depending on the availability of major modules.

pedrorocha’s picture

@jetwong98, D8 doesn't could be compared to other major version upgrades, because now we'll have the main modules inside the Core, so you'll really be able to create a project.

As an example, i remember that with D7 i waited a long time because of Views module, that now is part of Core.

jetwodru’s picture

I don't think Drupal Commerce and its submodules will be ready within 1 year after the release of D8. Many Drupal Distros had just released their D7 version this year like Drupal Commons, Drupal Commerce (earlier UberCart) and no update of Open Atrium and etc. What I dislike Drupal was its lack of Meta Titles, Block/Menu Class, Node Access Control namely node/1, node/2 Mandatory security control but always ignored in core, Dunno Why) .

Previously I came from Joomla and found its primitive features in core with various extensions working in a silo manner and that's why I moved to Drupal, more powerful & integrated esp CCK, Views, Rules, Webforms, Date & Calendar, I can use Drupal to replace Visual Studio.Net for designing complex custom forms now. Unfortunately, recently I have to go back to embrace Joomla 3.0 due to the lag of Drupal in mobile era. Frankly, I always want to focus on 1 platform exclusively rather than multple platforms, but no choices now.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.