-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove use of plugins for Jekyll #3
Comments
So in other words, it should work exactly as it is working right now but it needs to be ported to (client side) JavaScript? I might look into this if I may. |
@ests basically yes =) |
And please do! |
Merged
Please see my proposal. I will make any changes that you'll require. Please note, that we still need to test it against different browsers. |
Opened #18 before reading this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am currently using a jekyll plugin to construct the links onto play. This prohibits us from doing the rendering directly in GitHub Pages. It'd be nice to solve this another way. One thought that I had was writing some JavaScript -- when you click on a link that should lead to play, it in fact runs some JS. This JS goes to fetch the Rust file from the server, applies the minimal transformations, and then redirects to the appropriate play URL (in another window, of course).
The text was updated successfully, but these errors were encountered: