Bug #681
Define Event Node
| Status: | New | Start date: | 05/11/2012 | ||
|---|---|---|---|---|---|
| Priority: | High | Due date: | |||
| Assignee: |  Thiago de Mello Bueno |
% Done: | 50% |
||
| Category: | UX | ||||
| Target version: | - | ||||
| Tag: |
Description
Lets customize (or just style) the Event template for clarity.
I'll create subtasks.
Subtasks
History
Updated by Joel Moore about 1 year ago
Can this be elaborated upon? "Let's customize xyz" is vague at best. As relates to theming, please make sure I am aware of new issues as they arise. I am interested in making sure that any new theme development is done according to best practices (specifically Omega & responsive related). Thanks.
Updated by Thiago de Mello Bueno about 1 year ago
Joel!
Thanks for chiming in. The idea for this ticket is to actually start the larger conversation.
As in defining the needs for which to draw a spec from.
Knowing that creating requirements and getting feedback/buy in from the contentteam/owsfolk to ensure were actually improving usability/UX in changing the template.
So indeed once wed identified what would be desiered, we'd then be ready to talk implementation.
Which I would definitely like to run by you, make sure is done properly.
Thanks!
Updated by Thiago de Mello Bueno 12 months ago
- Subject changed from Customize Event template to Define Event Node
