Open agoose77 opened 3 years ago
I think staying as close to well-understood, portable markdown as possible is a pretty big win. I don't see a ton of value to bringing in lots of additional syntax to remember, even if we've made it possible with jupyterlab-markup
, for things like links which already have tons of different representations. Consider some of the "extended" link forms:
[an example](http://example.com/ "Title")
This is about [foo]
[foo]: http://example.com/ (Optional Title Here)
It's not too far of a stretch to interpret explicit titles as a pun for the node in the graph which has this label (or maybe even a URI).
# Jupyter Clients
A Jupyter Client provides an interactive computing experience to a user by connecting to
a [Jupyter Server](./Jupyter+Server.ipynb "connects to").
## JupyterLab
JupyterLab is a [Jupyter Client](#Jupyter-Client "subclass of").
## JupyterLite
JupyterLite is a [JupyterLab](#JupyterLab "subclass of") as well as
a [Jupyter Server](./Jupyter+Server.ipynb "subclass of")
Which would render like:
Jupyter Clients
A Jupyter Client provides an interactive computing experience to a user by connecting to a Jupyter Server.
JupyterLab
JupyterLab is a Jupyter Client.
JupyterLite
JupyterLite is a JupyterLab as well as a Jupyter Server
Currently we only find conventional Markdown style links. In addition to supporting
[[wiki]]
style links (which would require https://github.com/agoose77/jupyterlab-markup/issues/34), are there other link styles we need to support?