


Notes on building a Jekyll blog (with easy-to-use template)_html/css_WEB-ITnose
Jun 24, 2016 am 11:47 AM
I spent a few days writing this blog during my summer vacation. At that time, I read about Git from a blog of teacher Ruan Yifeng Regarding the establishment of Pages blog, to be honest, although the blog post is very easy to understand, it is too simple and does not have much content worth referencing.
The GitHub address is: https://github.com /LastAvenger/LastAvenger.github.io
I am slowly modifying it during the summer vacation, from supporting only displaying blog posts to supporting tag clouds, archiving, and comments, thanks to Jekyll It is so powerful that each function only requires a very small amount of code to implement. Looking back, it is not difficult to build such a blog, but the process of starting from scratch is really worth enjoying.
The whole The process of building a blog mainly involves two things, one is the front-end of the web page, and the other is the implementation of the function.
Front-end
My website mainly refers to the appearance of a template from LOFTER. Use Firefox's F12 to view the elements on the web page one by one, and then go to the W3C to see what this attribute is used for. In the process of making the web page, I finally have a little understanding of css.
Functions
This part is mainly implemented using Jekyll’s own functions. No plug-ins are used. The more important lines of code are:
Generate a one-page blog post directory and display the date and summary:
{% for post in paginator.posts %} <a href="{{ post.url }}">{{ post.title }}</a><hr> <p> {{ post.excerpt | strip_html }} </p> <a href="">{{ post.date | date_to_string }}</a> {% endfor %}
Page switching of blog post list:
{% if paginator.previous_page %} {% if paginator.page == 2 %} <a href="../">? 上 ? 一頁(yè)</a> {% else %} <a href="/page{{ paginator.previous_page }}">? 上 ? 一頁(yè)</a> {% endif %}{% else %} <a>? 上 ? 盡頭</a>{% endif %}{% if paginator.next_page %} <a href="/page{{ paginator.next_page }}">下 ? 一頁(yè) ? </a>{% else %} <a>下 ? 盡頭 ? </a>{% endif %}
Generate tag cloud, and increase the font size by 20% for every five blog posts under a certain tag:
{% for tag in site.tags %} <a href="#{{ tag[0] }}" title="{{ tag[0] }}" style="font-size: {{ tag[1].size | divided_by:5 | times:20 | plus:100 }}%;">{{ tag[0] }}({{ tag[1].size }})</a>{% endfor %}
Generate a tag cloud with date Tag list:
{% for tag in site.tags %} <blockquote id="{{ tag[0] }}">{{ tag[0] }}</blockquote> <ul> {% for post in tag[1] %} <li> <time datetime="{{ post.date | date_to_string }}">{{ post.date | date_to_string}}</time> <a href="{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a> </li> {% endfor %} </ul>{% endfor %}
Generate archived article navigation:
{% for post in site.posts %} {% capture ym %} {{ post.date | date:"%Y 年 %m 月" }} {% endcapture %} {% if yearmonth != ym %} {% assign yearmonth = ym %} <li><a href="#{{ ym }}">{{ ym }}</a></li> {% endif %}{% endfor %}
Generate archived article list:
{% for post in site.posts %} {% capture ym %}{{ post.date | date:"%Y 年 %m 月" }}{% endcapture %} {% if yearmonth != ym %} {% assign yearmonth = ym %} </ul> <blockquote id="{{ ym }}">{{ ym }}</blockquote> <ul> {% endif %} <li> <time datetime="{{ post.date | date_to_string }}">{{ post.date | date_to_string }}</time> <a href="{{ post.url }}" title="{{ post.title }}">{{ post.title }}</a> </li>{% endfor %}
Force content to be converted as Markdown:
{{ content | markdownify }}
Switching between blog posts:
{% if page.previous %} <a href="{{ page.previous.url }}">? 上 ? {{ page.previous.title }}</a>{% else %} <a>? 上 ? 盡頭</a>{% endif %}{% if page.next %} <a href="{{ page.next.url }}">下 ? {{ page.next.title }} ? </a>{% else %} <a>下 ? 盡頭 ? </a>{% endif %}

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

ARIA's role attribute is used to define the role of web elements and improve accessibility. 1. Role attribute helps assistive technology to understand the functions of elements, such as buttons, navigation, etc. 2. Use role attributes to assign specific roles to non-semantic HTML elements. 3. The role attribute should be consistent with the element behavior and be verified by the accessibility tool test.

How to create a website layout? 1. Use HTML tags to define the content structure, such as, ,. 2. Control styles and positions through CSS, using box model, float or Flexbox layout. 3. Optimize performance, reduce HTTP requests, use cache and optimize images, and ensure responsive design.

Improve the readability and maintainability of HTML code can be achieved through the following steps: 1. Use semantic tags, such as, etc. to make the code structure clear and improve SEO effect; 2. Keep the code formatted and use consistent indentation and spaces; 3. Add appropriate comments to explain the code intention; 4. Avoid excessive nesting and simplify the structure; 5. Use external style sheets and scripts to keep the HTML concise.

The key to keep up with HTML standards and best practices is to do it intentionally rather than follow it blindly. First, follow the summary or update logs of official sources such as WHATWG and W3C, understand new tags (such as) and attributes, and use them as references to solve difficult problems; second, subscribe to trusted web development newsletters and blogs, spend 10-15 minutes a week to browse updates, focus on actual use cases rather than just collecting articles; second, use developer tools and linters such as HTMLHint to optimize the code structure through instant feedback; finally, interact with the developer community, share experiences and learn other people's practical skills, so as to continuously improve HTML skills.

The reason for using tags is to improve the semantic structure and accessibility of web pages, make it easier for screen readers and search engines to understand page content, and allow users to quickly jump to core content. Here are the key points: 1. Each page should contain only one element; 2. It should not include content that is repeated across pages (such as sidebars or footers); 3. It can be used in conjunction with ARIA properties to enhance accessibility. Usually located after and before, it is used to wrap unique page content, such as articles, forms or product details, and should be avoided in, or in; to improve accessibility, aria-labeledby or aria-label can be used to clearly identify parts.

To create a basic HTML document, you first need to understand its basic structure and write code in a standard format. 1. Use the declaration document type at the beginning; 2. Use the tag to wrap the entire content; 3. Include and two main parts in it, which are used to store metadata such as titles, style sheet links, etc., and include user-visible content such as titles, paragraphs, pictures and links; 4. Save the file in .html format and open the viewing effect in the browser; 5. Then you can gradually add more elements to enrich the page content. Follow these steps to quickly build a basic web page.

HTMLtagsareessentialforstructuringwebpages.Theydefinecontentandlayoutusinganglebrackets,ofteninpairslikeand,withsomebeingself-closinglike.HTMLtagsarecrucialforcreatingstructured,accessible,andSEO-friendlywebpages.

To create an HTML checkbox, use the type attribute to set the element of the checkbox. 1. The basic structure includes id, name and label tags to ensure that clicking text can switch options; 2. Multiple related check boxes should use the same name but different values, and wrap them with fieldset to improve accessibility; 3. Hide native controls when customizing styles and use CSS to design alternative elements while maintaining the complete functions; 4. Ensure availability, pair labels, support keyboard navigation, and avoid relying on only visual prompts. The above steps can help developers correctly implement checkbox components that have both functional and aesthetics.
