Conda's Prefixes Blogpost #148
Conversation
kenodegard
force-pushed
the
prefixes-blogpost
branch
from
868dcea
to
2dca51b
Compare
✅ Deploy Preview for conda-dot-org ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
kenodegard
force-pushed
the
prefixes-blogpost
branch
from
e4b78d0
to
4c34468
Compare
kenodegard
force-pushed
the
prefixes-blogpost
branch
from
4c34468
to
b291bce
Compare
Co-authored-by: Katherine Kinnaman <[email protected]>
kenodegard
force-pushed
the
prefixes-blogpost
branch
4 times, most recently
from
2cca534
to
f918411
Compare
kenodegard
force-pushed
the
prefixes-blogpost
branch
7 times, most recently
from
031f498
to
345bbf5
Compare
kenodegard
force-pushed
the
prefixes-blogpost
branch
from
345bbf5
to
b0f769d
Compare
Co-authored-by: Katherine Kinnaman <[email protected]>
| "@docusaurus/core": "^3.3.2", | ||
| "@docusaurus/plugin-ideal-image": "^3.3.2", | ||
| "@docusaurus/preset-classic": "^3.3.2", |
There was a problem hiding this comment.
Bumped to docusaurus>3.2.0 to benefit from facebook/docusaurus#9581 which allows for local author images.
|
One more thought, the list kind of disappears with all the other stuff on the page. What if each list item was an H2 header or something? |
Co-authored-by: Bianca Henderson <[email protected]>
|
@kathatherine I've switched it to use |
blog/2024-05-14-prefixes.mdx
Outdated
There was a problem hiding this comment.
Does it need to be mdx? I don't see any JSX in this post.
There was a problem hiding this comment.
It looks like only 3 of our prior posts need JSX (imports for images, which I suspect isn't necessary)
I've just been sticking to a standard format 🤷🏼♂️
Is there a downside to using mdx even if we don't use JSX?
There was a problem hiding this comment.
This is great @kenodegard! Thanks for writing it. A few suggestions.
Co-authored-by: Paul Yim <[email protected]>
Description
A blogpost discussing the recent research into the various conda prefixes (conda/conda#12704).