playground:playground [Post-Platform Digital Publishing Toolkit]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<HTML>
<script>
    function fetch_request(url, callback){
        // fetching the pad
        fetch(`${url}`, {
            'method': 'GET',
            'mode': 'cors',
        })
        .then(response => response.text() )
        .then(css => inject_css(css) );
    }
    function inject_css(css){
        console.log('pad loaded!');
        let el = document.createElement('style');
        el.id = "etherstyle";
        el.innerText = css;
        document.head.appendChild(el);
    };
    fetch_request("/doku.php?id=stylesheet:style_playgound&do=export_text", inject_css);
</script>
</HTML>



====== PlayGround ======


Here's some text and i'm going to import some custom styling on this page only !

the way this would work is to 

* have a stylesheet namespace where we put the stylesheet page (so they become proper entry in the wiki, really publishing style!)

* use the plugin: https://www.dokuwiki.org/plugin:text ; this one allow to export a page as plain text by adding "&do=export_txt" to it's url , in our case the stylesheet

* use the plugin: https://www.dokuwiki.org/plugin:htmlok ; this one allow to have html tag inside each page, so we can use it to insert a "link" tag that links to the plain text version of the stylesheet

from MDN

//A <link> element can occur either in the <head> or <body> element, depending on whether it has a link type that is body-ok. For example, the stylesheet link type is body-ok, and therefore <link rel="stylesheet"> is permitted in the body. However, this isn't a good practice to follow; it makes more sense to separate your <link> elements from your body content, putting them in the <head>.
//

with a setup like that, publishing design and text are intertwined, stylesheets are part of the wiki as any page, bluring the line between what is form and what is content. moreover there isn't a 1 to 1 relationship between style and content: one page can use many stylesheet; or one stylesheet can be used many time. the content of the wiki can be written in continuous evolution, so it is the case for the design. this setup reject platform design as an authority, and can show how a same platform can hold many forms.