You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What did we have to figure out ourselves, and how can we help people not having to figure it out themselves in the future, i.e. by adding sections about certain mechanisms in JSServe to their docs.
I, for one do not really enjoy reading long examples in plain julia files or notebooks, since there is always some overhead to either running or displaying them. All the examples in the jsserve folder are really great and very helpful, but I think the docs would gain a lot from having them included as a page.
Additionally, I always feel a lot safer when I have at least a broad understanding of how a library works under the hood. So maybe after figuring this here out, we (or I) could build a short "technical introduction" with a bunch of diagrams and stuff, detailing how things work, what part of the library does what, which keywords to look out for and so on. Just to alleviate the struggle of having to infer the broader ideas and connections from the code alone.
The text was updated successfully, but these errors were encountered:
What did we have to figure out ourselves, and how can we help people not having to figure it out themselves in the future, i.e. by adding sections about certain mechanisms in JSServe to their docs.
I, for one do not really enjoy reading long examples in plain julia files or notebooks, since there is always some overhead to either running or displaying them. All the examples in the jsserve folder are really great and very helpful, but I think the docs would gain a lot from having them included as a page.
Additionally, I always feel a lot safer when I have at least a broad understanding of how a library works under the hood. So maybe after figuring this here out, we (or I) could build a short "technical introduction" with a bunch of diagrams and stuff, detailing how things work, what part of the library does what, which keywords to look out for and so on. Just to alleviate the struggle of having to infer the broader ideas and connections from the code alone.
The text was updated successfully, but these errors were encountered: