I consider that WIP can be used as a kind of changelog, in long-running changelogs, you often have an introduction section that focuses on highlights and a way of seeing more if you care
Here is my inspiration: blog.golang.org/go1.14
Some people use the "Product Updates" feature for this, which lets you write rich text posts about your product. It requires you to do more writing, but the upside is that you can nicely summarise a bunch of different changes in one cohesive story.
That feature needs a lot of work though. It's not very discoverable to begin with, and when you publish a post it doesn't get much attention on the site.
What do you think of this solution? Being able to write a short post, optionally linking to certain todos.
Yes, it can be the solution, and I like the idea to have more work to do when you want to highlight something 👍
I think that:
1. it should be displayed on the timeline (don't know if it's the case today)
2. it should probably "count" as a done task for the author
It currently isn't displayed on the timeline. It totally should though!
Right now it doesn't count as a done todo either. I guess we could make it count for the streak, as writing a status update is indeed work. And having to create a todo "Wrote a product update" just after you wrote it on WIP seems like unnecessary work.
I start to know individuals and their habits, to I pretty like the current view, but if you can keep the two views, yes, it can make sense to switch to the ungrouped view by default 👍
Or to keep WIP simple, maybe you can use the per-event view by default, and the grouped-by-user one only for people you follow?wip
So the nice thing about grouped-by-user is that you get the full context of what someone is working on today. One todo by itself might not always be meaningful, but by seeing the other things that person worked on today you get a good sense of what they are doing.
On the other hand, the downside is that every time someone posts a new todo it bumps up their whole list of that day. So as a viewer you start seeing the same content and you're not sure if there's anything you haven't seen it yet further down the page.
Perhaps there's an alternative solution possible. For example only showing the new todos (grouped per user), with the todos you've already seen hidden by a "See 4 more todos…" button. Although that would require us to start tracking which todos you've already seen. Or least a timestamp of when you last viewed the homepage. (anything created after that would be considered unseen).
Spotlight / highlighted tasks
I consider that WIP can be used as a kind of changelog, in long-running changelogs, you often have an introduction section that focuses on highlights and a way of seeing more if you care
Here is my inspiration: blog.golang.org/go1.14
Some people use the "Product Updates" feature for this, which lets you write rich text posts about your product. It requires you to do more writing, but the upside is that you can nicely summarise a bunch of different changes in one cohesive story.
That feature needs a lot of work though. It's not very discoverable to begin with, and when you publish a post it doesn't get much attention on the site.
What do you think of this solution? Being able to write a short post, optionally linking to certain todos.
Yes, it can be the solution, and I like the idea to have more work to do when you want to highlight something 👍
I think that:
1. it should be displayed on the timeline (don't know if it's the case today)
2. it should probably "count" as a done task for the author
It currently isn't displayed on the timeline. It totally should though!
Right now it doesn't count as a done todo either. I guess we could make it count for the streak, as writing a status update is indeed work. And having to create a todo "Wrote a product update" just after you wrote it on WIP seems like unnecessary work.
An option to see the timeline by events without grouping by user
I was just discussing this with @levelsio the other day.
Would you like it as an option or the default? I'm considering making it the default. So you see each todo individually ordered by date. Similar to how Twitter works.
I start to know individuals and their habits, to I pretty like the current view, but if you can keep the two views, yes, it can make sense to switch to the ungrouped view by default 👍
Or to keep WIP simple, maybe you can use the per-event view by default, and the grouped-by-user one only for people you follow?wip
So the nice thing about grouped-by-user is that you get the full context of what someone is working on today. One todo by itself might not always be meaningful, but by seeing the other things that person worked on today you get a good sense of what they are doing.
On the other hand, the downside is that every time someone posts a new todo it bumps up their whole list of that day. So as a viewer you start seeing the same content and you're not sure if there's anything you haven't seen it yet further down the page.
Perhaps there's an alternative solution possible. For example only showing the new todos (grouped per user), with the todos you've already seen hidden by a "See 4 more todos…" button. Although that would require us to start tracking which todos you've already seen. Or least a timestamp of when you last viewed the homepage. (anything created after that would be considered unseen).
Thank you for your answers 👏
To complete my initial question, from what I can see, you are naturally more talking about editing your own WIP timeline, what about the follow-up of what happens in the community?
@wilbertliu I don't use WIP with Trello yet, but that's my ultimate goal :)
The majority of community interaction still happens in the chat. But me and @Jankeesvw are actively developing the website to facilitate it here as well.
The chat is great, but can be distracting and sometimes hard to follow. The website allows us for deeper interactions like this Q&A.
It seems like the notification system already works well to notify you when something relevant to you happened. So you post a question, someone answers. You get a notification email. That prompts you to check out their answer and perhaps reply to it. Which then sends them a notification email, etc.
That works well, because you already check your email inbox multiple times per day. And the emails are (hopefully) always relevant because they pertain to you personally and are actionable (e.g. we don't email you when someone likes your comment, because that's nothing you can act on)
But there's still the issue of getting people to the website in the first place. To post that question here. And to see what other people are up to.
For that we're experimenting with a weekly community digest sent via email. And also making the homepage more interesting to you by letting you follow specific individuals rather than every single WIP member.
We still have a long way to go though. Any suggestions are more than welcome.
To keep the interface light but allow more customization, maybe we can try having something like this that affects CSS: www.conventionalcommits.org/e…
Basically, if you type
[bugfix] the normal human-readable text, WIP knows that it's a bugfix and can update the CSS, it can also be cool to have some stats about the task kindsI really like that! I've been toying with the idea of adding support for regular hashtags. I think it could open up a bunch of possibilities. For example grouping all #marketing tasks together. Or indeed #bugfix'es etc.
The reason I haven't implemented it just yet, is because it might get confusing having both regular hashtags and product hashtags.
I agree that hashtags would be better, maybe you can just reserve some keywords that can't be used as project hashtags?
We can allow any hashtag and just prioritize product hashtags. So if you tag something #bugfix it will first check if you have a product with that hashtag. If so, it will link to your product. If not, it will be a regular hashtag.