HTML5

I put together the beginnings of a module with a form using the Forms API. It had nested fieldsets and looked pretty good with the default Bartik theme. When I saw the HTML5 support for email, tel and number fields, I tried to use them by installing elements module and then the html5_tools module, and finally the Omega theme. I am assuming Omega is needed for HTML5 support, although I have not seen any specific mention of it.

What do you all think is going to happen to the state of HTML5 in Drupal 7 with the development focus shifting to Drupal 8? I worry a bit there's still going to be some large gaps in HTML5-related technology integration with Drupal 7 as the focus shifts.

I've just finished up writing a guide to HTML5 in Drupal 7:
http://www.daymuse.com/blogs/drupal-html5-guide-theming-tags-and-templates

Do you all have any thoughts on the remaining gaps in HTML5 implementation for Drupal 7 and where we go from here?

Happy Friday! I maintain the admin theme in Drupal 8 core: Seven. There have been many changes to Seven in Drupal 8 that affect the relationship between admin themes and modules, and how the admin UI is generated.

I've always thought that the strategy we've put in place are going to have a positive impact on maintainers of contrib admin themes, but I've never sought out feedback directly. I am now!

Object oriented CSS

Im new to drupal, and i want to create a full HTML5/CSS3 site, what modules and tools do i need to work with to do that or are the three listed tools in this group enough?

We (the Drupal 8 Twig people) are doing a survey about the theme system in Drupal - please fill it out, the data is important for future development of the theme system:
Theme Survey 2014

cheers!

Drupal Dev Days is an important event in the Drupal calendar. The sponsors and organisers are kind enough to provide the community with a place to sprint for the entire week.

Hi all, or hello world!
1)Is there a way to change this template: http://www.consulcesi.it/ in a new one in html5?
2)Is possible to keep the same structure of the Urls?

The more is similar the more is good ;)

Thanks!
Lorenzo

p.s.
this is my first post. Dunnow if is the right discussion but...any help for the questios before? :)

It's been a pet peeve of mine for a long time that, while D.O and G.D.O have a lot of great ways to add ideas and discuss them there's really no efficient way of collectively prioritizing the ones we should focus our efforts on.

I have spent a lot of time trying out different tools that do this, as well as trying to design and build them. We may at some point reach a home-grown solution, but in the meantime I have found a very simple and effective tool that I'm trying out. It's called Tricider. I've posted an initial question here:

http://tricider.com/brainstorming/1H6kX

I am trying to install Bootstrap theme in Drupal 8, but am not able to install it. This was trail to start with drupal 8 themeing. Any help on this welcomed,

I get error message

"The bootstrap theme was not found.
Your version of Drupal is no longer supported. Upgrading is strongly recommended! See the available updates page for more information and to install your missing updates."

I did updates but still same issue.

Target in hand for the mobile initiative:

Complete a survey of 3rd party resources to aid with component naming conventions.

The different steps are:

Do a survey of various style guides to see what others have named these components and build a list of possible components in a Google drive spreadsheet at: https://docs.google.com/spreadsheet/ccc?key=0AvR7gnIrX0ckdDgzNDI0blZVSnF...
List of style guides/resources that should be used for each component:

A non-profit, developer-first, community-focused conference.

Join designers, developers and drupalistas for four days of focused experience-sharing, talks and sessions on design, frontend engineering and Drupal. From 31 May to 3 June 2018 in Utrecht, The Netherlands

Frontend United in copenhagen 29 - 30 - 31 August 2014

Friday: Sessions & Frontend Love
Saturday: more Sessions & Frontend Love
Sunday: Codesprint

Join Drupal 8 mobile initiative meetings! Catch up with what's next after code freeze for the Mobile initiative...

The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Tuesday, July 16th:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Wednesday)
Convert to your timezone

Join Drupal 8 mobile initiative meetings! Catch up with the all new CSS Architecture...

The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Tuesday, June 4th:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Wednesday)
Convert to your timezone

If you can’t attend at this time, there’s an additional meeting in Asia Pacific timezones at #40.5

Join Drupal 8 mobile initiative meetings! Catch up with what happened in Drupalcon, hear John's Drupalcon stories...

The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Tuesday, May 28th:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Wednesday)
Convert to your timezone

The Drupal 8 mobile initiative meeting Asia Pacific timezones! Catch up with what happened in Drupalcon, hear John's Drupalcon stories...

The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Wednesday, May 29th:
San Francisco — 8pm (Tuesday)
London — 4am
India — 9:30am
Taipei — 12pm
Sydney — 3pm
Convert to your timezone

Background

The movement towards semantic data

Please join us for our next Mobile Initiative meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Wednesday, January 23:
San Francisco — 8pm (Tuesday)
London — 4am
India — 9:30am
Taipei — 12pm
Sydney — 3pm

Please join us for our next Mobile Initiative meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Tuesday, January 22:
San Francisco — 11am
New York — 2pm
London — 7pm
Taipei — 3am (Wednesday)
Convert to your timezone

Please join us for our next Mobile Initiative meeting to discuss issues related to the Drupal 8 mobile initiative. The meeting will be held as a Google+ Hangout (online video) with concurrent text chat in #drupal-mobile on IRC at:

Wednesday, January 16:
San Francisco — 8pm (Tuesday)
London — 4am
India — 8:30am
Taipei — 12pm
Sydney — 3pm

At DrupalCamp Ghent, we held a very small frontend BOF, with myself, Laurii, Emma.maria, and guest frontender Xano.

It quickly became a retrospective on the Friday sprints that took place at DrupalCon Amsterdam. The collective thoughts were not positive. It felt like we fell way short of our goals and potential for the Friday sprint. Drupalcon Friday sprints are about introducing people to sprinting and it feels like we failed badly at that.

Here were some of the problems:

• Newbies did not get enough help
• The few people helping the newbies did not get enough support

To cheer the contributors of the Drupal 8 Mobile Initiative, I am starting this initial list.

Did you work on the mobile issue queues? Did you add a patch? Did you review patches? Did you do manual testing? Did you work on the mobile handbook pages? Please edit and add a link to your user account, your twitter handle, indicate if your company sponsored some or all of your work. Provide a brief description summarizing your contributions.

Problem

"As a content author I want to make a quick change to a block on a page I am editing without having to wade through many levels of navigation or a sea of options."

As part of the Drupal.org code sprint in Portland; Chris Ruppel, Joel Moore and myself have been discussing a new Bluecheese. A lean, tight, and admin friendly theme that lays out a framework for the future. One that would allow us to develop a mobile friendly, responsive design.

What we want

An admin friendly UI

If you have development chops, designers and other contributors of this community need your help bringing designs to life.

Allow me to paint a picture of the need and skills required...

The task of creating content has been redesigned (http://groups.drupal.org/node/217434), and has reached a point of consensus. At this point, the design really needs to interactive to flush out how all of the various interactions will work (or don't). Additionally, once made interactive, we validate the direction by testing the prototype with end users.

Please edit this wiki page if something needs more clarification, needs a link to a comment thread, etc!!!

Attendees: jacine, mortendk, aspilicious, ericduran, Crell, Transition, linclark, katherined, davereid, webchick, jhood, jbeach, zigmoo, RobLoach, dcmouyard, lewisnyman, Snugug, (if I missed anyone please add yourself)

Issues mentioned in meeting along with select comments: (I left more of the discussion in since some of the issues require more background information to follow)

Issue #1 http://groups.drupal.org/node/211633 => Drupal 8 feature freeze: December 1st, 2012

Below is the agenda with notes we took today in the PiratePad document, slightly modified for better organization and readability.

Agenda

1. Set up regular meetings.
2. Start mapping out initiative goals to actionable issues.
3. Create a roadmap document where we’ll track progress.
4. Discuss documenting our work.
5. Discuss current issues and roadblocks.

1. Meetings

• Meetings will be held regularly to discuss sprints, progress, outreach and any issues that may be blocking progress.
• It was decided that the meeting will occur every 2 weeks one Tuesday at 8pm UTC (1pm PT / 4pm ET).

Here are the principles we will follow when developing HTML5 functionality for Drupal.
These principles are open for discussion here in this wiki.
Please add your feedback below.

10 GUIDING PRINCIPLES
1. Support older browsers.
2. Lean into the diversity of devices.
3. Maintain existing functionality.
4. Perform.
5. Be accessible.
6. Get semantic.
7. Fulfill the common use case, not the edge case.
8. Mimic XHTML. Be HTML.
9. Value findability. Not mythology.
10. Value practicality over purity.
11. Support evolution.

10 GUIDING PRINCIPLES
0. HTML5ify

(Let's create a Myth versus Fact document to answer reoccurring concerns about HTML5 and Drupal. Anyone can edit this document and provide answers. HEAVY rewriting is welcome at this stage!)

=====

Myth: HTML5 is not done, we should wait until it's done before implementing it in Drupal.

Fact: Most of HTML5 is dividable in 3 different groups: "it just works", "degrades by default", and "some effort required". See http://mathiasbynens.be/notes/html5-levels for additional information.

At 1st we're starting to make cck widgets for every html5 elements.

We already have the number field in the html5_tools.module file and you can use that as a base for starting the other fields.

If you're interested in what new fields are available take a look at the elements module code, there is not support for email, number, url, color, and range.

Declaring a new widget type.

/**
* Implements hook_field_widget_info().
*/
function html5_tools_field_widget_info() {
return array(
'numberfield' => array( // Machine name of the widget.