Is it possible to increase the width of the post contents, it currently takes around 1/3 of the screen width:

When I add images with the current width, its size gets reduced to match the page width, which sometimes makes the image/plots/graphs difficult to read.

I want to get markdown in order to start writing and editing my blog, but I'm not sure where to start.

I couldn't delete template posts without a build error. I believe the coding referencing in the "about.md" of files "2015-10-10-getting-started" and "2014-01-01-text-formatting-examples" causes a break in the file structure.

To solve: Reformat "about.md" located in "../menu" to include whats below only then save. After this step delete the template posts.
layout: page
title: About
permalink: /about

Why the contents in this file isn't changed that i edit

It is Lagrange title and github address in my repository

Make the readme more user friendly (this will increase the amount of users for sure) by creating a step by step guide which specifies how to:

• personalize the website
• get started as quickly as possible.

Example: how to set the social icons in the footer, which are already available, maybe how to add more of them...

They should always be next to each other in a row

og:image meta tag is used to generate cards for social media (twitter/facebook/...). Currently, it is generated by the jekyll-seo-tag plugin based on post:image.

The problem is jekyll-seo-tag expects the image path to be full, while Lagrange expects it relative to assets/img.

In the example page, there is an og:image tag:

<meta property="og:image" content="https://lenpaul.github.io/Lagrange/mountains.jpg" />

which contains an incorrect path. So if you share a link to this page on Twitter, the image is not shown.

Can I Open The _DATA Directory And Edit Setting.YML To Translate The Theme Language To zh-CN?

I would like the disable MathJax. Is there a config option for this?

Hi! I forked the project and committed some changes but the site doesn't show up and gives a 404 error page. I've searched the internet for solutions but couldn't find anything useful. Any suggestions?

https://jekyllrb.com/docs/themes/

I'm trying to use this theme to make a github pages site with the url "vedantroy.github.io". The current instructions say:

To start using Jekyll right away with GitHub Pages, fork the Lagrange repository on GitHub. From there, you can rename your repository to 'USERNAME.github.io', where 'USERNAME' is your GitHub username, and edit the settings.yml file in the _data folder to your liking. Ensure that you have a branch named gh-pages. Your website should be ready immediately at 'http://USERNAME.github.io'. Note: if you are hosting several sites under the same GitHub username, then you will have to use Project Pages instead of User Pages - just change the repository name to something other than 'http://USERNAME.github.io'.

However, the current Github pages documention says that for user sites, the files can only be published from the master branch. What should I do?

If your site is a User or Organization Page that has a repository named .github.io or .github.io , you cannot publish your site's source files from different locations. User and Organization Pages that have this type of repository name are only published from the master branch.

Hi,

I a getting bad rendering and broken links on local testing with bundle exec jekyll serve. The rendering on Github Pages is great. I believe the problem might reside in lines like this one:

What should I do? Thanks!

Right now, the theme is checking for an excerpt for the RSS feed. Is there a simple switch (or line of code to comment out) to default to full content for the feed?

The user @carlsonsantana validate your site template "https://lenpaul.github.io/Lagrange/" and found these accessibility errors:

• Page https://lenpaul.github.io/Lagrange/:
  • Issue cc4c54c9-b3f3-489b-9adf-22aeda410c73:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > footer > a:nth-child(5)
    • Context: <a href="/Lagrange/feed.xml"><i class="fa fa-rss-square" ari...</a>
  • Issue cb23d786-fbdd-4a20-a5bb-81d059e63d80:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > footer > a:nth-child(4)
    • Context: <a href="mailto:[email protected]" target="_blank"><i class="fa fa-envelope" aria-...</a>
  • Issue d82e78d8-8aa4-45f8-b2db-13eded0e50b3:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > footer > a:nth-child(3)
    • Context: <a href="http://www.linkedin.com/in/lenpaul/" target="_blank"><i class="fa fa-linkedin" aria-...</a>
  • Issue 53cbf462-6561-499c-88e8-e77ccd36b58b:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > footer > a:nth-child(2)
    • Context: <a href="https://twitter.com/paululele" target="_blank"><i class="fa fa-twitter" aria-h...</a>
  • Issue 94bb18aa-85bb-4e07-a373-f5e1c11c3f35:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > footer > a:nth-child(1)
    • Context: <a href="https://www.github.com/lenpaul" target="_blank"><i class="fa fa-github" aria-hi...</a>
  • Issue 27606d37-7dee-4503-80d7-5e46a9ad001e:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_1.1_1_1.H30.2
    • Message: Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(5) > div > a
    • Context: <a href="https://lenpaul.github.io/Lagrange/journal/about-the-author.html"><img src="https://lenpaul.githu...</a>
  • Issue f136696b-e683-4b4b-b3fd-0befd86780a3:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_1.1_1_1.H30.2
    • Message: Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(4) > div > a
    • Context: <a href="https://lenpaul.github.io/Lagrange/journal/learning-resources.html"><img src="https://lenpaul.githu...</a>
  • Issue 8a58b674-3f58-4594-ac8c-f04f9c008198:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_1.1_1_1.H30.2
    • Message: Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(3) > div > a
    • Context: <a href="https://lenpaul.github.io/Lagrange/journal/text-formatting-examples.html"><img src="https://lenpaul.githu...</a>
  • Issue 91123553-b128-4804-9a2e-bb0f668ed13e:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_1.1_1_1.H30.2
    • Message: Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(2) > div > a
    • Context: <a href="https://lenpaul.github.io/Lagrange/journal/getting-started.html"><img src="https://lenpaul.githu...</a>
  • Issue bddc3382-44c7-4e5a-a227-372311ee622c:
    • Type: Error
    • Code: WCAG2AA.Principle1.Guideline1_1.1_1_1.H30.2
    • Message: Img element is the only content of the link, but is missing alt text. The alt text should describe the purpose of the link.
    • Selector: html > body > div:nth-child(2) > div > div:nth-child(1) > div > a
    • Context: <a href="https://lenpaul.github.io/Lagrange/journal/welcome-to-lagrange.html"><img src="https://lenpaul.githu...</a>
  • Issue 674de4f1-52bf-4c9e-8f4f-e1199fe42dab:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > header > h3 > div > nav:nth-child(2) > a:nth-child(5)
    • Context: <a href="/Lagrange/feed.xml"><i class="fa fa-rss-square" ari...</a>
  • Issue 20392589-236c-4d97-996a-54c29ffc80d5:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > header > h3 > div > nav:nth-child(2) > a:nth-child(4)
    • Context: <a href="mailto:[email protected]" target="_blank"><i class="fa fa-envelope" aria-...</a>
  • Issue 2c3b36b5-6e25-4bdc-9a0d-eb20f017f2db:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > header > h3 > div > nav:nth-child(2) > a:nth-child(3)
    • Context: <a href="http://www.linkedin.com/in/lenpaul/" target="_blank"><i class="fa fa-linkedin" aria-...</a>
  • Issue c5159215-1f1a-447e-8de2-02e35dc86498:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > header > h3 > div > nav:nth-child(2) > a:nth-child(2)
    • Context: <a href="https://twitter.com/paululele" target="_blank"><i class="fa fa-twitter" aria-h...</a>
  • Issue 0d07926e-2e7e-48a8-b7b3-dda8b4c39b62:
    • Type: Error
    • Code: WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.A.NoContent
    • Message: Anchor element found with a valid href attribute, but no link content has been supplied.
    • Selector: html > body > div:nth-child(2) > header > h3 > div > nav:nth-child(2) > a:nth-child(1)
    • Context: <a href="https://www.github.com/lenpaul" target="_blank"><i class="fa fa-github" aria-hi...</a>
  • Issue fe5b7c53-f7a5-433b-9e4d-1fdb758afe11:
    • 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><title>La...</html>

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

I don't have much knowledge about css, so I am not sure if the code in the 270th line is correct. I have checked the code in VS code and WebStorm, they all show '}' expected.

pre {
    padding: 8px 12px;
    overflow-x: auto;

    > code {
        border: 0;
        padding-right: 0;
        padding-left: 0;
    }
}

Hi,

Thank you for this very useful theme.

I'm trying to deploy into a directory on my server, and it seems that the theme is not using baseurl (in _config.yml) throughout. In particular, it still uses '/assets' to refer to assets like css.

I've just started with jekyll, so I may just be doing this wrong. Is there a way to deploy to a directory or is this a bug?

Thanks.

the class attribute is defined twice which causes the paginator-button and paginator-active classes to not render.

Is it possible to remove all redundant "teaser" image, and use css to "crop" original "feature" image?

data setting is good!
and i think maybe we just one feed function.
for my PR, the following jobs have been done

1. support inline Latex using $example$
2. displays the total number of pages and the current number of pages.
3. using overflow-x: auto in order to have a better experience on mobile phones.

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

When clicking on the feed symbol in the page's header or footer while reading a post one gets redirected to the 404 page.

That's because the feed is located at:
https://lenpaul.github.io/Lagrange/feed.xml

But while reading a blog post this becomes:
https://lenpaul.github.io/Lagrange/journal/feed.xml
which obviously doesn't exist.

I fixed this by changing settings.yml from
- {icon: 'rss-square', link: 'feed.xml'}
to
- {icon: 'rss-square', link: '/feed.xml'}

This only works because I run Lagrange directly under the root URL but for the demo page this fix won't work because is will link to https://lenpaul.github.io/feed.xml which also doesn't exist.

before :

  <a href="https://github.com/{{site.author.github}}"><i class="fa fa-github" aria-hidden="true" target="_blank"></i></a>

after :

   <a target="_blank" href="https://github.com/{{site.author.github}}"><i class="fa fa-github" aria-hidden="true" ></i></a>

How does this point to FontAwesome? I was trying to find the old reference and change it to point at FontAwesome 5 so I don't load two versions, but I can't find the original reference in the first place.

hello! I was wondering if the menu pages allow for images to be posted on them? I am having a hard time figuring this out and would love some advice on if hosting images on menu pages is possible or not (like a head shot on the about page or multiple images on the other pages). Thank you!

Hi,
I was checking the Lagrange demo website in my cell phone, windows system and linux system using different web browsers. I found that there might be some problems of showing the inlined math symbol/equations in some of the combinations of the system and web browser. Hope this could be fixed.
Thanks.
Lei

GitHub Pages supports apply community-curated Jekyll themes in _config.yml. I tested it, but it doesn't work with this theme.

Issue description

Inline MathJax not working

Steps to reproduce the issue

1. \( y = mx + 1 \) or \$ y = mx + 1 \$

What's the expected result?

• Inline LaTex

What's the actual result?

• ( y = mx + 1 )

Additional details / screenshot

While my site looks good when hosted on github pages, when I run it with jekyll serve there is no CSS and clicking on the link to a post gives a 404 error. I suspect this is because the links are hardcoded to http://github.com/pages. Is there anyway to fix this by making the links relative?

@LeNPaul interested adding an Atom (RSS) feed function?

The hyperlinks only work if the user clicks on the post. Is it possible to make hyperlinks work in the preview?

Proofread documentation posts and add content about the optional Disqus.

Also talk about how users can change what social media icons show, and what options that they have.

Also add a credits page for those who made suggestions.

There's a wikipedia link to Joseph-Louis Millennial!

https://github.com/LeNPaul/Lagrange/blob/gh-pages/_posts/2014-01-01-text-formatting-examples.md

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