nodeform

This module adds a "delete" MENU_LOCAL_TASK to all nodes and removes "delete" button from all node forms. While this module is very simple and may not seem important for a developer, it does provide a significant improvement for content publishers/maintainers, especially to those who are new to Drupal.

Please leave your feedback.

Also, can I submit it as a contributed module?

deletetab.info:

; $Id: $
name = Delete Tab
description = Adds "delete" tab (MENU_LOCAL_TASK) for all nodes and disables default "delete" button on node forms.
package = Administration

There are many Drupal 7 core issues that are tagged as "Needs usability review". It would be awesome to try and keep an eye on this list and review UI changes that are going in to core/7, with the aim of trying not to degrade Drupal usability further with un-monitored changes, as we usually do in Drupal core. The most important ones to review are the ones that are in the review process, marked RTBC or recently committed.

Vertical tabs are finally in Drupal core!

Screenshot of vertical tabs on an 'Article Edit' page in Drupal 7.

A week ago Angie "webchick" Byron committed a large patch from #323112 Vertical Tabs to Drupal 7 core. This change is quite possibly the most significant usability enhancement to Drupal 7 to date. Two of the three formal usability tests did usability testing with vertical tabs and reported positively.

Screenshot of a 'Story Edit' page in Drupal 6, before vertical tabs.

UPDATE: Rob Loach has created a patch to implement vertical tabs on the node-type form.

UPDATE: See other issues about vertical tabs in Drupal core .

What is more interesting about this however, is the process, time and effort that it took to get this change into Drupal core. It all started over a year ago, well before DrupalCon Boston 2008 even before Drupal 6 had a stable release. The discussion around part of that patch goes back as far as November 2007! Along the way countless people have been involved in many discussions, worked on heaps of mockups, lots of prototypes, and loads of code.

Read more

Over the past two weeks at the core internationalization virtual sprint, we've been working on translatable fields. This would allow any core field attached to a node, user, taxonomy term etc. to be multilingual.

Core already allows for translating one entire node into another node, but you can't for example have translatable user profile fields, or taxonomy descriptions - and we're hoping this patch would be an enabler for that (and also make node translation more flexible).

First of all I must say that Michael Haggerty's solution looks great. I've worked along the same lines with my project, that is, splitting the node form into two columns, not exercising jQuery magic. My module splits node forms into a main and right column and a footer. The admin interface makes it easy to change the region placement, weights and collapsed-state of all top-level form elements.

Michael Haggerty is working on an interesting node-form customizing tool for Site admins. See the video demo and blog post (from Planet Drupal). It appears no code has been released yet. I believe there is some cross-over here in functionality with Panels2, although I've never actually used that part of panels2, so I'm not sure.

This is my first proposal for changes to the content creation form.

They are minor but yet I feel they will make things easier. I thought let's get a few basic things rolling before we get to the really hard stuff later on. Pease do comment on each of the four changes seperatly.

So here are my thoughts behind this mockup.

<

ol>