🍪☀️ PlutoUI Roadmap ☀️🍪

[pankgeorg]

New features enabled by AbstractPlutoDingetjes.jl (ConcretePlutoDigetjes.jl)

• WebCamInput -> returns Array{T wherer T<:ColorType, 2}
• MicrophoneInput -> returns audio (save audio?) (see JuliaMusic?)
• TableInput -> returns dataframe
• Scrubbable matrix -> returns matrix
• Nice FileInput -> return IO ?? String?? url of file uploaded (somewhere?) ??
• Images with labels (and some metadata for backrefing from Books.jl?)
  • create bibliography (βιβλιογραφία)
  • reference (julia objects), captions for images, captions for tables

New outputs

(use the <output> html5 element)

• Number output (fix typography, layout)
• "Dashboard-like" primitive outputs (statistic like)
  • Localization, "type", color, "percent", icon, label, transition using this (old clock like)
  • More visual styles for combinations of (text, number)
• Boolean values (check ✅/❌icon)?
• Sparklines/data bars? 1em high
• DateTime output

Add HTML 5 features to PlutoUI.*

• <label>
• :disabled
• <form>
• <fieldset>
• <output>

Documentation website:

• Pluto notebook sourcecode should be our documentation!

Accessibility

Let's carefully read the docs and improve accessibility on Pluto notebooks!

[stillyslalom]

Re: "Pluto notebook sourcecode should be our documentation!"

It's a great idea to have an example/tutorial notebook like this one, but good documentation also requires a separate detailed reference for each function. Reference documentation should be somewhat pedantic and repetitive so that the user doesn't have to read the rest of the documentation to figure out the particulars of one function, and that makes for a really bulky notebook. Please consider retaining the Documenter.jl docs (which are... broken again?)