[BLOG] Add uarray-intro

[MarsBarLee]

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 (UTC)
consulting	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 10:55am
labs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 17, 2025 10:55am

[MarsBarLee]

@gabalafou I'm getting the Vercel build error: error [Error: [next-mdx-remote] error compiling MDX:

Full error message:

Unexpected character `'` (U+0027) after name,
expected a character that can start an attribute name,
such as a letter, `$`, or `_`; whitespace before attributes;
or the end of the tag

  270 |
> 271 |     <class 'int'>
      |            ^
  272 |     <class 'str'>
  273 |

Link to error

The context is showing the result of some code. Link to this section in the old blog website.

Maybe we could wrap it in a code block? But then it would look out of place with the rest of the code results, unless the rest were also in a code block.

[gabalafou]

Ugh that is formatted so ugly on the old site. If I understand correctly, and as I think you're saying, on this blog post on the old website, the blocks with gray background are meant to represent the code blocks, whereas the monospace-font lines (with no background color) that immediately follow are meant to represent the output from running those code blocks. But the way that is shown visually in the old blog post isn't intuitive to me at all. Let me play with this a bit and get back to you. Thanks for providing the link to the old blog post, by the way, super helpful!

[MarsBarLee]

Thanks for taking a look at it! And yes, I understood the blog the same way, code and then result. Maybe both could be in code blocks, but have different color backgrounds or text, to emphasize the difference?

[gabalafou]

@pavithraes, I think this is good to go.

I redid the commit history so that I could change the base branch to main.

Once my latest push has successfully deployed, you can take a look at the preview build of the blog post at the following URL: https://labs-git-uarray-intro-quansight.vercel.app/blog/uarray-intro

If this all looks good, then we will be able to apply the notebook code cell syntax demonstrated in this blog post to the backlog of unmigrated blog posts. The syntax looks like this:

<CH.Code className="labs-blog-cell-in-out">

```python in
print("hello world")
```

---

```txt out
hello world
```

</CH.Code>

[gabalafou]

I decided that we should stop duplicating these generic blog post images for each blog post and instead point the blog post metadata to a single image path shared across blog posts (we'll need to update these later).

[gabalafou]

see:

• [BUG] - Copy-pasted featured images #668