[BLOG] Add whats-new-in-sympy-14

[MarsBarLee]

Link to blog post, successful build.

Links to other Quansight blogs:

There is no need to check for Blog2Blog links due to updated website build.

Text styling

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

Non-text contents

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

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
consulting	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 20, 2023 at 6:52PM (UTC)
labs	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 20, 2023 at 6:52PM (UTC)

[MarsBarLee]

@gabalafou The Vercel build error shows a prerendering error and ReferenceError:

Error occurred prerendering page "/blog/whats-new-in-sympy-14". Read more: https://nextjs.org/docs/messages/prerender-error
ReferenceError: n is not defined
at _createMdxContent (eval at <anonymous> (file:///vercel/path0/node_modules/next-mdx-remote/dist/index.js:55:35), <anonymous>:815:47)
at MDXContent (eval at <anonymous> (file:///vercel/path0/node_modules/next-mdx-remote/dist/index.js:55:35), <anonymous>:974:9)
...

(Link to Vercel build error)

I think this error is related to the math used in the blog post. Maybe due to the <math> tag or pycon in the code blocks?

[gabalafou]

Hey @MarsBarLee, I pushed a commit to this branch that I think fixes the build issues. If it builds this time, can you double check the post? If it looks good on your end, I can go ahead and approve and squash-merge this PR into develop.

[noatamir]

LGTM

[gabalafou]

@noatamir since it looks good to you, I'm going to go ahead and merge this is in.