Markup and styles for upcoming task UI

Problem

• hardcode any component you’re working on
• test it out without having whole models instantiated
• CSS class naming should go as follow, following BEM conventions.

task-board

task-list task-list__title

task-card task-card__title task-card__number task-card__type task-card__time

And the modifiers could be: --inbox, --backlog, --progress, --done (e.g. task__card--done)

Subtasks

• task-board (holds the four columns, never taller than window, scrolls left/right to show columns)
• task-list (the column)
• task-card (the individual task)

References

Progress on: #2 (design repo)

[rlueder]

Sounds good! let’s not let semantics paralysis get to us! (btw I checked Trello and they use board, list and card) 👍

[joshsmith]

I agree that the axis probably would not flip. I do think though that swim lane and lane are too methodology-specific and not as friendly for ESOL speakers. I think either list or column wins out, and prefer list since it matches closer to the TaskList object we’re likely to have on the backend.