academicpages / academicpages.github.io

Academic Pages **Academic Pages is a GitHub Pages template for personal and professional portfolio-oriented websites.** Getting Started • Register a GitHub account if you don't have one and confirm your e-mail (required!) • Click the "Use this template" button in the top right. • On the "New repository" page, enter your public repository name as "[your GitHub username].github.io", which will also be your website's URL. • Edit site-wide configuration in and double check that the is the one that you just selected in the previous step and that reflects the correct path for your repository. • Add your site content, upload any files (like PDFs, .zip files, etc.) to the directory. They will appear at https://[your GitHub username].github.io/files/example.pdf. • Check status by going to the repository settings, in the "GitHub pages" section • (Optional) Use the Jupyter notebooks or python scripts in the folder to generate markdown files for publications and talks from a TSV file. See more info at https://academicpages.github.io/ Additional Tutorials Additional tutorials for working with the Academic Pages template can be found at the following sites: • https://jayrobwilliams.com/posts/2020/06/academic-website/ Running locally When you are initially working on your website, it is very useful to be able to preview the changes locally before pushing them to GitHub. To work locally you will need to: • Clone the repository and made updates as detailed above. Using a different IDE • Make sure you have ruby-dev, bundler, and nodejs installed On most Linux distribution and Windows Subsystem Linux the command is: If you see error , , run the following: then try run again. On MacOS the commands are: • Run to install ruby dependencies. If you get errors, delete Gemfile.lock and try again. If you see file permission error like or Install Gems Locally (Recommended): then try run again. If succeeded, you should see a folder called and . • Run to generate the HTML and serve it from the local server will automatically rebuild and refresh the pages on change to Markdown (*.md) and HTML files, while changes to the core template and configuration (i.e., ) will require stopping and restarting Jekyll. You may also try to ensure jekyll to use specific dependencies on your own local machine. If you are running on Linux it may be necessary to install some additional dependencies prior to being able to run locally: Using Docker Working from a different OS, or just want to avoid installing dependencies? You can use the provided to build a container that will run the site for you if you have Docker installed. You can build and execute the container by running the following command in the repository: You should now be able to access the website from . Using the DevContainer in VS Code If you are using Visual Studio Code you can use the Dev Container that comes with this Repository. Normally VS Code detects that a development container configuration is available and asks you if you want to use the container. If this doesn't happen you can manually start the container by **F1->DevContainer: Reopen in Container**. This restarts your VS Code in the container and automatically hosts your academic page locally on http://localhost:4000. All changes will be updated live to that page after a few seconds. Maintenance Bug reports and feature requests to the template should be submitted via GitHub. For questions concerning how to style the template, please feel free to start a new discussion on GitHub. This repository was forked (then detached) by Stuart Geiger from the Minimal Mistakes Jekyll Theme, which is © 2016 Michael Rose and released under the MIT License (see LICENSE.md). It is currently being maintained by Robert Zupko and additional maintainers would be welcomed. Bugfixes and enhancements If you have bugfixes and enhancements that you would like to submit as a pull request, you will need to fork this repository as opposed to using it as a template. This will also allow you to synchronize your copy of template to your fork as well. Unfortunately, one logistical issue with a template theme like Academic Pages that makes it a little tricky to get bug fixes and updates to the core theme. If you use this template and customize it, you will probably get merge conflicts if you attempt to synchronize, although rebasing the changes from this template will work along with manually cherry picking the relevant commits. If you are not comfortable with the Git command line, you can save your various configuration files and Markdown files, delete the repository, and fork it again. ---