conda-forge
Update glossary
PR Checklist:
- [x] note any issues closed by this PR with closing keywords
- [x] if you are adding a new page under
docs/orcommunity/, you have added it to the sidebar in the corresponding_sidebar.jsonfile - [x] put any other relevant information below
This PR is a minor update to the glossary, with style homogenization and a new entry for CDN.
Deploy Preview for conda-forge-previews ready!
| Name | Link |
|---|---|
| Latest commit | 2c11387d57d26492913a0e22e6a288daa2a2bc1e |
| Latest deploy log | https://app.netlify.com/sites/conda-forge-previews/deploys/665601e86eebd40008746168 |
| Deploy Preview | https://deploy-preview-2184--conda-forge-previews.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 configuration.
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
The <a id ... anchors were there to re-export the old anchors from the old website, but we don't need to follow that format everywhere. Actually I lean towards moving away from the #term- prefix if possible (and only keep the old ones around for backwards compatibility with external sites linking to us, while using the new ones internally).
The
<a id ...anchors were there to re-export the old anchors from the old website, but we don't need to follow that format everywhere. Actually I lean towards moving away from the#term-prefix if possible (and only keep the old ones around for backwards compatibility with external sites linking to us, while using the new ones internally).
Makes sense to me. That means keeping the <a ... tags, but removing the {#term-...} tags and updating all links within the repo that refer to glossary[.md]#term- to remove the term- part, correct?
sigh link checker failure due to ci network problems. @conda-forge-admin, please restart ci
I don't think that works in this repo (but you can always close and reopen on your own). I issued a CI rerun, let's see.