I think something good might come out of this and I actually loved the name (I clicked on this because waffle.io souded cool). What I really think , in terms of design, is that you should get rid of that 3d rendered waffle.io image with that shadow. Not only it makes the website look like something of 5+ years ago but you can also see that the image is heavily compressed and is not looking good at all.
Waffle.io
61–66 of 66 posts
Re: Waffle.io
#62This is wonderful. The main page doesn't mention the term, but the easiest way to describe this is that it is adding a Kanban board to Github. http://en.wikipedia.org/wiki/Kanban_board The simplicity to effectiveness ratio of Kanban boards really impress me.
Compare this page to libressl.org
Reading it three times and I still dont get it what its for for whom and what it does. But at least it looks fancy.
Re: Waffle.io
#63Great idea. Obscure landing page.
It's practically impossible to know what this does,unless you click on the [our board] link. Even after scrolling all the way to the bottom of the page where you are asked to part with money.
It would be a shame for such a great idea to be passed by due to lack of clarity.
Re: Waffle.io
#64Earlier quoted context omitted.
I agree the landing page is confusing though I believe it's called waffle.io because kanban cards create a grid pattern & waffles also have a grid pattern.
It's an interesting choice as in British Vernacular Waffle - speak or write at length in a vague or trivial manner.
As a verb waffle has the same meaning in American English but the images of waffles on their landing page make it clear they are going for the food. For me at least it's easy to not jump back and forth between meanings of waffle once I understand the intent is to refer to the food.
Homonyms can be confusing but it helps when such a stark difference in meaning makes it easy to distinguish what meaning is appropriate in a given context.
Re: Waffle.io
#65We use kanban for the Brackets[1] project, so I've been looking into tools like this recently. The most promising one I've seen so far is Octokan[2]. What I like about Octokan is that it:
1. uses GitHub Issue labels to represent the columns (unlike Waffle) 2. doesn't require all of our open issues to be "on the board" 3. is faster than Huboard 4. uses horizontal scrolling with fixed width columns like Trello rather than trying to pack all of the columns into the width of the window (also in contrast to Huboard)
We currently use Trello for our backlog and kanban[3] but it is kind of painful to synchronize this with GitHub (and so we don't... there's a lot of "small item" work that happens only in GitHub and is not tracked through our kanban flow).
None of the tools I've seen provide us with cycle time and throughput metrics, which is a drag. We're likely to write a script to pull the data out of GitHub and calculate those values. (GitHub, alas, does not track when labels are added or removed... so we have to start there in our custom work.)
I think it's great that there are people building better visualizations on top of GitHub Issues and I'm looking forward to seeing how tools like Waffle, Octokan, Huboard, etc. evolve.
[1]: http://brackets.io [2]: http://octokan.com/ [3]: https://trello.com/b/LCDud1Nd/brackets
Re: Waffle.io
#66I like the idea, it seems really helpful, but just as a warning if you call your site Waffle and blue is the prominent color, especially on the logo, you're going to cause people to make connections that shouldn't be made...
I agree. I immediately closed the site down and came and checked the comments as I assumed it some sort of trap.