Ideas for blog content

[UlisesGascon]

As we will have a blog soon :partying_face: (see: expressjs.com #1483), it's time to start thinking about the content.

Here are some ideas about recent events that might be good candidates for blog posts:

• [ ] Blog entry about how to make a blog entry in the expressjs.com blog (lead by @crandmck)
• [ ] Blog entry about adopting the OSSF Scorecard in the organization (lead by @inigomarquinez )
• [ ] Blog entry for Express 5.0 (inspiration1, inspiration2)
• [ ] Blog entry about the last security releases, see: GHSA-rv95-896h-c2vc (inspiration)
• [ ] Blog entry about the Express Forward initiative (see: expressjs/discussions #160) (lead by @import-brain )
• [ ] Blog entry about the new Security Working Group (see: expressjs/discussions #165)
• [ ] Blog entry about the Revive the Triage Team (see: expressjs/discussions #227) (lead by @CBID2 )

If you are interested in working on these items, please let us know. Also, feel free to suggest more topics and ideas (cc: @expressjs/express-tc @expressjs/triagers).

[CBID2]

I'll do an entry about the triage team revival @UlisesGascon

[import-brain]

As we will have a blog soon 🥳 (see: expressjs.com #1483), it's time to start thinking about the content.

Here are some ideas about recent events that might be good candidates for blog posts:

• [ ] Blog entry for Express 5.0 (inspiration1, inspiration2)
• [ ] Blog entry about the last security releases, see: GHSA-rv95-896h-c2vc (inspiration)
• [ ] Blog entry about the Express Forward initiative (see: expressjs/discussions #160)
• [ ] Blog entry about the new Security Working Group (see: expressjs/discussions #165)
• [ ] Blog entry about the Revive the Triage Team (see: expressjs/discussions #227)

If you are interested in working on these items, please let us know. Also, feel free to suggest more topics and ideas (cc: @expressjs/express-tc @expressjs/triagers).

I can take the Express Forward initiative article.

[UlisesGascon]

Fantastic! Thanks for your support @CBID2 and @import-brain. I will add you a leaders for those blog entries :heart:

Please let me know if you have any question (feel free to DM me in Slack or put a comment in #express-triage-team). As the blog structure is not yet ready, my suggestion is try to use a markdown format, so later on it will easy to integrate :+1:

[crandmck]

Thanks for kicking this off, @UlisesGascon ... These are all excellent suggestions for posts!

My suggestion is super boring, and could come in with the PR (when it's ready) to add the blog capability itself, and that's a very short post that explains HOW to write a blog post... So meta ;-) Even though it will be pretty simple, it would still be good to have it all laid for contributors ...

[UlisesGascon]

I think that is a brilliant idea @crandmck! I added it to the list in bold, let see who wants to lead it :+1:

[crandmck]

I would like to take the lead on the first item--and after thinking about it, I suggest that it be slightly broader in scope and be something like "Welcome to the Express blog" and just a quick summary of relevant discussion at the last TC meeting:

• The initial purpose of the blog will be primarily a communication channel for the TC to the rest of the community.
• We will also consider posts on select topics nominated by the TC (e.g. as noted above in this issue) to communicate important information of interest to the Express community.
• In the future, we may open up the blog to more general (unsolicited) community contributions when we have the bandwidth to review them. Right now, our focus is on on releasing 5.x, fixing errors in and improving the existing docs, and generally attending to deferred maintenance on the project.
• Simple instructions to write a post: where files go, naming conventions, formatting, etc.