jonocodes / pwder Goto Github PK

and add it to readme

When visiting :
https://pwder.io/gh/jonocodes/pwder/master/examples/nginx.md
I got an error message:

Failed to load https://labs.play-with-docker.com/: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://pwder.io' is therefore not allowed access. The response had HTTP status code 405.

Is it possible to use local dev environment(play-with-docker locally) rather than using https://labs.play-with-docker.com/?

I saw in screenshot.png you launched 2 terminals, are they from local dev environment?

Right now both the input and output blocks are grey. On PWD classroom this is not the case. It looks like the highlighter tag is not appearing on the output blocks.

Kind of like those CI banners that show in readme's on github. Or like the 'Try in PWD' link mentioned here: docker-library/docs#912

This would effectively launch the readme in pwder.io so you dont have to know how to cut and paste it in there. Discoverability. This way someone who finds the readme can run it.

We then might want to make sure that that image does not show when rendered.

It would be interesting to get this working entirely in browser instead of relying on a web service. I briefly tried to get strapdown and kramed to render GFM but it could use a little work.

Add 'view source' link on the bottom of pages. This would open a link to the raw readme (or the github rendered version?) in a new window.

If a line in an input block starts with '$ ', then '$ ' would get removed before executing it. This way the markdown can follow the Docker/Arch documentation guidelines a little closer. https://docs.docker.com/opensource/doc-style/#code-and-ui-text-styling

This could also be done with root commands which conventionally start with '# '.

Perhaps /gst/ would be good?

Figure out a way to keep up to date with upstream Jekyll theme better. Right the default theme file is generated by me viewing one of the rendered classroom documents. For example:
http://training.play-with-docker.com/helloworld/

I copy the HTML, then modify it to my needs. This means stripping out the header and footers, removing some scripts and DOM elements that are not needed. Then I add back some of the templating from
https://github.com/play-with-docker/play-with-docker.github.io/blob/master/_layouts/post.html

This is not efficient. There should either be a way of automating this, or at least a document that says exactly how to do this for future updates to the theme.

Additionally we should pull down copies of static assets like pwd.js and the css. Right now we are just referencing them from their original hosts, but since thats a moving target it is more brittle then having our own copy. We can host these right out of pwder by creating a route for static assets in Sinatra.

Right now the 'title' is rendered into the title tag and as an H1 at the page top.

The user might want to specify their own H1 and then not render the title into the H1.

Also useful for migrating over old readme's that have an H1.

Another option would be to scrape the first H1 in the page and use that in the title tag. Hmmm.