Blogpost: The evolution of SciPy CLI

[sayantikabanik]

Text styling

• [X] The blog is written with plain language (where relevant).
• [X] If there are headers, they use the proper header tags in order to do so (with only one level-one header).
• [X] All links describe where they link to (for example, check the Quansight labs website).
• [X] Any kind of styling that the author uses (for example, bold for emphasis) is consistent throughout the blog.

Non-text contents

• [X] All content is represented as text (for example, images need alt text and videos need captions or descriptive transcripts).
• [X] If there are emojis, there are not more than three in a row.
• [X] Don't use flashing gifs or videos.
• [X] If it were to be read as plain text, the blog still makes sense and no information is missing.

[netlify[bot]]

✅ Deploy Preview for admiring-northcutt-a5be8c ready!

Name	Link
🔨 Latest commit	af981137539e6c95df11754007a00b19ddd818f6
🔍 Latest deploy log	https://app.netlify.com/sites/admiring-northcutt-a5be8c/deploys/627912b3e2023f00094df79a
😎 Deploy Preview	https://deploy-preview-322--admiring-northcutt-a5be8c.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[rgommers]

This looks pretty decent now. Let me ask for review from someone who doesn't know how the project happened to make sure the story is actually clear without that context. @noatamir would you be able to review this blog post?

[noatamir]

Happy to! by when -ish? 😇

[rgommers]

Thanks @noatamir. Not super urgent, but within the next week would be great - and then squash-merge if it all looks good. Or if you prefer I do the final check & merge, then by Friday (I'm on holiday from Sat onwards).

[noatamir]

I left some suggestions and comments. I'm about half way through and need to stop for today.

[noatamir]

continuing now 😊

[sayantikabanik]

Thanks a ton, @noatamir ✨ I shall make the required re-writes and commit the suggestions.

[sayantikabanik]

Thanks again @noatamir for the detailed feedback, I have updated the required sections of the blogpost.

[noatamir]

Let me know when you're ready to publish. Looks great to me!

[sayantikabanik]

Let me know when you're ready to publish. Looks great to me!

Super excited 💃🏽, about my first blog with Quansight. Do I need to follow any additional steps for the deployment to though successfully?

[noatamir]

It's my first time squash-merging on the blog so we will both find out together 😄 All the checks are green so I think it should be fine 👍 I will do this a bit later when I have more time I need to prepare for a meeting.

[rgommers]

Yay, nice post 🎉!

@noatamir I'm not sure how, but something didn't go quite right here: you managed to do both a squash-merge (in commit 4177e2c1b2) and a regular merge of the branch after that (in commit 3ee0fa70). The normal way of doing this is to select "Squash and merge" for the green button, hit that, and then do nothing else.

There's no other commits on top yet, so I think I'll fix up the history by resetting main to commit 4177e2c1b2, to get rid of the 29 extra commits.