DEV Community

Ben Halpern for The DEV Team

Posted on

Changelog: Pin posts you want to feature to the top of your profile feed

If you go to my profile, you can see it in action:

ben image

DEV now allows you to pin up to five posts at the top of your profile feed, in case you want to show off your best writing to any visitors.

In order to pin a post, click on the Manage button on your posts and then click Pin to Profile. We will also probably add this to more quickly accessible area in the future.

Currently the five posts display chronologically but I think we could follow up with giving more control here. This is also a precursor to a possible design adjustment which would highlight your pins in a different format.

Happy coding!

Discussion (12)

Collapse
hamatti profile image
Juha-Matti Santala • Edited on

How do I pin posts, I couldn't find that anywhere on my profile nor on my dashboard?

edit I found it! I had to open a post, choose Manage and there it was!

Collapse
drewtownchi profile image
Drew Town

Thanks! It wasn't obvious to me either. It'd be nice to see this in the "..." menu on the dashboard.

Collapse
ben profile image
Ben Halpern Author

My bad. I didn't even include that in the post. Edited.

Collapse
hamatti profile image
Juha-Matti Santala

That's where I went to look first too!

Collapse
desi profile image
Desi

Yes! I've been waiting for this!

Collapse
ben profile image
Ben Halpern Author

Yay!

Collapse
laurieontech profile image
Laurie

This is awesome!

Collapse
lauragift21 profile image
Gift Egwuenu

Awesome feature!!

Collapse
ronsoak profile image
ronsoak

Could we add a filter to our dashboard to just see pinned posts?

Collapse
ben profile image
Ben Halpern Author

Good idea!

Collapse
citizen428 profile image
Michael Kohl • Edited on

Very nice new feature, Ben! BTW, sometimes the caching on the site seems to be a bit too aggressive, I had to fully reload my profile (⌘-⇧-R) for them to show up.

Collapse
ben profile image
Ben Halpern Author

Yeah, if I recall this might only trigger an async cache which is probably not right.

Aggressive caching is definitely where we over-optimize and just trying to get it to work right, you know those hard parts of computer programming 😄