For performance, it's usually recommended to render CSS in HTML head and JS in the foot of the page. That way only the CSS loading needs to happen before rendering the page, and the JS can execute once it is visible. (Assuming the page doesn't need the JS to complete to generate content).
Markitup's inline JS requires both jQuery and markitup to be loaded above the widget, in the page.
I would suggest rather having data attributes inline, and adding a single script to the widget's media that consumes these configures the widget.
For performance, it's usually recommended to render CSS in HTML head and JS in the foot of the page. That way only the CSS loading needs to happen before rendering the page, and the JS can execute once it is visible. (Assuming the page doesn't need the JS to complete to generate content).
Markitup's inline JS requires both jQuery and markitup to be loaded above the widget, in the page.
I would suggest rather having data attributes inline, and adding a single script to the widget's media that consumes these configures the widget.