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
Add stupid-proof setup instructions #357
Comments
I think that development files and to be published files (which are necessary to run the slides) should be divided into different folders, that way it will be more intuitive. It should be done easily as part of the build process. |
I think there should be a downloadable template package which can be used especially by non git users. I am a git user but did not expect having to clone the repository to get the template for my presentation. |
The downloads section is good for this, IMHO. Maybe a download of only what one needs to get started? |
Right, the download section is good for this, but as a non git or github user I'd prefer a download package consisting only of the minimal file setup. |
GH actually dropped the static file uploads/downloads a while ago. I have some ideas for how to improve on this involving a long overdue dedicated site and domain for the project. There's a lot going on right now though so will take me a while to get to. |
I don't think people having to fork/clone/download the repo is a big deal - just that it could be pointed out more explicitly that "you'll be making all of your changes in |
Bought revealjs.com – the plan is to build a page there with better setup instructions and migrate the demo from lab.hakim.se/reveal-js. For now it's just a GH page. |
Still hoping to build out revealjs.com sometime – but in the meantime I've added installation instructions to the readme. They're linked from the top so hopefully easy enough to find: https://github.com/hakimel/reveal.js#installation |
Should be as straightforward as
index.html
or whatever your recommended way of doing it is. Wasn't immediately obvious to me that this repo is a deck itself, rather than just the development repo with a special download or setup step.
The text was updated successfully, but these errors were encountered: