-
\ No newline at end of file
diff --git a/henry/_layouts/tag.html b/henry/_layouts/tag.html
deleted file mode 100644
index 7e45fda..0000000
--- a/henry/_layouts/tag.html
+++ /dev/null
@@ -1,13 +0,0 @@
----
-layout: default
----
-
-
Posts With Tag: {{page.tag}}
-
-
- {% for post in site.posts %}
- {% if post.tags contains page.tag %}
- {% include components/post.html %}
- {% endif %}
- {% endfor %}
-
\ No newline at end of file
diff --git a/henry/_pages/about.html b/henry/_pages/about.html
deleted file mode 100644
index ac9021b..0000000
--- a/henry/_pages/about.html
+++ /dev/null
@@ -1,25 +0,0 @@
----
-layout: default
-title: About
-order: 2
-customPage: true
-permalink: /about/
----
-
-
-
-
-
-
-
-
-
-
-
-
-
Hello, I'm {{site.title}}!
-
I'm a London-based front-end web developer with over ten years of experience. I design and build beautiful, responsive websites.
-
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
-
The Old High German name is recorded from the 8th century, in the variants Haimirich, Haimerich, Heimerich, Hemirih. Harry, its English short form, was considered the "spoken form" of Henry in medieval England. Most English kings named Henry were called Harry. The name became so popular in England that the phrase "Tom, Dick, and Harry" began to be used to refer to men in general. The common English feminine forms of the name are Harriet and Henrietta.
-
\ No newline at end of file
diff --git a/henry/_pages/work.html b/henry/_pages/work.html
deleted file mode 100644
index 03d2142..0000000
--- a/henry/_pages/work.html
+++ /dev/null
@@ -1,20 +0,0 @@
----
-layout: default
-title: Work
-order: 1
-customPage: true
-permalink: /work/
----
-
-
-
- {% assign sortedProjects = site.projects | sort: 'creationDate' | reverse %}
- {% for project in sortedProjects %}
-
- {% endfor %}
-
-
\ No newline at end of file
diff --git a/henry/_posts/2021-01-13-sample-data.md b/henry/_posts/2021-01-13-sample-data.md
deleted file mode 100644
index 0829f95..0000000
--- a/henry/_posts/2021-01-13-sample-data.md
+++ /dev/null
@@ -1,127 +0,0 @@
----
-title: "Sample Data"
-categories: docs
-tags: jekyll demo documentation
----
-
-
-
-
-
-Markdown (or Textile), Liquid, HTML & CSS go in. Static sites come out ready for deployment.
-
-**Headings**
-
-# Heading 1
-
-## Heading 2
-
-### Heading 3
-
-#### Heading 4
-
-##### Heading 5
-
-###### Heading 6
-
-
-
-**Blockquote**
-
-> No more databases, comment moderation, or pesky updates to install—just your content.
-
-**Unordered List**
-
-* Jekyll
- * Nested Jekyll
- * Nested Ruby
-* Ruby
-* Markdown
-* Liquid
-
-**Ordered List**
-
-1. Jekyll
- 1. Nested Jekyll
- 2. Nested Ruby
-2. Ruby
-3. Markdown
-4. Liquid
-
-**Link**
-
-This is an example inline link.
-
-**Paragraph w/ strong, em, etc.**
-
-These are just a few of the *available* **configuration** options. Many configuration options can either be specified as flags on the command line, or alternatively (and more commonly) they can be specified in a _config.yml file at the root of the source directory. Jekyll will automatically use the options from this file when run. For example, if you place the following lines in your _config.yml file.
-
-**Image**
-
-
- From the movie Dunkirk.
-
-
-**Video**
-
-
-
-**Paragraphs w/ Aligned Images**
-
-The Jekyll gem makes a jekyll executable available to you in your Terminal window. You can use this command in a number of ways.
-
-
-
- From the movie Joker.
-
-
-This site aims to be a comprehensive guide to Jekyll. We’ll cover topics such as getting your site up and running, creating and managing your content, customizing the way your site works and looks, deploying to various environments, and give you some advice on participating in the future development of Jekyll itself.
-
-Jekyll is a simple, blog-aware, static site generator. It takes a template directory containing raw text files in various formats, runs it through a converter (like Markdown) and our Liquid renderer, and spits out a complete, ready-to-publish static website suitable for serving with your favorite web server. Jekyll also happens to be the engine behind GitHub Pages, which means you can use Jekyll to host your project’s page, blog, or website from GitHub's servers for free.
-
-
-
- From the movie Fight Club.
-
-
-Throughout this guide there are a number of small-but-handy pieces of information that can make using Jekyll easier, more interesting, and less hazardous. Here's what to look out for.
-
-If you come across anything along the way that we haven’t covered, or if you know of a tip you think others would find handy, please file an issue and we’ll see about including it in this guide.
-
-The front matter is where Jekyll starts to get really cool. Any file that contains a YAML front matter block will be processed by Jekyll as a special file. The front matter must be the first thing in the file and must take the form of valid YAML set between triple-dashed lines.
\ No newline at end of file
diff --git a/henry/_posts/2021-01-14-how-to-use-the-theme.md b/henry/_posts/2021-01-14-how-to-use-the-theme.md
deleted file mode 100644
index 244c8a2..0000000
--- a/henry/_posts/2021-01-14-how-to-use-the-theme.md
+++ /dev/null
@@ -1,188 +0,0 @@
----
-author: guest
-title: "How To Use"
-categories: docs jekyll
-tags: jekyll settings
----
-
-
-
-
-
-### Configuration
-All configuration options are in the _config.yml file. Let's take a look of the important ones.
-
-#### General
-* **title**: Site name.
-* **description**: Site description.
-
-#### Paths
-These options are pretty important, so take a closer look. If you experience any problems with your paths you should check here.
-
-* **url**: A lot of people have problems when they try to setup their paths. That's why I've decided to keep things as simple as possible. So, usually you'll have to paste here your domain https://mysite.com and then in the baseurl you paste your subdomain (if there is one). The theme is configured to use absolute paths, so you'll have to paste the whole path here — domain + subdomain. For example, if your website is in the root folder, write down https://mysite.com, if there is a subfolder — https://mysite.com/subfolder. In this case you don't need the baseurl anymore.
-* **baseurl**: No longer needed due theme configuration. I left it just in case.
-
-#### Options
-* **darkMode**: Enable/disable dark theme for the theme. If enabled you'll see an icon in the upper right corner.
-* **showTags**: Enable/disable visibility of post's tags.
-* **showCategories**: Enable/disable visibility of post's categories.
-* **showSearch**: Enable/disable visibility of global site search.
-* **showSharePost**: Enable/disable visibility of post's share options.
-* **showFavIcon**: Enable/disable visibility of favicon.
-* **showComments**: Enable/disable visibility of post's comments.
-* **showCookieBanner**: Enable/disable visibility of the cookie banner. This theme supports Google Analytics (GA), so there have to be some kind of user notification. If you don't use GA or other tracking service, you should disable it. Keep in mind that the banner is pretty basic, so in some cases you may need to customize it or entirely replace it with another third-party cookie service.
-* **useExternalContactForm**: Enable/disable usage of [Formspree](https://formspree.io/){:target="_blank"} as default contact form. If this option is disabled, when you click **Contact** link in the main menu you'll be redirected directly to your default mail client. If enabled, a modal box will pop up and you'll be introduced to a more user-friendly contact form.
-* **useAnalytics**: Enable/disable usage of Google Analytics.
-
-#### Third Party / Social
-* **facebook**: Link to your facebook page.
-* **twitter**: Link to your twitter page.
-* **instagram**: Link to your instagram page.
-* **email**: Your email address.
-* **formspree**: Link to your [Formspree](https://formspree.io/){:target="_blank"} form. If you use Formspree, generate form ID and paste it here. Works only if you activated useExternalContactForm option in the previos section.
-* **googleAnalyticsTrackingCode**: Add your Google Analytics Tracking ID. Example ID: *UA-XXXXXXX-2*.
-* **disqusID**: Add your website shortname from Disqus. Keep in mind that by default Disqus comments are not configured. If you use this make sure showComments option is set to **true**.
-* **twitterHandle**: Add your Twitter handle.
-
-
-
-#### Permalinks
-There is a default structure of your links. If you want a different one, please check [Jekyll documentation](https://jekyllrb.com/docs/permalinks/){:target="_blank"}.
-
-#### Pagination
-* **paginate**: Number of posts per page.
-* **paginate_path**: The default path is /blog/page:num/, so for example if you go to the second page you'll see something like this http://mysite.com/blog/page2/.
-
-**Important Note:** Due to theme's compatibility with GitHub Pages, pagination is only supported on the default posts/blog page — **Blog**. When you list categories or tags, there is no pagination.
-
-#### Includes
-* **include**: Force the inclusion of the pages directory.
-
-#### Post Separator
-* **excerpt_separator**: By default when you're writing a post, you should add <!--more--> to define the end of the excerpt. If you remove this option your excerpt will show with the default settings and you'll not have control over the content. If you want to keep the custom separator (I strongly suggest) you can leave it as is or change the <!--more--> tag as well.
-
-#### Assets Settings
-* **sass_dir**: Choose the path to your SCSS files.
-* **style**: Choose the compression method for the final CSS file.
-
-If you need extra help, just check out the [official Jekyll documentation](https://jekyllrb.com/docs/home/){:target="_blank"}.
-
-### How To Add a Post
-All you need to do is to add a file to your _posts directory with the following format: YEAR-MONTH-DAY-title.MARKUP. Where YEAR is a four-digit number, MONTH and DAY are both two-digit numbers, and MARKUP is the file extension representing the format used in the file. You can overwrite these in the post's front matter. Take for example the current file. The title is different from the one in the filename.
-
-In the beginning of the every post you have a so called [front matter](https://jekyllrb.com/docs/frontmatter/){:target="_blank"} block which contains some data about the post. Here is the short description of the options.
-
-* **layout**: Post's layout. This setting is configured by default. Use only if you want a custom post layout.
-* **author**: Post's author. You can see all authors in the authors.yml file in the _data folder.
-* **title**: Post's title. Overwrites the one from the filename.
-* **date**: Post's date. Overwrites the one from the filename.
-* **categories**: This post can be included under one or many categories. List them here. Keep in mind that you have to create a file for every new category. Check out the guide for creating a new category below.
-* **tags**: List the specific post tags. Keep in mind that you have to create a file for every new tag. Check out the guide for creating a new category below.
-* **description**: Meta description used for better SEO.
-* **comments**: By default they are always true, but if you want to turn them off for a specific post just set this to false.
-
-You can add more or different data in the front matter by yourself. You'll just have to learn how to display it :).
-
-### How To Add a Page
-Adding page is even simpler than adding post. Go go _pages folder and add a file with the following format: page-title.FORMAT. FORMAT is the file extension and it can be .md, .markdown or .html. Pages are also using front matter to add information to your page. Just like posts, pages have default front matter.
-
-* **layout**: The page's layout. Unlike posts, setting the layout for the page is required.
-* **title**: Page's title.
-* **permalink**: This is important. If you do not enter the permalink, your URL will be something like this http://example.com/_pages/about. Enter the permalink and get rid of /_pages/ part. Do not forget the trailing slash!
-* **showInMenu**: By default every page is shown in the main menu. Set it to false if you don't want it to be visible there.
-
-There are two "special" or in other words hardcoded pages that are custom for this theme - **About Page** and **Work Page**. They have some additional front matter that I'd like to share with you.
-Special pages do not use page layout so they'll need another property to show up in the main menu.
-
-* **customPage**: If you want a special page to be visible in the menu you'll have to keep this option set to true along with showInMenu. If false or removed the page will not be visible.
-* **order**: Custom pages can be ordered. Just place a number here.
-
-### How To Add a New Project
-Go to the _projects folder and create a new file. There is a little bit of front matter that you'll have to fill:
-
-{% highlight ruby linenos %}
----
-name: App
-category: App Design
-creationDate: 2021-02-01
-client: Tesla
-role: App Deisgner
-website: https://project.website.com
-cover: http://path.to.cover.image.jpg
-gallery:
-- http://path.to.image1.jpg
-- http://path.to.image2.jpg
----
-{% endhighlight %}
-
-I think all of the properties are self-explanatory. Keep in mind that demo projects are using webp format for the images and they are hosted on my server to keep the size of the theme as low as possible. If you keep your images in the images folder (as you should be) the path is /assets/images/image.FORMAT.
-
-### How To Add a New Category
-I wanted to keep this theme as light and clean as possible, so the use of external plugins was not an option. Besides, I also wanted to be GitHub Pages compatible.
-Adding a category is pretty simple, but some empty file creation is needed. Categories and tags are collections (just like projects) and every collection item require a dedicated file. Here are the steps of new category creation.
-
-1. Go to _category folder and create new file. For example: documentation.html.
-2. Open that file and add category property in the front matter. *Note: Filename and category must be exactly the same.*
-
-{% highlight ruby linenos %}
----
-category: documentation
----
-{% endhighlight %}
-
-{:start="3"}
-3. *Optional*: Go to a post and add category name to the list.
-
-### How To Add a New Tag
-I wanted to keep this theme as light and clean as possible, so the use of external plugins was not an option. Besides, I also wanted to be GitHub Pages compatible.
-Adding a tag is pretty simple, but some file creation is needed. Categories and tags are collections (just like projects) and every collection item require a dedicated file. Here are the steps of new tag creation.
-
-1. Go to _tag folder and create new file. For example: jekyll.html.
-2. Open that file and add tag property in the front matter. *Note: Filename and tag must be exactly the same.*
-
-{% highlight ruby linenos %}
----
-tag: jekyll
----
-{% endhighlight %}
-
-{:start="3"}
-3. *Optional*: Go to a post and add tag name to the list.
-
-### How To Add a New Author
-1. Go to _data folder and open authors.yml file. Take a look at the examples and add another author.
-2. Then go to a specific post and add author's name in the front matter.
-
-{% highlight ruby linenos %}
-henry:
- name: Henry Dawson
- title: Ordinary Gentleman
- avatar: /assets/images/user1.webp
-{% endhighlight %}
-
-Take a look at the example above. henry is the name that you put in the post's front matter and the name is just a display name that is used thereafter.
-
-### Enable & Configure Disqus Comments
-To enable and configure comments you must do the following:
-
-1. Go to _config.yml and under **Options** enable showComments.
-2. Go to _includes/components/comments.html file and edit your PAGE_URL and PAGE_IDENTIFIER variables. [Read about Disqus](https://disqus.com/admin/install/platforms/universalcode){:target="_blank"}.
-
-### Formspree (Contact Form)
-Go to [Formspree](https://formspree.io/){:target="_blank"} and register. Create a new project and then a form. Paste form's endpoint to the _config.yml file, section **Third Party / Social**. Voilà!
-
-### Site Search
-This theme use a third-party search library that is completely JavaScript. In the root folder you'll find the search.json file which is basically the search result's config. If you go to _includes/scripts.html you can also configure the library itself. You can change the settings but make sure you know what you are doing.
-
-### GitHub Pages
-Here is the one of many ways to upload the theme to GitHub Pages.
-
-1. Go to [GitHub](https://github.com/){:target="_blank"} and create a new repository. It can be private or public for now, just don't forget to make it public when you finish editing.
-2. Clone your repo and create a new branch called gh-pages.
-3. Go to your Henry theme and open _config.yml file. After url in the **Paths** section write down your full URL. Example: https://githubusername.github.io/repositoryname. Build using bundle exec jekyll build.
-4. Copy the contents of _site folder to the newly created GitHub Pages repo.
-5. Then define user by executing two commands: git config user.email "Your Email" and git config user.name "Your Name".
-6. Use git add . to stage all files, then type git commit -m "Initial commit" to make your first commit and that followed by git push -u origin gh-pages to push the changes.
-7. Open https://githubusername.github.io/repositoryname (remember, you'll have to make it public). If you want to push new changes to the website, repeat step 6 and in the end just use git push.
-
-That's it! Do not hesitate to ask if you have any questions. Happy blogging!
\ No newline at end of file
diff --git a/henry/_posts/2021-01-15-how-to-install-the-theme.md b/henry/_posts/2021-01-15-how-to-install-the-theme.md
deleted file mode 100644
index 0950480..0000000
--- a/henry/_posts/2021-01-15-how-to-install-the-theme.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-author: henry
-title: "How To Install"
-categories: docs
-tags: jekyll ruby bundler documentation
----
-
-
-
-
-
-I assume that you have already downloaded and installed Ruby. Here's what you need to do next:
-
-1. Run gem install jekyll bundler.
-2. Extract the theme to a desired folder.
-3. Go into that folder by executing cd name-of-the-folder.
-4. Run bundle install.
-5. If you want to access and customize the theme, use bundle exec jekyll serve. This way it will be accessible on http://localhost:4000/ or http://127.0.0.1:4000/. Also, after every change you make the theme will rebuild itself automatically.
-6. Run bundle exec jekyll build and upload the content of the compiled _site folder on your host server.
\ No newline at end of file
diff --git a/henry/_projects/app.html b/henry/_projects/app.html
deleted file mode 100644
index 479dbea..0000000
--- a/henry/_projects/app.html
+++ /dev/null
@@ -1,14 +0,0 @@
----
-name: App
-category: App Design
-creationDate: 2021-02-01
-client: Tesla
-role: App Deisgner
-website: https://dribbble.com/UpNow_Studio
-cover: http://joro.me/demo-assets/jekyll/henry/project6-main.webp
-gallery:
-- http://joro.me/demo-assets/jekyll/henry/project6-lb1.webp
-- http://joro.me/demo-assets/jekyll/henry/project6-lb2.webp
----
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
\ No newline at end of file
diff --git a/henry/_projects/customer-logo.html b/henry/_projects/customer-logo.html
deleted file mode 100644
index 1f88606..0000000
--- a/henry/_projects/customer-logo.html
+++ /dev/null
@@ -1,14 +0,0 @@
----
-name: Customer Logo
-category: Logo Design
-creationDate: 2021-02-13
-client: Forbes
-role: Deisgner
-website: https://dribbble.com/christinescarcelli
-cover: http://joro.me/demo-assets/jekyll/henry/project3-main.webp
-gallery:
-- http://joro.me/demo-assets/jekyll/henry/project3-lb1.webp
-- http://joro.me/demo-assets/jekyll/henry/project3-lb2.webp
----
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
\ No newline at end of file
diff --git a/henry/_projects/dashboard.html b/henry/_projects/dashboard.html
deleted file mode 100644
index c62885d..0000000
--- a/henry/_projects/dashboard.html
+++ /dev/null
@@ -1,15 +0,0 @@
----
-name: Dashboard
-category: UI/UX
-creationDate: 2021-02-20
-client: Amazon
-role: Web Developer
-website: https://dribbble.com/RikoSapto
-cover: http://joro.me/demo-assets/jekyll/henry/project1-main.webp
-gallery:
-- http://joro.me/demo-assets/jekyll/henry/project1-lb1.webp
-- http://joro.me/demo-assets/jekyll/henry/project1-lb2.webp
----
-
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
\ No newline at end of file
diff --git a/henry/_projects/illustration.html b/henry/_projects/illustration.html
deleted file mode 100644
index 920db35..0000000
--- a/henry/_projects/illustration.html
+++ /dev/null
@@ -1,14 +0,0 @@
----
-name: Illustration
-category: Vector Graphics
-creationDate: 2021-02-08
-client: FitBit
-role: Deisgner
-website: https://dribbble.com/mspasova
-cover: http://joro.me/demo-assets/jekyll/henry/project4-main.webp
-gallery:
-- http://joro.me/demo-assets/jekyll/henry/project4-lb1.webp
-- http://joro.me/demo-assets/jekyll/henry/project4-lb2.webp
----
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
\ No newline at end of file
diff --git a/henry/_projects/product-page.html b/henry/_projects/product-page.html
deleted file mode 100644
index 385d6fc..0000000
--- a/henry/_projects/product-page.html
+++ /dev/null
@@ -1,14 +0,0 @@
----
-name: Product Page
-category: Web Design
-creationDate: 2021-02-16
-client: Nike
-role: Front-End Developer
-website: https://dribbble.com/OrangePeelStudiosUK
-cover: http://joro.me/demo-assets/jekyll/henry/project2-main.webp
-gallery:
-- http://joro.me/demo-assets/jekyll/henry/project2-lb1.webp
-- http://joro.me/demo-assets/jekyll/henry/project2-lb2.webp
----
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
\ No newline at end of file
diff --git a/henry/_projects/website.html b/henry/_projects/website.html
deleted file mode 100644
index 39083ff..0000000
--- a/henry/_projects/website.html
+++ /dev/null
@@ -1,14 +0,0 @@
----
-name: Website
-category: Web Design
-creationDate: 2021-02-03
-client: Time Magazine
-role: Web Deisgner
-website: https://dribbble.com/sauqidesign
-cover: http://joro.me/demo-assets/jekyll/henry/project5-main.webp
-gallery:
-- http://joro.me/demo-assets/jekyll/henry/project5-lb1.webp
-- http://joro.me/demo-assets/jekyll/henry/project5-lb2.webp
----
-
Henry is an English male given name and surname derived from Old French Henri/Henry, itself derived from the Middle High German name Heinrich, from Old High German Haimirich (from haim- "home" and rich "ruler"), which was conflated with the name Haginrich (from hagin "enclosure" and rich "ruler").
I assume that you have already downloaded and installed Ruby. Here's what you need to do next:
-
-
Run gem install jekyll bundler.
-
Extract the theme to a desired folder.
-
o into that folder by executing cd name-of-the-folder.
-
Run bundle install.
-
If you want to access and customize the theme, use bundle exec jekyll serve. This way it will be accessible on http://localhost:4000/ or http://127.0.0.1:4000/. Also, after every change you make the theme will rebuild itself automatically.
-
Run bundle exec jekyll build and upload the content of the compiled _site folder on your host server.
-
-
-
-
Configuration
-
All configuration options are in the _config.yml file. Let's take a look of the important ones.
-
General
-
-
title: Site name.
-
description: Site description.
-
-
Paths
-
These options are pretty important, so take a closer look. If you experience any problems with your paths you should check here.
-
-
url: A lot of people have problems when they try to setup their paths. That's why I've decided to keep things as simple as possible. So, usually you'll have to paste here your domain https://mysite.com and then in the baseurl you paste your subdomain (if there is one). The theme is configured to use absolute paths, so you'll have to paste the whole path here — domain + subdomain. For example, if your website is in the root folder, write down https://mysite.com, if there is a subfolder — https://mysite.com/subfolder. In this case you don't need the baseurl anymore.
-
baseurl: No longer needed due theme configuration. I left it just in case.
-
-
Options
-
-
darkMode: Enable/disable dark theme for the theme. If enabled you'll see an icon in the upper right corner.
-
showTags: Enable/disable visibility of post's tags.
-
showCategories: Enable/disable visibility of post's categories.
-
showSearch: Enable/disable visibility of global site search.
-
showSharePost: Enable/disable visibility of post's share options.
-
showFavIcon: Enable/disable visibility of favicon.
-
showComments: Enable/disable visibility of post's comments.
-
showCookieBanner: Enable/disable visibility of the cookie banner. This theme supports Google Analytics (GA), so there have to be some kind of user notification. If you don't use GA or other tracking service, you should disable it. Keep in mind that the banner is pretty basic, so in some cases you may need to customize it or entirely replace it with another third-party cookie service.
-
useExternalContactForm: Enable/disable usage of Formspree as default contact form. If this option is disabled, when you click Contact link in the main menu you'll be redirected directly to your default mail client. If enabled, a modal box will pop up and you'll be introduced to a more user-friendly contact form.
-
useAnalytics: Enable/disable usage of Google Analytics.
-
-
Third Party / Social
-
-
facebook: Link to your facebook page.
-
twitter: Link to your twitter page.
-
instagram: Link to your instagram page.
-
email: Your email address.
-
formspree: Link to your Formspree form. If you use Formspree, generate form ID and paste it here. Works only if you activated useExternalContactForm option in the previos section.
-
googleAnalyticsTrackingCode: Add your Google Analytics Tracking ID. Example ID: UA-XXXXXXX-2.
-
disqusID: Add your website shortname from Disqus. Keep in mind that by default Disqus comments are not configured. If you use this make sure showComments option is set to true.
-
twitterHandle: Add your Twitter handle.
-
-
Permalinks
-
There is a default structure of your links. If you want a different one, please check Jekyll documentation.
-
Pagination
-
-
paginate: Number of posts per page.
-
paginate_path: The default path is /blog/page:num/, so for example if you go to the second page you'll see something like this http://mysite.com/blog/page2/.
-
-
Important Note: Due to theme's compatibility with GitHub Pages, pagination is only supported on the default posts/blog page — Blog. When you list categories or tags, there is no pagination.
-
Includes
-
-
include: Force the inclusion of the pages directory.
-
-
Post Separator
-
-
excerpt_separator: By default when you're writing a post, you should add <!--more--> to define the end of the excerpt. If you remove this option your excerpt will show with the default settings and you'll not have control over the content. If you want to keep the custom separator (I strongly suggest) you can leave it as is or change the <!--more--> tag as well.
-
-
Assets Settings
-
-
sass_dir: Choose the path to your SCSS files.
-
style: Choose the compression method for the final CSS file.
All you need to do is to add a file to your _posts directory with the following format: YEAR-MONTH-DAY-title.MARKUP. Where YEAR is a four-digit number, MONTH and DAY are both two-digit numbers, and MARKUP is the file extension representing the format used in the file. You can overwrite these in the post's front matter. Take for example the current file. The title is different from the one in the filename.
-
In the beginning of the every post you have a so called front matter block which contains some data about the post. Here is the short description of the options.
-
-
layout: Post's layout. This setting is configured by default. Use only if you want a custom post layout.
-
author: Post's author. You can see all authors in the authors.yml file in the _data folder.
-
title: Post's title. Overwrites the one from the filename.
-
date: Post's date. Overwrites the one from the filename.
-
categories: This post can be included under one or many categories. List them here. Keep in mind that you have to create a file for every new category. Check out the guide for creating a new category below.
-
tags: List the specific post tags. Keep in mind that you have to create a file for every new tag. Check out the guide for creating a new category below.
-
description: Meta description used for better SEO.
-
comments: By default they are always true, but if you want to turn them off for a specific post just set this to false.
-
-
You can add more or different data in the front matter by yourself. You'll just have to learn how to display it :).
-
-
-
How To Add a Page
-
Adding page is even simpler than adding post. Go go _pages folder and add a file with the following format: page-title.FORMAT. FORMAT is the file extension and it can be .md, .markdown or .html. Pages are also using front matter to add information to your page. Just like posts, pages have default front matter.
-
-
layout: The page's layout. Unlike posts, setting the layout for the page is required.
-
title: Page's title.
-
permalink: This is important. If you do not enter the permalink, your URL will be something like this http://example.com/_pages/about. Enter the permalink and get rid of /_pages/ part. Do not forget the trailing slash!
-
showInMenu: By default every page is shown in the main menu. Set it to false if you don't want it to be visible there.
-
-
There are two "special" or in other words hardcoded pages that are custom for this theme - About Page and Work Page. They have some additional front matter that I'd like to share with you.
-
Special pages do not use page layout so they'll need another property to show up in the main menu.
-
-
customPage: If you want a special page to be visible in the menu you'll have to keep this option set to true along with showInMenu. If false or removed the page will not be visible.
-
order: Custom pages can be ordered. Just place a number here.
-
-
-
-
How To Add a New Project
-
Go to the _projects folder and create a new file. There is a little bit of front matter that you'll have to fill:
I think all of the properties are self-explanatory. Keep in mind that demo projects are using webp format for the images and they are hosted on my server to keep the size of the theme as low as possible. If you keep your images in the images folder (as you should be) the path is /assets/images/image.FORMAT.
-
-
-
How To Add a New Category
-
I wanted to keep this theme as light and clean as possible, so the use of external plugins was not an option. Besides, I also wanted to be GitHub Pages compatible.
-
Adding a category is pretty simple, but some empty file creation is needed. Categories and tags are collections (just like projects) and every collection item require a dedicated file. Here are the steps of new category creation.
-
-
Go to _category folder and create new file. For example: documentation.html.
-
Open that file and add category property in the front matter. Note: Filename and category must be exactly the same.
-
-
----
-category: documentation
----
-
-
-
Optional: Go to a post and add category name to the list.
-
-
-
-
How To Add a New Tag
-
I wanted to keep this theme as light and clean as possible, so the use of external plugins was not an option. Besides, I also wanted to be GitHub Pages compatible.
-
Adding a tag is pretty simple, but some file creation is needed. Categories and tags are collections (just like projects) and every collection item require a dedicated file. Here are the steps of new tag creation.
-
-
Go to _tag folder and create new file. For example: jekyll.html.
-
Open that file and add tag property in the front matter. Note: Filename and tag must be exactly the same.
-
-
----
-tag: jekyll
----
-
-
-
Optional: Go to a post and add tag name to the list.
-
-
-
-
How To Add a New Author
-
-
Go to _data folder and open authors.yml file. Take a look at the examples and add another author.
-
Then go to a specific post and add author's name in the front matter.
Take a look at the example above. henry is the name that you put in the post's front matter and the name is just a display name that is used thereafter.
-
-
-
Enable & Configure Disqus Comments
-
To enable and configure comments you must do the following:
-
-
Go to _config.yml and under Options enable showComments.
-
Go to _includes/components/comments.html file and edit your PAGE_URL and PAGE_IDENTIFIER variables. Read about Disqus.
-
-
-
-
Formspree (Contact Form)
-
Go to Formspree and register. Create a new project and then a form. Paste form's endpoint to the _config.yml file, section Third Party / Social. Voilà!
-
-
-
Site Search
-
This theme use a third-party search library that is completely JavaScript. In the root folder you'll find the search.json file which is basically the search result's config. If you go to _includes/scripts.html you can also configure the library itself. You can change the settings but make sure you know what you are doing.
-
-
-
GitHub Pages
-
Here is the one of many ways to upload the theme to GitHub Pages.
-
-
Go to GitHub and create a new repository. It can be private or public for now, just don't forget to make it public when you finish editing.
-
Clone your repo and create a new branch called gh-pages.
-
Go to your Henry theme and open _config.yml file. After url in the Paths section write down your full URL. Example: https://githubusername.github.io/repositoryname. Build using bundle exec jekyll build.
-
Copy the contents of _site folder to the newly created GitHub Pages repo.
-
Then define user by executing two commands: git config user.email "Your Email" and git config user.name "Your Name".
-
Use git add . to stage all files, then type git commit -m "Initial commit" to make your first commit and that followed by git push -u origin gh-pages to push the changes.
-
Open https://githubusername.github.io/repositoryname (remember, you'll have to make it public). If you want to push new changes to the website, repeat step 6 and in the end just use git push.
-
-
-
That's it! Do not hesitate to ask if you have any questions. Happy blogging!
-
-
-
\ No newline at end of file
diff --git a/henry/index.html b/henry/index.html
deleted file mode 100644
index b1c345f..0000000
--- a/henry/index.html
+++ /dev/null
@@ -1,3 +0,0 @@
----
-layout: blog
----
\ No newline at end of file
diff --git a/henry/psd/Henry.psd b/henry/psd/Henry.psd
deleted file mode 100644
index f0f5f20..0000000
Binary files a/henry/psd/Henry.psd and /dev/null differ
diff --git a/henry/search.json b/henry/search.json
deleted file mode 100644
index b3b88ab..0000000
--- a/henry/search.json
+++ /dev/null
@@ -1,14 +0,0 @@
----
-layout: none
----
-[
- {% for post in site.posts %}
- {
- "title" : "{{post.title | escape}}",
- "category" : "{{post.category}}",
- "tags" : "{{post.tags | join: ', '}}",
- "url" : "{{post.url | absolute_url}}",
- "date" : "{{post.date}}"
- } {% unless forloop.last %},{% endunless %}
- {% endfor %}
-]
\ No newline at end of file
- {% else %}
- {% assign author = site.data.authors['noavatar'] %}
-
- {% endif %}
-
-
- ![Logo]({{"/assets/images/logo.svg"){kind=logo}
- ![{{site.title}}]({{"/assets/images/henry.webp")
- 
-
- 
- 
- 
-
-