As you may be aware of, Pluto.jl doesn’t support themes (yet?). I’ve been using in-browser user CSS to modify certain aspects of Pluto styling for a long time. However, it becomes less convenient and practical when switching between multiple computers, and user CSS are not even supported in some mobile browsers. This package allows overriding Pluto styles on the server side, independent of the browser.
I don’t intend to register PlutoStyles.jl in General, so feel free to add it by URL.
Default styles that fit my taste are provided, most notably (i) occupy full window width, and (ii) allow large image sizes in collections. Arbitrary custom overrides are possible, see README at
Originally, I thought of the intended PlutoStyles audience as those who already know what CSS changes they want, and just need a convenient way to apply these modifications. Then the explanations given in README should be enough.
Maybe there are other potential users indeed, who have preferences similar to mine, and would like to use PlutoStyles defaults. In this case, see some comparison screenshots below!
Another piece of CSS is applied to the index Pluto page. It shows full paths for notebooks, and colors notebooks in the default /pluto_notebooks/ directory:
The built-in Pkg manager requires that the package is registered in a Registry.
This needs not to be the official General registry, a private Registry also works if you add it to Julia before starting Pluto (see 🎁 Package management · fonsp/Pluto.jl Wiki · GitHub).
I assume you are talking about Pluto built-in package manager? Because Julia built-in Pkg installs it just fine with ]add <url>.
PlutoStyles is not to be imported within notebooks! And shouldn’t be installed via Pluto.
This is the whole point: notebooks stay unmodified and without extra dependencies.
Just follow README: install PlutoStyles, and do
I like the wideness of PlutoStyles. No longer does so much of the space get wasted. It’s maybe a bit too wide as some of Pluto’s elements get underneath the scroll bar on a mac, sometimes.
IMHO, the three buttons that open from ‘…’ would be better inside the box, in place of the ‘…’.
This would save one mouse click, and would also solve this problem.
Nice idea for this CLI wrapper! Going to borrow it (:
I typically use Pluto in two different ways: a permanently-running instance on a remote server, and also start a local instance from time to time. Your wrapper conveniently covers both cases.
Yes, the popup menu is indeed beyond the screen edge on all systems. I tried to make it popup to the left of the “…” button, but didn’t succeed in it - maybe someone with a better CSS knowledge helps. Or it gets changed in Pluto itself as you say…
You can use the same CSS that is being used in Pluto if the screen width is too small, which you can find here:
Here is that in action in a pluto notebook where I put the CSS from PlutoStyles in the first cell and the snippet from editor.css (without @media as you want it active all the time) in the second cell
Interesting, you don’t seem to have these cell footers at all for inactive cells! I see them all the time, in plain vanilla Pluto, on all browsers and devices.
I think @aplavin meant unfocused or something along that line with “inactive”.
Are you instead referring to the disable feature you did introduce recently?
If you look at the latest screenshot from him none of the cells seem disabled but is abyway strange that all cella show the footer even if they are not focused or containing unsaved code