-
Sorry to ask this here and like this, but can you just fork this repo, rename it to |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments
-
You can, but I wouldn't advise that. Anytime the theme is updated you won't be able to easily merge those changes back in. If you're hosting on GitHub, follow those instructions in the README. You basically create a repo with a Best part you automatically get any theme updates this way too. If you're looking for a starter, take a look at the |
Beta Was this translation helpful? Give feedback.
-
I currently run a version here: https://github.com/Andre601/Andre601.github.io I currently face a minor issue where GitHub reports the following message each time I build the page:
I don't really have that big of interest to keep this updated as I just want to host a site with static and blog pages. |
Beta Was this translation helpful? Give feedback.
-
You need to install the theme following the GitHub compatible method. GitHub Pages only supports a few 1st party themes using the If you want to use this theme you need to set |
Beta Was this translation helpful? Give feedback.
-
Also if you want to go with a fork you'll need to remove all the junk. |
Beta Was this translation helpful? Give feedback.
-
Is it important where I post/upload files to in the repository? |
Beta Was this translation helpful? Give feedback.
-
Up to you how you manage that. As long as you use a valid path in your content shouldn't matter where you put them. I tend to put everything in [link to a file](/assets/your-file.pdf) <a href="/assets/your-file.pdf">link to a file</a> |
Beta Was this translation helpful? Give feedback.
-
I talk about the pages themself. |
Beta Was this translation helpful? Give feedback.
-
I suggest you start with Jekyll's documentation to get a feel for how to use it and follow how to create posts and files. This is a reason why I don't advise forking the repo. It's not setup in a way that makes it a good starter. It has extra folders and the demo/example sites aren't setup in the same way you'd do it in your own repo. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the information. |
Beta Was this translation helpful? Give feedback.
You can, but I wouldn't advise that. Anytime the theme is updated you won't be able to easily merge those changes back in.
If you're hosting on GitHub, follow those instructions in the README. You basically create a repo with a
_config.yml
file and your posts/pages and that's it. The layouts, includes, stylesheets, etc are pulled automatically by GitHub every time the site is built.Best part you automatically get any theme updates this way too.
If you're looking for a starter, take a look at the
/docs
folder. That's the source for the demo site and is built on GitHub Pages using the method I mentioned above. You could copy that folder, update_config.yml
to your liking, replace_posts
and…