When I look through these two lists I see a lot that is developer focused. Better internal and external APIs are definitely targeted at developers and those are 2 of the 11 goals for Drupal 7. When it comes to Drupal 8 configuration management and web services are both things that have a definite impact on coders. The html 5 initiative was for front end developers. Without even digging down into these initiatives I can see a top down approach of developers as a target audience.
Drupal 8's trajectory of a first class REST server built on Symfony is very admirable. If they pull it off might even use it #symfony_live
— Code In A Box (@codeinabox)
@crell's talk makes me want to hug Drupal. Amazing how deeply they've embraced outside libs. An example for the rest of us #symfony_live
— Ryan Weaver (@weaverryan)
not afraid to admit I didn't have much love for Drupal... having said that, Drupal & Symfony looks like a great leap forward #symfony_live
— Chris Rickard (@chrisrickard)
Drupal 8's trajectory of a first class REST server built on Symfony is very admirable. If they pull it off might even use it #symfony_live
— Code In A Box (@codeinabox)
@crell's talk makes me want to hug Drupal. Amazing how deeply they've embraced outside libs. An example for the rest of us #symfony_live
— Ryan Weaver (@weaverryan)
not afraid to admit I didn't have much love for Drupal... having said that, Drupal & Symfony looks like a great leap forward #symfony_live
— Chris Rickard (@chrisrickard)
We will open the core sandbox and meta issue soon, once the above dependencies are resolved or worked around, so that contributors can begin to explore what it means for Views to be in core.
We are planning one last major sprint before feature freeze in the week preceding BADCamp. (Pantheon will be hosting this sprint; more details soon.) The BADCamp sprint will be our chance to coordinate our final push to make Views core-ready. Once Views is committed to core, all further work will take place in our sandbox and the Drupal core issue queue.
I've put together this 15 minute video that summarizes the problems that need to be solved and paints a picture of what an Outside-In UI could look like and what you could do with it.
There are lots of details I couldn't go into within the limited time span of this video. The intent was not to present a finished design. Rather, my hope is that the video can help the community find new answers to difficult problems by introducing new questions to ask. It's an attempt to break out of some old assumptions about how things are done in Drupal.
I see three initiatives (official or not) important for D8 which desperately need help:
1. The mobile initiative (official) led by John Albin.
2. The project browser to solve / help a critical task: New users universally did NOT understand that you can extend Drupal. This would allow to browse modules and themes on drupal.org and install them on a site all from the Drupal UI.
3. Use Twig as our default theme engine. Most work is in this sandbox.
All CSS in Drupal core should be defined by the theme.
This will help in a number of ways:
- Prevent the need for css overrides
- Stop all drupal sites looking drupally
- Allow full control to the themer
(me) - does not affect contrib.
HTML/JS prototype we've created for a mobile toolbar and dashboard for Drupal that we hope to include as part of the Spark distribution and then propose for Drupal 8 core as part of the Drupal 8 Mobile Initiaitve.
Drupal 7's default administration tools (e.g. Toolbar module and Shortcut module) were not designed in a “mobile first" way, and as such can be difficult to work with on tablets or smartphones.
The first Alpha release of Spark has just been released, so we decided to take it for a test drive. Come with us and see where Drupal usability is headed.
The key difference you'll notice immediately is with the black admin bar. There are now View and Edit buttons in the top-left corner.
Click Edit and a grey overlay comes over the page. Anything that you can edit will now be outlined in blue.
With Ember, the Drupal 7 overlay is gone. This is a good thing.
Most transparent Drupal Core development... ever
last updated August 2, 2012.
We are hard at work on the next version of Drupal. Some of the great things planned include better HTML5 and mobile support, improved multilingual features, and setting up Drupal 8 on a modern web development framework. But we can't do any of it without your help!