Highlight release/important posts

[sirinoks]

There are many posts on Telescope, but some are more important than the others. I always want to read posts that summarise releases for example, but I might miss them amongst the other ones.

What if we had some posts highlighted in a specific way to stand out, or had them pinned to always come first, or perhaps had a separate tab with them alltogether? Posts that summarise releases, have information for new students, talk about planning.. You know, those.

Ways to implement

As mentioned, I see so far three ways to make this work:

• Highlight with a different color, so you don't miss it when you scroll
• Pin the latest release post to the very top, so there will be always one with latest infromation
• A separate tab, which might discourage students reading other people's posts, as they will default to only reading that single category

What posts to highlight? Here are some ideas:

• Release
• Planning
• Overview of sorts
• Guides
• Posts from current sheriffs

[cindyorangis]

There are many posts on Telescope, but some are more important than the others.

sarcasm start
Obviously, all my blogs are very important so I want mine to be featured on the front page with "ANNOUNCEMENT" tag with cute flags and colours

sarcasm end

I always want to read posts that summarise releases

Same. While Releases exist, I don't really read them because commit messages aren't that great at telling you the whole story. I want highlights/summaries of each release but who will write them for me? I just want one blog post or one video per Release that tells me everything that went down... woe is me... Alternatively, we can also stick these Release Notes in the Docusaurus site as well.

have information for new students

flashback start
"@humphd! Help me find an issue I can work on."
Dave grumbles as he tries his best to direct Student to the labeled buckets of issues and hopefully, they can find their way because he didn't sign up to be a matchmaker.
flashback end

The new Docusaurus site should be able to help them get set up and everything but there will always be the age-old problem of them asking which issue to start working on...

talk about planning

This is an interesting one because we can have things like Discussions, Milestones, Slack, Project Boards, etc etc. I feel like this should satisfy the requirement of "planning" or are you suggesting something slightly different like some kind of "Roadmap" visual that tells us what we're building towards?

Guides

I love guides, this should be a thing.

Posts from current sheriffs

This is probably just a temporary thing because sheriffs only exist from Jan - Apr of every year.

[sirinoks]

flashback

I actually thought of making a weekly/mounthly/something-ly list of issues, maybe in a video, or a blog post format which would do exactly that - recommend issues to people that are doable, while explaining more about them

This is an interesting one because we can have things like Discussions, Milestones, Slack, Project Boards, etc etc. I feel like this should satisfy the requirement of "planning" or are you suggesting something slightly different like some kind of "Roadmap" visual that tells us what we're building towards?

I mean, the things that are talked about during planning meetings, or some content like
https://github.com/Seneca-CDOT/telescope/wiki/Release-2.6-Planning
https://github.com/Seneca-CDOT/telescope/wiki/Telescope-3.0-Priorities
https://blog.humphd.org/toward-telescope-3-0/

I know there's more, but I can't find it CAUSE IT'S NOT HIGHLIGHTED ANYWHERE . But yes, I mean posts of a general news/overview type

Guides

There was a point where I was exploring Supabase and turned out someone made a useful post on it already, there was just no way to know unless you read every post, or you get it recommended by someone who read it.

[cindyorangis]

I want highlights like this https://blog.humphd.org/telescope-2-6-1/

[sirinoks]

There was some talk during triage about making a separate Telescope blog which perhaps could be done by sheriffs, or (what I like more) written collectively. So that would be the third option of implementation,

A separate tab, which might discourage students reading other people's posts, as they will default to only reading that single category

Example is the Supabase developer blog

There were also tags mentioned that we could use for highlighting.

In the end, this requires more discussion and will be addressed on Tuesday during Planning meeting.

[humphd]

I would suggest one of two ways that we could approach this. Let's create a "Telescope Developer" blog, using either:

• in our next.js app
• our Docusaurus app

Then we add the RSS feed for this blog to Telescope.

The advantage of putting this in the next.js app is that we could include a "Blog" link at the top (e.g., feature it). The advantage of the Docusaurus app is that it's pretty much already done (less to build).

I think having the Sheriffs write the post about the release each time we ship would be great.

[tpmai22]

@sirinoks are you interesting in taking this issue ?