This is waiting on...

http://drupal.org/node/491454

However, wanted to start a new thread as once the mechanism to add default issue components to existing projects safely is there I think it will still be necessary to decide if this is a good idea and more importantly what the name of this new issue component would be.

To recap this issue...

At D4D Boston there was a working group to discuss ways to help the design community interact with the drupal community effectively. One idea that came out of this is to make it easier and more direct for a themer/designer to add an issue to a module issue queue _specifically_ to suggest that the module provide improved markup.

Since developers live in their issue queue this feels like the right place for feedback about default markup output to be provided.

Use Case: Module X outputs really poor markup. Themer/designer copies the markup that the module gives, modifies it as a "here is what I think it should be", and submit that as an issue with the component "Markup". Ideally this helps start the conversation about exactly what needs to happen to either improve the default markup or provide excellent documentation on how to get the markup the designer wants. Having a dedicated "markup" component also makes it easier for a module maintainer to manage specifically design/UI issues in the queue.

Please review the issue at http://drupal.org/node/491454 to see the work done so far by sethcohn, dww and myself so far. It needs review to be RTBC.

Comments

winston’s picture

winston commented
Status: Active » Postponed
dww’s picture

dww
we/he/they
commented

Once #491454: Provide a way to add a new default component to existing projects lands, this will just be a d.o specific configuration task, not a project_issue feature. That said, we've already discussed the d.o use-case in #491454 so I'm not sure there's a point to duplicating that discussion by moving this to the infra or webmasters issue queue. Tempted to just close this as a duplicate. What do you say?

winston’s picture

winston commented

dww, your call. The problem I have right now is that I can't easily refer themers/designers to the other issue as the name of the issue is pretty far away from this particular proposal. I was hoping to be able to refer themers/designers to this issue to discuss the idea in general and maybe get a consensus on what this should be.

For example, the Zen project is one of the few I found that has a component for this already and it is called "CSS/HTML Markup". Is that the best name? In my discussions with a couple of people at D4D in Boston the thought was that Markup was fine by itself as CSS is easily over-ridden - it is markup that it not as easy (at least not to those without a little php knowledge).

So this issue isn't about making it possible, but rather what will we call it when it is possible.

Is there a configuration queue? If so, could we just move it there with a status of postponed?

dww’s picture

dww
we/he/they
commented
Project: Project issue tracking » Drupal.org site moderators
Version: 6.x-1.x-dev »
Component: User interface » Site organization

Ok sure, then this would be a better place for this issue.

For anyone seeing this for the first time, #491454: Provide a way to add a new default component to existing projects is worth reading for background and some initial discussion about these questions...

tvn’s picture

tvn commented
Status: Postponed » Closed (won't fix)

Closing old issues. Please re-open if necessary.