Code Monkey home page Code Monkey logo

freshman21's People

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

freshman21's Issues

typo in tags.md

permalink: /tags/ in tags.md is mistyped to premalink: /tags/.
It causes jekyll generates _site/tags.html if _config.yml sets permalink to some style other than pretty.
After correcting it, /tags/ will be generated in stead of /tags.html, which is expected and the same style as categories.md.

How to custom navigation?

I found an interesting thing. When I added a markdown file in the root of my GitHub Pages repo, the title of markdown was placed in the navigation automatically. Besides, all of navigation was placed according to the order of initial character of each words.

My question is, how to custom navigation? Any order, any words?

Thanks!

Sincerely,
Robin

Error deploying this theme

xx@kami:~/freshman21$ jekyll build --destination /var/www
Configuration file: /home/xx/blog/_config.yml
            Source: /home/xx/freshman21
       Destination: /var/www/
 Incremental build: disabled. Enable with --incremental
      Generating...
  Conversion error: Jekyll::Converters::Scss encountered an error while converting 'css/main.scss':
                    Invalid US-ASCII character "\xE3" on line 324
jekyll 3.4.0 | Error:  Invalid US-ASCII character "\xE3" on line 324

Extra slash at Recent Posts links

<div class="sidebar-module">
  <h4>{{ site.locales[site.default_locale].Recent_Posts }}</h4>
  {% for post in site.posts limit:5 %}
  <li>
  <a href="{{ site.baseurl }}/{{ post.url }}" title="{{ post.title }}" rel="bookmark">{{ post.title }}</a>
  </li>
  {% endfor %}
</div>

In the snippet above (Recent_Posts.html) the {{ post.url }} already comes with a prepending slash, so the compound `"{{ site.baseurl }}/{{ post.url }}`` gets one extra slash between the baseurl and the post url.

If the baseurl is not empty, the URL still works. If the baseurl is empty, the url won't be interpreted as relative path and the link will be broken.

build error from scss

I clone the code and run [jekyll build], it shows

$ jekyll build
Configuration file: D:/GitHub/richeir.github.io/freshman21/_config.yml
Source: D:/GitHub/richeir.github.io/freshman21
Destination: D:/GitHub/richeir.github.io/freshman21/_site
Incremental build: disabled. Enable with --incremental
Generating...
Conversion error: Jekyll::Converters::Scss encountered an error while converting 'css/main.scss':
Invalid GBK character "\xE3" on line 324
jekyll 3.4.3 | Error: Invalid GBK character "\xE3" on line 324

Each page has a class "about" for all images

As I understand, in the file _layouts/page.html you apply class "about" to all "page"s:

  <article class="post-content about"> 
    {{ content }}
  </article>

And in case I would like to add new page, for example, "Collections.md" with some images, then all images are in a circle.
I delete "about" in the file _layouts/page.html:

  <article class="post-content"> 
    {{ content }}
  </article>

and in case if I would like to make image in circle, like in your example in http://yulijia.net/freshman21/about, I add new class in _sass/_layout.scss:

.img-about
{
  height: 128px;
  width: 128px;
  border-radius:50%;
  margin: 0 auto;
  display: block;
}

And in 2_about.md use markdown syntax:

![麋鹿](https://i.imgur.com/Mdc4szJl.jpg){: .img-about}

Maybe there is more elegant solution for this problem.

Theme feedback and suggestions

Hello!

Many thanks for the neat and useful theme for Jekyll. For me it turned out to be one of the best! I’m not a web programmer, but still would like to express some of my preferences with respect to the theme.

I would like to suggest an improvement to the theme localisation, adding the opportunity to change "Read more"
For example, in the file /index.html change the line
<p style="text-align: right"><a href="{{ post.url | prepend: site.baseurl }}">Read more</a></p>
to
<p style="text-align: right"><a href="{{ post.url | prepend: site.baseurl }}">{{ site.locales[site.default_locale].ReadMore }}</a></p>

And to the file /_config.yml add a variable to each language:

en:
  ReadMore: "Read more"
ru:
  ReadMore: "Читать далее" (one of "Далее", "Читать дальше", "Читать далее", "Подробнее")

Additionally, in my view, russian localisation is not translated quite correctly
Google_search: "Поиск на Google" I would change to Google_search: "Поиск по сайту"
Recent_Posts: "Свежие посты" I would change to Recent_Posts: "Свежие записи"
Taggedwith: "с тегами" I would change to Taggedwith: "с метками"
Tags: "Теги" I would change to Tags: "Метки"
Here we have examples of translation of a few terms into russian: https://codex.wordpress.org/Вниманию_переводчиков

"Теги" and "Посты" - this is anglicism (words taken from english), which have the following equivalents "Метки" and "Записи".

On the main page, a multiple option should be present:
Previous: "Предыдущие записи", instead of Previous: "Предыдущий пост"
Next: "Следующие записи", and not Next: "Следующий пост"

In the case of freestanding posts, it should be just:
Previous: "Предыдущая запись"
Next: "Следующая запись"

Here, perhaps, it would be convenient to introduce separate parameters for Previous and Next, for example:

      PreviousPost: "Предыдущие записи"
      NextPost: "Следующие записи"
      PreviousPage: "Предыдущая запись"
      NextPage: "Следующая запись"

Alternatively you can use a "universal" (more general) translation:
Previous: "Назад"
Next: "Вперёд"
But in my view this isn’t very elegant.

I think it would be a good idea to localise the publication date as well. For example like here:
In the file index.html I changed

      <time itemprop="datePublished" datetime="{{ post.date | date: '%Y-%m-%d' }}">
      {{ site.locales[site.default_locale].PostDate }}{{ post.date | date: "%b %-d, %Y" }}
      </time>

to

<time itemprop="datePublished" datetime="{{ post.date | date: '%Y-%m-%d' }}">
          {{ site.locales[site.default_locale].PostDate }}
          {% if site.locales[site.default_locale].months %}
            {% case site.default_locale %}
            {% when 'ru' %}
              {{ post.date | date: "%-d" }}
              {% assign month = post.date | date: '%-m' %}
              {% case month %}
                {% when '1' %} {{ site.locales[site.default_locale].months.January }}
                {% when '2' %} {{ site.locales[site.default_locale].months.February }}
                {% when '3' %} {{ site.locales[site.default_locale].months.March }}
                {% when '4' %} {{ site.locales[site.default_locale].months.April }}
                {% when '5' %} {{ site.locales[site.default_locale].months.May }}
                {% when '6' %} {{ site.locales[site.default_locale].months.June }}
                {% when '7' %} {{ site.locales[site.default_locale].months.July }}
                {% when '8' %} {{ site.locales[site.default_locale].months.August }}
                {% when '9' %} {{ site.locales[site.default_locale].months.September }}
                {% when '10' %} {{ site.locales[site.default_locale].months.October }}
                {% when '11' %} {{ site.locales[site.default_locale].months.November }}
                {% when '12' %} {{ site.locales[site.default_locale].months.December }}
              {% endcase %}
              {{ post.date | date: "%Y" }}
            {% else %}
              {{ post.date | date: "%b %-d, %Y" }}
            {% endcase %}
          {% else %}
            {{ post.date | date: "%b %-d, %Y" }}
          {% endif %}
        </time>

and in the file _layouts/post.html I changed

    <time itemprop="datePublished" datetime="{{ page.date | date: '%Y-%m-%d' }}">
    {{ site.locales[site.default_locale].PostDate }}{{ page.date | date: "%b %-d, %Y" }}
    </time>

to

<time itemprop="datePublished" datetime="{{ page.date | date: '%Y-%m-%d' }}">
        {{ site.locales[site.default_locale].PostDate }}
        {% if site.locales[site.default_locale].months %}
          {% case site.default_locale %}
          {% when 'ru' %}
            {{ page.date | date: "%-d" }}
            {% assign month = page.date | date: '%-m' %}
            {% case month %}
              {% when '1' %} {{ site.locales[site.default_locale].months.January }}
              {% when '2' %} {{ site.locales[site.default_locale].months.February }}
              {% when '3' %} {{ site.locales[site.default_locale].months.March }}
              {% when '4' %} {{ site.locales[site.default_locale].months.April }}
              {% when '5' %} {{ site.locales[site.default_locale].months.May }}
              {% when '6' %} {{ site.locales[site.default_locale].months.June }}
              {% when '7' %} {{ site.locales[site.default_locale].months.July }}
              {% when '8' %} {{ site.locales[site.default_locale].months.August }}
              {% when '9' %} {{ site.locales[site.default_locale].months.September }}
              {% when '10' %} {{ site.locales[site.default_locale].months.October }}
              {% when '11' %} {{ site.locales[site.default_locale].months.November }}
              {% when '12' %} {{ site.locales[site.default_locale].months.December }}
            {% endcase %}
            {{ page.date | date: "%Y" }}
          {% else %}
            {{ page.date | date: "%b %-d, %Y" }}
          {% endcase %}
        {% else %}
          {{ page.date | date: "%b %-d, %Y" }}
        {% endif %}
      </time>

also I added to _config.yml:

      months:
        January: "января"
        February: "февраля"
        March: "марта"
        April: "апреля"
        May: "мая"
        June: "июня"
        July: "июля"
        August: "августа"
        September: "сентября"
        October: "октября"
        November: "ноября"
        December: "декабря"

Also it would be good to localise the heading “Table of Contents” which is written in the file "_sass/_layout.scss":

#markdown-toc:before{
  content:"Table of Contents";

In russian it would be:

#markdown-toc:before{
  content:"Содержание";

Change `site.url` to `site.baseurl` can make it work at localhost

Ap categories.md and tags.md, creating post links with {{site.url}} always direct the link to external website.
In the situation that user would like to preview posts at localhost, change {{site.url}} to {{site.baseurl}} helps to make the theme work at both localhost and remote server.

How to custom 404 page?

Adding 404 page to website is common sense, and this is useful for user experience. We are lucky that GitHub provides 404 page. But I want to custom 404 page, how to implement it? By the way, I tried to add custom 404 page by adding 404.md file, but the title of this file(Page Not Found) was placed in the navigation automatically, this is so bad, so I remove it.

Thanks!

Sincerely,
Robin

Why my custom javascript of backing to top don't work?

I used So Simple Theme before and I changed it to your theme yesterday. But I found a problem which worked well before. I added Back to Top feature by myself. The operations are follows:

Step 1, placed custom java script of backing to top feature. This java script can be shown at: http://git.io/xX5b

Step 2, added scroll up image, and this image can be obtained at: http://git.io/xXdk

Step 3, added custom div at footer.html, the code is follows:

<script src="/assets/js/vendor/jquery-1.9.1.min.js"></script>
<script src="/assets/js/totop.js"></script>
<footer class="site-footer">
   <div id="totop" style="position:fixed;bottom:150px;right:50px;cursor: pointer;">
      <a title="Back To Top"><img src="/images/scrollup.png"/></a>
   </div>
</footer>

After this three steps, the custom feature of backing to top finished. But it didn't work. It shown when I open any pages of my website, and when I click the scroll up image, nothing happened.

I am not familiar with java script, could you please help me? Thanks.

Sincerely,
Robin

How to make the category case sensitive?

Hi, there. I dig out a problem which troubles me.

Categories of my blog:

tree _posts/ | more

_posts/
├── Linux
│   ├── xxx.md
│   └── xxx.md
├── MySQL
│   ├── xxx.md
│   └── xxx.md
├── Other
│   ├── xxx.md
│   └── xxx.md
└── Python
├── xxx.md
└── xxx.md

4 directories, 121 files

But it displays in the page as follows:

Categories of my blog

I want to make the category of my blog case sensitive, like Linux, MySQL, Other, Python etc. How to make it? Thanks.

Sincerely,
Robin

Unnecessary conditional operator in _includes/footer.html

It seems, that conditional operator is unnecessary in _includes/footer.html:

  {% if site.github_username %}
  <a href="https://github.com/">Github</a>
  {% else %}
  GitHub 
  {% endif %}

That's enough:

  <a href="https://github.com/">GitHub</a>

Typo of recent.

Thanks for you excellent work.

I discovered a typo. When we express some post which published lately, we use recent posts, not resent.

All typo of resent are follows:

grep -rn Resent ./*

./_config.yml:33: Resent_Posts: "Resent Posts"
./_config.yml:46: Resent_Posts: "近期文章"
./_includes/Resent_Posts.html:2:

{{ site.locales[site.default_locale].Resent_Posts }}


./_includes/sidebar.html:4:{% include Resent_Posts.html %}
./_posts/2014-12-19-freshman21-structure.md:44:│   ├── Resent_Posts.html # right column sidebar content
./_posts/2014-12-19-freshman21-structure.md:102:│   ├── Resent_Posts.html
./_posts/2014-12-19-how-to-set-the-config-file.md:77: {% include Resent_Posts.html %}

I am looking forward to fix this typo. Thanks.

Sincerely,
Robin

Google search didn't work properly.

Thanks for adding Google search feature. I've tried to add full-text search feature via jekyll-lunr-js-search, but failed. Jekyll by GitHub don't support this plugin.

I add Goole search by myself according to your code. But it didn't work properly. I add hidden form parameter which is called site, yet I input search content, the results that provided by Google did't display the content of my own website. That is to say, the hidden form parameter site did't accept by Google search url.

I'm looking forward to fix this bug. Thanks.

Robin

File to import not found or unreadable: base. on line 53

Hi, I am new to jekyll and really enjoying your theme. But I've face some problem when trying to jekyll serve the template on localhost and the following message showed.

Conversion error: Jekyll::Converters::Scss encountered an error while converting 'blog/css/main.scss':
File to import not found or unreadable: base. on line 53
jekyll 3.8.5 | Error: File to import not found or unreadable: base. on line 53

Do you have any idea how to fix it?

How to update font size of post content?

I tried to update font size of my website, and I updated this font size: title of site, link of post and title of post. But I am in a puzzle about font size of post content. Thanks.

Sincerely,
Robin

Add feature of search?

I am looking forward to add search feature, thanks. Of course, I will try it by myself.

Sincerely,
Robin

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.