pages-themes / leap-day Goto Github PK

Hi there,

Please see my page:

https://pnlbwh.github.io/dashboard/

As you can see on the left, default texts provided by the theme: Project maintained by pnlbwh and Hosted on GitHub Pages — Theme by mattgraham overlaps my headers.

Similar issue can be seen at https://pnlbwh.github.io/TBSS/TUTORIAL.html where my full table of contents isn't even visible on the left.

Is it normal or is there a way to push the default texts below?

The user @carlsonsantana validate your site template "https://pages-themes.github.io/leap-day/" and found these accessibility errors:

• Page https://pages-themes.github.io/leap-day/:
  • Issue 936cf575-1895-4ea8-aac1-59a0f85da420:
    • 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.46:1. Recommendation: change background to #1f1f1f.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(11) > div > pre > code > span:nth-child(27)
    • Context: <span class="k">end</span>
  • Issue adaeb022-8ebf-4379-aa54-fcb3231f4d96:
    • 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 2.12:1. Recommendation: change text colour to #fffefd.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(11) > div > pre > code > span:nth-child(24)
    • Context: <span class="si">}</span>
  • Issue 3f8ff507-7e17-46c1-89d3-ff299168732b:
    • 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 2.12:1. Recommendation: change text colour to #fffefd.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(11) > div > pre > code > span:nth-child(22)
    • Context: <span class="si">#{</span>
  • Issue e892a991-27b2-4d71-83b9-a429a28fe8f1:
    • 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.46:1. Recommendation: change background to #1f1f1f.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(11) > div > pre > code > span:nth-child(9)
    • Context: <span class="k">do</span>
  • Issue 2442c06f-3cce-49a9-aef2-2a948841311e:
    • 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.56:1. Recommendation: change background to #212121.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(11) > div > pre > code > span:nth-child(1)
    • Context: <span class="c1"># Ruby code with syntax highlig...</span>
  • Issue 02c6d0db-4c08-4051-9636-cf4bb653fc39:
    • 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 4.29:1. Recommendation: change background to #2f2f2f.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(10) > div > pre > code > span:nth-child(22)
    • Context: <span class="kc">true</span>
  • Issue 8efe9ff6-06c9-4ebb-b4df-0bc4cf7d35b3:
    • 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.46:1. Recommendation: change background to #1f1f1f.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(10) > div > pre > code > span:nth-child(21)
    • Context: <span class="k">return</span>
  • Issue c6210235-8757-4c73-b44e-33f4a01a47df:
    • 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 4.29:1. Recommendation: change background to #2f2f2f.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(10) > div > pre > code > span:nth-child(5)
    • Context: <span class="kd">function</span>
  • Issue 17e8cf1c-bb18-487c-8441-7ca6a30ef95d:
    • 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 4.29:1. Recommendation: change background to #2f2f2f.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(10) > div > pre > code > span:nth-child(2)
    • Context: <span class="kd">var</span>
  • Issue d979551f-6d75-4cdc-95d6-de4c081b9a61:
    • 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.56:1. Recommendation: change background to #212121.
    • Selector: html > body > div:nth-child(3) > section > div:nth-child(10) > div > pre > code > span:nth-child(1)
    • Context: <span class="c1">// Javascript code with syntax ...</span>
  • Issue 0395965e-2b08-459c-bc93-c83b7544f33f:
    • 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.09:1. Recommendation: change text colour to #157bae.
    • Selector: html > body > div:nth-child(3) > section > p:nth-child(2) > a
    • Context: <a href="./another-page.html">Link to another page</a>
  • Issue 18e76311-cae3-4b06-9b1b-10264b1c9b5e:
    • 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 2.54:1. Recommendation: change text colour to #705800.
    • Selector: #banner > div > span
    • Context: <span>Downloads:</span>

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

I already set my "title" in _config.yml but the theme shows my first Header

FIY.

Best,
Yang

hello i want to add python code highlight. How is that possible?

Hi,

a few days ago our custom CSS stopped working. I made a test with a very easy piece of code and it seems it does not read the CSS after the @ import.

During the table of content generation, the current implementation would use the content of the header, transform it a little bit, and then use the transformed as the id of the header and the ref of the table of content entries.

For non-ASCII headers that have custom ids, this approach proves problematic, as no ID will be generated from the non-ASCII header, resulting in a broken table of content.

# 注意事项 {#notes}

To fix this, I think the ID of headers should be used if they are available, and we only fall back to header content otherwise.

jekyll 3.7.2 | Error: Liquid syntax error (dirname/_includes/head.html line 5): Unknown tag 'seo' included

I am new to jekyll and I build a site following the tutorial in https://jekyllrb.com/docs/quickstart/. It by default use a gem-based theme and it work well. And then I wanna try regular theme so I copy the directories needed(_includes, _layout,asset and so on) into my site dir. And I delete the command line of 'gem "minima", "~> 2.0"' in Gemfile and 'theme: minima' in _config.yml as described in https://jekyllrb.com/docs/themes/.
Then I ran jekyll serve but it throws an error above.

Did I miss something after delete the command lines ?

Hello,

Google's Lighthouse extension reports this vulnerability (version v0.1.1):

Another Jekyll theme solved this vulnerability internally, and published a new release. Could you do the same?

I started getting this error today after pushing changes to my leap-day themed GitHub pages site.

Example error:

• Commit: ZufengW/ZufengW.github.io@9590e6b
• Action: Page Build
• Title: GitHub Pages failed to build your site.
• Message: Your SCSS file assets/css/style.scss has an error on line 1: File to import not found or unreadable: leap-day. Load path: /tmp/jekyll-remote-theme-20210724-6-1uvld1q/_sass.
• Impact: Cannot update the GitHub pages site.

The commit in this example is a tiny test change that doesn't change the SCSS file. I've done similar commits in the past that worked. But I started noticing this failure today when I pushed to two of my leap-day themed repos.

See the online (github) pages of my site;
https://blocksizeproposals.github.io/README-cn
or the source;
https://github.com/BlocksizeProposals/BlocksizeProposals.github.io/blob/master/README-cn.md

Notice how on the rendered site (github.io) the headers all have an id="" tag, which in the English version is a sanitized version of the latin1 characters, in the Chinese text the id tag is completely empty.

This breaks the headers-to-the-side feature as you can see. Clicking on each of the links
on the left side of the screen when looking at this page;
https://blocksizeproposals.github.io/README-cn

has no effect, as each link ends with '#'.

Please notice how the github rendered page does this correctly, it adds the Chinese characters to the URL and escapes them.
So you get something like;
https://github.com/BlocksizeProposals/BlocksizeProposals.github.io/blob/master/README-cn.md#%E6%BF%80%E6%B4%BB%E6%96%B9%E6%B3%95

In markdown, we could sometimes have

<details>
<summary>Summary of the details</summary>
- detail 1
- detail 2
- detail 3
</details>

rendered like this:

However, it's actually rendered and display as plain text... (actually not 100% sure if it's a theme specific problem 😳 )

Thank you!!

Helpful for an org

Source: https://validator.w3.org/nu/?doc=http%3A%2F%2Fpages-themes.github.io%2Fleap-day

• leap-day/_layouts/default.html

  Line 5 in 6501e79

  <meta http-equiv="X-UA-Compatible" content="chrome=1">

  • A meta element with an http-equiv attribute whose value is X-UA-Compatible must have a content attribute with the value IE=edge

• leap-day/_layouts/default.html

  Line 14 in 6501e79

  <meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no">

  • Consider avoiding viewport values that prevent users from resizing documents
• <h1 id="header-1">
  • Consider using the h1 element as a top-level heading only (all h1 elements are treated as top-level headings by many screen readers and other tools)
  • this could be solved by allowing section h3 in the nav:

    leap-day/assets/js/main.js

    Line 16 in 6501e79

    $("section h1, section h2").each(function(){

Also,

• leap-day/_layouts/default.html

  Line 56 in 6501e79

  <script type="text/javascript">

  • The type attribute is unnecessary for JavaScript resources

I am trying to use this theme. It is a very nice template. But am experiencing a few issues with the left menu. Appreciate your kind advice on how to over my issues.

Below is a picture of the issue:

1. The number of headers I have used seems to exceed the length of a page. In such a situation, I cannot see my headers after 5. Conclusions. The left menu cannot be scrolled up or down either. How to make it scrollable? Presently when I roll my mouse wheel, the text in the white zone gets scrolled regardless of my mouse pointer position. I think when the mouse pointer is within the left column, the mouse wheel should scroll the left menu, else it should scroll the main text region.
2. Information on Project maintained by and Hosted on GitHub-Pages - Theme appears to be overlapping with my headers in the left menu. How do I prevent this overlap? I was expecting these info to appear after my headings.
3. How do I make the texts in the left menu align left to be beneath the word Singapore. Presently, they are aligned right by default.

In file /sass/jekyll-theme-leap-day.scss there are two (incorrect) CSS function calls to linear_gradient instead of linear-gradient. Fix incoming in a PR soon.

The URLs have '#' only. For example, if I have a heading named "你好", then the URL should be appended with "#你好" instead of "#", which it actually nothing.
It's a bug. Is that a problem with this theme itself?

You may see what happened through my page: link

Hi,

Love the simplicity of the theme, but it would be better for me if there was an easy way to specify 'menu items'. These menu items would be the key pages of the site: eg User Guide, Getting Started, Download and Support. These menu items can be local pages or external links.

Thanks for considering this feature

default.html

<!doctype html>
<html lang="{{ site.lang | default: " en-US" }}">
<head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="chrome=1">
    
    {% seo %}

Regenerating: 1 file(s) changed at 2017-10-18 13:05:22   Liquid Exception: Liquid syntax error (line 7): Unknown tag 'seo' in /_layouts/default.html
...error:
             Error: Liquid syntax error (line 7): Unknown tag 'seo'
             Error: Run jekyll build --trace for more information.

I don't see %seo% declaration anywhere in the code.

Have worked with it a while and cannot find a means to make the href in wrapper nav ul behave like a "real" url.

Is there a way to do that or do I need to find a different way to show links to external pages (back to GitHub Discussions, Issues, etc.)?

Thanks for all your hard work.

Hi, thanks for the beautiful theme - and it works with mobile devices as well!

Most other themes supports going to the front page with title click, in Leap Day, however, the title is updated depending on the specific page - this causes problem that it seems there is no way to jump back to the front page.

I don't know whether this is intentional or overlooked?

I created a GitHub page with leap day theme. But when I opened the same page in the phone, the left side menu is not coming

hello

Is there a way to set the github.repository_url in the _config.yml ? Or override the variable?
(I have a main project, and the html in a projectname.github.io page)

I tried in the _config.yml
github.repository_url: https://github.com/user/project
site.github.repository_url: https://github.com/user/project

I haven't used jekyll before, so sorry if this is a simple question.

Apologies - don't know if you've seen these?

https://validator.w3.org/nu/?doc=https%3A%2F%2Fpages-themes.github.io%2Fleap-day%2F#l6c24

https://jigsaw.w3.org/css-validator/validator?uri=https%3A%2F%2Fpages-themes.github.io%2Fleap-day%2F&profile=css3svg&usermedium=all&warning=1&vextwarning=&lang=en

This .replace(/[^\w-]+/g,'') peace of code from main.js file does not work correctly with other languages than English.

I am using .replace(/[^\w\u0410-\u044f-]+/g,'') for Russian language, but I don't know what to do with other.

Hello,

I'm using the leap-day GitHub Pages theme in this page (https://dellos7.github.io/constitucion/), directly using the theme from GitHub, and I've realized that generated header anchors do not keep accented letters in the anchor.

For instance:

## Título I

get's parsed as #ttulo-i.

However, when navigating through the repo in GitHub, I will be able to use the headers in achors like this: #título-i. This is, GitHub does preserve accented letters, so if I'm able to use header anchors in GitHub (#título-i) I'm not able to do so in the site using the theme (as it would be #ttulo-i).

I think that they should be parsed at least as GitHub does, because the way they are working currently you can have them only working in the GitHub .md viewer or in the site using the theme, not in both places.

If you shall require any additional information or help, just let me know.

Thank you.

Just discovered this...

If I open https://pages-themes.github.io/leap-day/ in a browser and click on the "header 2" link on the left hand side everything works as it should, and the page scrolls to a position to show "header 2" just below the banner.

However, if I copy the "header 2" link (https://pages-themes.github.io/leap-day/#header-2) and paste it into a new browser window or tab "header 2" ends up behind the banner somewhere and you have to scroll up to see it.

Happy Christmas!

Andy B.

Fantastic theme, minimalist, stylish, just exactly what I was looking for. The Octocat icon at #banner > #logo doesn't look too great on my screen, however (scales poorly, blurred, pixelated):

This could be fixed by recreating this file an SVG, rather than a PNG, and making the associated change in jekyll-theme-leap-day.scss. This would break compatibility with browsers that don't support SVG rendering, but apparently supported browsers are at close to 100% share anyway (97%). Planning on submitting a PR soon, I have this resolved locally.

Hello,

Tried to apply this theme on my page but the scrolling is not working properly:
On the theme preview:
https://raw.githubusercontent.com/shyoutarou/Exam-70-483_Criar_usar_tipos/master/.github/LeapDayRight.gif

On my page:
https://raw.githubusercontent.com/shyoutarou/Exam-70-483_Criar_usar_tipos/master/.github/LeapDayIssue.gif

Best Regards.

I'm using this nice simple theme for automaitcally generated documentation, this works great so far except for pages the document lots of options, you can see it at https://machippie.github.io/system/.

Is there a way to limit the ToC only to h1 and h2? Or to get a better scrolling behavior for the sidebar?

The theme looks really nice thanks!

I have some suggestions and questions. As this is the first time I run jekyll I'm not sure how useful they are ;-)

1. In order to get jekyll working I had to add gem "kramdown-parser-gfm" to Gemfile. Without it I got messages saying kramdown-parser-gfm wasn't installed.

2. The script/bootstrap script is designed to mess with the user system, instead of just install things in the user home. IMHO this is a very bad idea.

3. I don't understand why the theme wastes so much user screen for screen sizes over tha 1060px. I also don't understand why so much sizes are hardcoded in pixels. As I said before I know nothing about jekyll, I just wanted to read images from my repo in an easy way when I found I had to use GitHub pages. So them I saw the templates and really liked this one. For my site I'm using:

section
{
 width:85%;
 right: -13%;
}
#banner
{
 right:1%;
 margin-right:0px;
 .fork
 {
  left:15%;
  margin-left:0;
 }
}
.wrapper
{
 width:95%
}
nav
{
 width: 14%;
 left:0;
 margin-left:0;
}
footer
{
 width: 14%;
 left:0;
 margin-left:0;
}

Sources say it’s possible through CSS (no JS required), but I’m not sure if the inner-workings of Leap Day are compatible.

To reproduce

Uh… Here! ➡ https://pages-themes.github.io/leap-day/#header-1

Note

Chrome DevTools told me that the links in the ToC are adjusted and animated by JavaScript. <a>s in the body are not covered, howëver, nor URLs with a #, of course.

I found the following W3C validation errors in assets/css/style.css:

ERROR; URI: file://localhost/TextArea; line 690: 
        
                                Value Error :  background (nullcolors.html#propdef-background)
        
                                “linear_gradient(#ffe788,#ffce38)” is not a “background-color” value : 
                            
ERROR; URI: file://localhost/TextArea; line 704: 
        
                                Value Error :  background (nullcolors.html#propdef-background)
        
                                “linear_gradient(#ffe788,#ffe788)” is not a “background-color” value : 
                            
ERROR; URI: file://localhost/TextArea; line 821: 
        
                                Value Error :  padding (nullbox.html#propdef-padding)
        
                                “auto” is not a “padding” value : 
                            

Interested in fixing them? Just clone this repository locally, make the suggested change, and run script/cibuild to confirm it's been fixed. After that, you can submit a pull request to get your change merged. Feel free to drop questions here if you run into any problems.

I've successfully installed the theme, index.md rendered into _site/index.html and was shown locally perfectly. But if I add new post in _post/ dir that I created, I didn't see the new post show up?
I think the _post/ folder's not parsed when building?

I've used other theme, which can show same post.

Dear Developers,

I am one of the user of the leap day themes. In one of the GitHub page the left side bar is overlapping the left side footer section. how to rectify this issue.

total heading and sub heading : 24

Hi!
I have been using this awesome theme to build my website and it was working fine when I looked at it on Firefox but now it looks like plain text when I opened it.
I thought it was my code but not even your official template displays correctly.
However, if I use Chrome, everything works smoothly.
What could it be the problem?

Thanks.

In the footer, the theme writes the line "Project maintained by {GithubUsername}".

Would be cool if i could change this line to something like "website maintained by" or something entirely different.