Timeline for Best way to deliver "mockup tool kit" to engineering team?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 7, 2012 at 15:59 | answer | added | Gordon Kennedy | timeline score: 2 | |
| Mar 7, 2012 at 15:48 | comment | added | dennislees | Because I'm dealing with 25 people in 3 countries, with different levels of code-savvy ranging from expert to clueless. Suggesting that we all start working in html/css is not an option. | |
| Mar 7, 2012 at 11:37 | history | tweeted | twitter.com/#!/StackUX/status/177357371843158016 | ||
| Mar 7, 2012 at 10:57 | answer | added | Matt | timeline score: 4 | |
| Mar 7, 2012 at 10:27 | answer | added | Rahul | timeline score: 3 | |
| Mar 7, 2012 at 9:48 | comment | added | Rahul | Bootstrap is implemented in live CSS and HTML; why would you take that a step back to bitmap images? Seems counterproductive to me. | |
| Mar 7, 2012 at 6:17 | comment | added | dennislees | To begin with, it will just be a collection of UI elements (buttons, tables, controls, etc.) and perhaps some empty browser window templates with gridlines to show where our fixed elements like navigation will go. | |
| Mar 7, 2012 at 6:12 | comment | added | Mervin | Sorry but can you elaborate on what you mean by a mockup toolkit,is it just a collection of mockups and style guides ? | |
| Mar 7, 2012 at 6:08 | history | asked | dennislees | CC BY-SA 3.0 |