Academic makes it easy to create a beautiful website for free using Markdown, Jupyter, or RStudio. Customize anything on your site with widgets, themes, and language packs. Check out the latest demo of what you'll get in less than 10 minutes, or view the showcase.
Academic Kickstart provides a minimal template to kickstart your new website.
- Get Started
- View the documentation
- Ask a question
- Request a feature or report a bug
- Updating? View the Update Guide and Release Notes
- Support development of Academic:
You can choose from one of the following four methods to install:
- one-click install using your web browser (recommended)
- install on your computer using Git with the Command Prompt/Terminal app
- install on your computer by downloading the ZIP files
- install on your computer with RStudio
Then personalize your new site.
- Academic Admin: An admin tool to import publications from BibTeX or import assets for an offline site
- Academic Scripts: Scripts to help migrate content to new versions of Academic
Copyright 2017-present George Cushen.
Released under the MIT license.
- GitHub organization with all case study repositories: https://github.com/opencasestudies.
Note that the DT search table is hosted at this URL (http://www.opencasestudies.org/OCS_search/) from a separate repo: https://github.com/opencasestudies/OCS_search
The html code used is located within the layouts/shortcodes directory and added to the markdown files within the content/home/ directory using {{<>}} labels. The config/_default directory has the files for the overall layout of the site. Use hugo server to preview what the website looks like before pushing to the repo. Follow this by hugo to generate any additional files to be added to the public directory. The public directory is a submodule that points to a different repo that the final changes to the website are pushed to if you commit and push changes to that directory. That repo lives at: https://github.com/opencasestudies/opencasestudies.github.io. If you have challenges look at the hugo documentation for any updates. This is typically why things may not be working as expected.