codeasashu / hcz-jekyll-blog Goto Github PK

When I try to jekyll serve the site, I immediately get the following errors:

[2016-07-12 19:31:26] ERROR `/static/img/loadingAnimation.gif' not found.
[2016-07-12 19:31:28] ERROR `/static/projects/placeholder.jpg' not found.
[2016-07-12 19:31:28] ERROR `/static/img/loadingAnimation.gif' not found.
[2016-07-12 19:31:33] ERROR `/static/img/loadingAnimation.gif' not found.
[2016-07-12 19:31:33] ERROR `/static/projects/placeholder.jpg' not found.

despite the fact that I have checked and all of these images are in the appropriate static folders.
What am I missing here?

The demo button on this page redirect to malware/porn http://jekyllthemes.org/themes/hcz-jekyll-material/

The gem jekyll-paginate is now obsolete and has been replaced by jekyll-paginate-v2. It requires a few minor changes:

• In _config.yml, a new structure needs to be made for the pagination options, see https://github.com/sverrirs/jekyll-paginate-v2/blob/8fc336f992e0bfd7bc29f39af8c6adfae6758ea0/README-GENERATOR.md#site-configuration
• In index.html pagination needs to be enabled explicitly, see https://github.com/sverrirs/jekyll-paginate-v2/blob/8fc336f992e0bfd7bc29f39af8c6adfae6758ea0/README-GENERATOR.md#page-configuration
  It seems to work fine as a drop-in replacement otherwise.

Your theme has been listed on http://jekyllthemes.ru

At the moment, the homepage and posts-by-category views statically take the first 20 words of an article and present that as an excerpt, even when there is a manually-defined excerpt front matter. Instead, it should display the full excerpt if it exists, and only then fall back to the current functionality.

Your theme has been listed on https://jekyll-themes.com/.

Post by category doesn't works if we put white space in the category. For example if I add a new category web designing it do not works. How can I overcome this situation?

Right now all items on the home page are statically set to use the fa-sticky-note icon. Instead, it would be nice if it made use of metadata inside a post, such as icon: fa-user or image: /images/my-thumbnail.png. Same goes for the posts-per-category view and the proposed collections-based projects.

Since the rewrite, the _config.yml file has had more generic options, and no longer has a filled-in baseurl variable. That causes the demo site to load the CSS of the parent site instead.

That said, you have a master branch, but it's empty right now. Why not separate everything into a clean master branch, and a demo site gh-pages branch? That would cut down on the merge conflicts that currently happen every time _config.yml changes.

Hello. I can´t find the file to load it in blogger. Can you help me please? Thanks.

It's probably a good idea to update https://github.com/ashutosh2k12/hcz-jekyll-blog/blob/gh-pages/about.md to link to this very repository instead, else it gets quite confusing as to where to get the theme from the demo site.

The Gemfile.lock file lists versions such as faraday (0.12.0.1) (and also repeats them later, like faraday (~> 0.8, < 1.0)). It's very unlikely that this very specific version of these packages is required, and there have been updates to the packages since. The required package versions should be less specific than that.

In http://aboutashu.com/hcz-jekyll-blog/others/2016/06/04/example-content.html if you click on the "jekyll" breadcrumb, you get redirected to http://aboutashu.com/category/jekyll instead of http://aboutashu.com/hcz-jekyll-blog/category/jekyll.

Similarly, all links in http://aboutashu.com/hcz-jekyll-blog/category/jekyll don't make use of baseurl either.

Hello, my friend wants to use the theme. But after she forked your repository and changed the name to "celery-gu.github.io", she cannot visit the website "celery-gu.github.io". And I tried like that and found I can't make it either. Could you please tell me how to use it? Thank you very much.

How can I do this. I don't want to see on main folder. I moved to _includes but I think I must change the lociton code. Where is this code?

Right now there's no way to make a menu link open in a new tab, even though that's the expected behaviour of the "XML Feed" link.

Adding this into _includes/navigation.html seems to do the job decently fine, although perhaps making a more user-friendly boolean is a better idea:

        {% assign target = i.target %}
        {% unless target %} {% assign target = '_self' %} {% endunless %}

In my current setup, I have a menu like this:

urls:
    - text: Home
      url: /index.html
      icon: fa-home
      layout: post
    - text: Articles
      url: /category/General articles.html
      icon: fa-file-text
    - text: About
      url: /about/index.html
      icon: fa-user

(This is because the server I'm using at the moment only displays pages that really exist, so just a link to /about/ or / would give a 404.)
This works fine, but the style of the menu button does not get the current-menu-item style applied to it when I visit the menu item.

Hi there,
I just found your great theme, but I couln't find an easy way to change the color scheme.
I looked at the sass and css files, but there seems to be no central option to control the primary and secondary colors (actually teal).

It would be great if the theme allows setting these colors without modifing the minified css files.
Please add an configurable option.

I hope that your work can be installed automatically with adding gem, as described here. If you feel it necessary maybe this can be your reminder, but feel free to close it if you think it's not necessary. Thanks i love your theme 😄

The user @carlsonsantana validate your site template "https://codeasashu.github.io/hcz-jekyll-blog" and found these accessibility errors:

• Page https://codeasashu.github.io/hcz-jekyll-blog/:
  • Issue 479068ab-645b-450f-bf16-408bbbb67ffa:
    • Type: Error
    • Code: WCAG2AA.Principle2.Guideline2_4.2_4_1.H64.1
    • Message: Iframe element requires a non-empty title attribute that identifies the frame.
    • Selector: #google_osd_static_frame_6407425108843
    • Context: <iframe id="google_osd_static_frame_6407425108843" name="google_osd_static_frame" style="display: none; width: 0px; height: 0px;"></iframe>
  • Issue 92a51603-f4fa-4098-a589-50af4e7103c5:
    • Type: Error
    • Code: WCAG2AA.Principle2.Guideline2_4.2_4_1.H64.1
    • Message: Iframe element requires a non-empty title attribute that identifies the frame.
    • Selector: #aswift_0
    • Context: <iframe width="720" height="60" frameborder="0" marginwidth="0" marginheight="0" vspace="0" hspace="0" allowtransparency="true" scrolling="no" allowfullscreen="true" onload="var i=this.id,s=window.google_iframe_oncopy,H=s&amp;&amp;s.handlers,h=H&amp;...
  • Issue 171936e9-60db-48e1-8503-8181d1f5449f:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_3.1_3_1.H49.AlignAttr
    • Message: Align attributes .
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(2) > div:nth-child(2) > div > div
    • Context: <div align="center"><script async="" src="https:...</div>
  • Issue ae244bbd-5b71-41fd-819a-4c380a306152:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.17:1. Recommendation: change text colour to #007a6f.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(2) > div:nth-child(2) > div > footer > a
    • Context: <a href="#">Privacy link</a>
  • Issue 594fa0b4-33b4-4c0f-ae70-34e88f5f3545:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change text colour to #008579.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(2) > div:nth-child(1) > div > div:nth-child(5) > div:nth-child(2) > h4 > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/others/2015/06/04/test-page.html">Test Page</a>
  • Issue 91ef06d2-31ee-4868-bc53-e78d408d1483:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change text colour to #008579.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(2) > div:nth-child(1) > div > div:nth-child(3) > div:nth-child(2) > h4 > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/others/2016/06/04/example-content.html">Example content for posts</a>
  • Issue e29701f5-4fbf-4918-b2d6-f76090f4162e:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change text colour to #008579.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(2) > div:nth-child(1) > div > div:nth-child(1) > div:nth-child(2) > h4 > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/jekyll/2016/06/04/welcome-to-jekyll.html">Welcome to Jekyll!</a>
  • Issue d3ef2bad-478d-4d9e-a38e-da88d2b43337:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change background to #008579.
    • Selector: #bs-example-navbar-collapse-1 > ul > li:nth-child(6) > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/feed.xml" target="_blank"><i class="fa fa-feed"></i> XML ...</a>
  • Issue 3a4e7987-63f3-4fb2-940e-a2ee17b05634:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change background to #008579.
    • Selector: #bs-example-navbar-collapse-1 > ul > li:nth-child(5) > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/#" target="_self"><i class="fa fa-github"></i> Gi...</a>
  • Issue c21afc42-a6dd-464f-be0f-6af9a9e231cc:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change background to #008579.
    • Selector: #bs-example-navbar-collapse-1 > ul > li:nth-child(4) > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/#" target="_self"><i class="fa fa-graduation-cap"...</a>
  • Issue 71d9c4ae-8519-4e40-8de5-410e3b142068:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change background to #008579.
    • Selector: #bs-example-navbar-collapse-1 > ul > li:nth-child(3) > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/projects" target="_self"><i class="fa fa-desktop"></i> P...</a>
  • Issue 5e39f741-6c75-4c73-b78a-5e965dfc1e5d:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.67:1. Recommendation: change background to #008579.
    • Selector: #bs-example-navbar-collapse-1 > ul > li:nth-child(2) > a
    • Context: <a href="https://codeasashu.github.io/hcz-jekyll-blog/about/" target="_self"><i class="fa fa-comments"></i> ...</a>
  • Issue 5d438352-6053-4664-85dd-ccaff010f184:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_3.1_3_1.F68
    • Message: This form field should be labelled in some way. Use the label element (either with a "for" attribute or wrapped around the form field), or "title", "aria-label" or "aria-labelledby" attributes as appropriate.
    • Selector: #js-search__input
    • Context: <input class="form-control" type="text" id="js-search__input" placeholder="Search">
  • Issue cdf28dad-65dd-4431-911c-2e78282b16fe:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.InputText.Name
    • Message: This textinput element does not have a name available to an accessibility API. Valid names are: label element, title undefined, aria-label undefined, aria-labelledby undefined.
    • Selector: #js-search__input
    • Context: <input class="form-control" type="text" id="js-search__input" placeholder="Search">
  • Issue be4e8470-5f88-40ac-97e7-3ab92c61b24b:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.EmptyNoId
    • Message: Anchor element found with no link content and no name and/or ID attribute.
    • Selector: html > body > div:nth-child(1) > div > div > div:nth-child(1) > div:nth-child(2) > div > a:nth-child(4)
    • Context: <a class="icon" target="_blank" href=""><i class="fa fa-stack-exchange"...</a>
  • Issue a1291250-cd0b-4430-8563-88807e6de917:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.EmptyNoId
    • Message: Anchor element found with no link content and no name and/or ID attribute.
    • Selector: html > body > div:nth-child(1) > div > div > div:nth-child(1) > div:nth-child(2) > div > a:nth-child(3)
    • Context: <a class="icon" target="_blank" href=""><i class="fa fa-linkedin"></i></a>
  • Issue 871606be-d352-41a8-bb19-728682e0b1e4:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.EmptyNoId
    • Message: Anchor element found with no link content and no name and/or ID attribute.
    • Selector: html > body > div:nth-child(1) > div > div > div:nth-child(1) > div:nth-child(2) > div > a:nth-child(2)
    • Context: <a class="icon" target="_blank" href=""><i class="fa fa-twitter"></i></a>
  • Issue 7317584f-d296-4f93-bbac-6373a0eee108:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.EmptyNoId
    • Message: Anchor element found with no link content and no name and/or ID attribute.
    • Selector: html > body > div:nth-child(1) > div > div > div:nth-child(1) > div:nth-child(2) > div > a:nth-child(1)
    • Context: <a class="icon" target="_blank" href=""><i class="fa fa-facebook"></i></a>
  • Issue 8cf36159-5b64-4c79-aaf7-2f1a58cc16f3:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.72:1. Recommendation: change background to #008579.
    • Selector: html > body > div:nth-child(1) > div > div > div:nth-child(1) > div:nth-child(2) > p
    • Context: <p class="list-group-item-text">Freelance developer</p>
  • Issue 4066724c-5678-44f7-9618-c84aad0d7067:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
    • Message: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.72:1. Recommendation: change background to #008579.
    • Selector: html > body > div:nth-child(1) > div > div > div:nth-child(1) > div:nth-child(2) > h4
    • Context: <h4 class="list-group-item-heading">John Smith</h4>
  • Issue a3c74e58-5943-49ba-9435-e0f98a4df896:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_1.1_1_1.H37
    • Message: Img element missing an alt attribute. Use the alt attribute to specify a short text alternative.
    • Selector: #about
    • Context: <img id="about" class="logo-img" src="/hcz-jekyll-blog/static/img/avatar.png" height="75px" width="75px">
  • Issue 15e3e569-6fff-4bfe-8686-5fb64d3dacb2:
    • Type: Error
    • Code: WCAG2AA.Principle3.Guideline3_1.3_1_1.H57.2
    • Message: The html element should have a lang or xml:lang attribute which describes the language of the document.
    • Selector: html
    • Context: <html><head><meta chars...</html>

You can check these accessibility errors using pa11y.
You can view the full validation results in our website.

Hi. I just came across to this really nice theme and started experimenting with.

having had a look at the code I found out that there are some social icons that should appear at the top of the page. However when I serve the page with jekyll those icons won't appear at all.

What am I missing?