It would be nice if you could expose these values in an editable text area that would allow users to modify the style sheet without having to make temporary changes to the code.

I exposed it as an option to exporter({ style: ... })

Ah, I meant in the context of this notebook. I.e. for those simply wishing to use this/your source and not fork or embed within a notebook.

yeah I want to keep this notebook lean and if someone wants to spend time customizing CSS they should probably do it in another notebook so they have the settings persisted and can iterate on them. Basically everything in this notebook gets replicated on every export so smaller is better.

Fair. Now that you resolved forking this is a non-issue (though I always prefer using a source notebook). Please feel welcome to close this thread.

It seems that I cannot fork this to my account and have it work? When I try this, the previews are blank.

I cannot repro this, I just tested on my alt and it worked for me even is a private notebook. Maybe refresh and try again?

the other way is import the exporter function and instanciate it, but forking should work too.

I just tried again and got the same issue. I am using a notebook URL. Tried both private fork and making this listed. Reference notebook is published unlisted. Attempted with two notebooks.

link?

is the notebook URL you are targeting public?

Yes. Here's a view of the error message when I hit download: https://observablehq.com/d/2eca9b0a203b713f I tried just now with https://observablehq.com/@ambassadors/noaa-urban-heat-island-mapping (and have tried others). Here's my forked version: https://observablehq.com/d/de30b581458f2082

Ahhh! Looks like unreferenced fileattachments are wiped after a fork. I have fixed it with https://observablehq.com/@tomlarkworthy/exporter#fileAttachmentKeepAlive so forking should work now. Thanks for letting me know!

Excellent 👌 Thank you! This is a fantastic tool!.