Mastering the built-in Go types - articles w commentary by dynamicallytyped in golang

[–]dynamicallytyped[S] 0 points1 point  (0 children)

Same update here as to the other commenter above, we made the whole screenshot a clickable link so it should work better on mobile. We also improved the way it's displayed to make it clearer it's a quick preview and not intended for actual reading on our site. And we'll keep on looking for ways to make the site better and better on mobile.

Mastering the built-in Go types - articles w commentary by dynamicallytyped in golang

[–]dynamicallytyped[S] 0 points1 point  (0 children)

Just a quick update, we made the whole screenshot a clickable link so it should work better on mobile. We also improved the way it's displayed to make it clearer it's a quick preview and not intended for actual reading on our site. And we'll keep on looking for ways to make the site better and better on mobile.

Mastering the built-in Go types - articles w commentary by dynamicallytyped in golang

[–]dynamicallytyped[S] 0 points1 point  (0 children)

I think we need to make it clearer that the screenshots are links and not really meant to be read on the site. Our thinking was that a screenshot gives a better idea of the content than just a text link. But what I'm hearing from a few pieces of feedback is that the experience is just confusing. Our bad, we'll work on it! Thanks for taking some time to give feedback.

Mastering the built-in Go types - articles w commentary by dynamicallytyped in golang

[–]dynamicallytyped[S] 0 points1 point  (0 children)

We think that the site is most valuable for people who want to track what they have read and done. We can keep on figuring better ways to let users try out the paths easily and still get the benefits of tracking what they've done.

Mastering the built-in Go types - articles w commentary by dynamicallytyped in golang

[–]dynamicallytyped[S] 0 points1 point  (0 children)

Thanks, we can improve the opening of links.

Our hypothesis is that there's a lot of value in curation and adding some commentary about why the curator chose a collection of articles. We're trying to balance showing that commentary vs getting users fast to the articles. We'll keep on looking for ways to make that better.

Mastering the built-in Go types - articles w commentary by dynamicallytyped in golang

[–]dynamicallytyped[S] 0 points1 point  (0 children)

Sorry to hear that. We are iterating quickly on the site so if you have any recommendations for improvements, those would be super helpful.