cvnero.blogg.se - Scss prepros comments stay in compressed

#Scss prepros comments stay in compressed update#

Video embeds are responsive and scale with the width of the main content block with the help of FitVids. For now it only appears on larger screens (tablet and desktop). PS: The TOC is hidden on small devices because I haven’t gotten around to optimizing it. Kramdown will take care of the rest and convert all headlines into a contents list.

Table of ContentsĪny article or page that you want a table of contents to render insert the following HTML in your post before the actual content. I’d suggest changing this to something more meaningful - your logo or avatar are good options. If you don’t assign a thumbnail the default graphic (default-thumb.png) is used. These are used by Open Graph and Twitter Cards meta tags found in _head.html. Post and page thumbnails work the same way.

#Scss prepros comments stay in compressed update#

Update the View all posts link in post.html layout found in _layouts to match title and URL set previously.

Rename posts.md to writing.md and update the YAML front matter to match the title and URL set in _config.yml.

Links : - title : Writing url : /writing/

In _config.yml under links: rename the title and URL to the following:.

For example, to change Posts to Writing update the following: The name can be customized to your liking by editing a few references. image : feature : feature-image-filename.jpg credit : Silent Comics #name of the person or site you want to credit creditlink : #url to their site or licensing Post Index PageĪ sample index page listing all posts grouped by the year they were published has been provided. Image credits appear directly below the feature image with a link back to the original source. If you want to apply attribution to a feature image use the following YAML front matter on posts or pages. image : feature : feature-image-filename.jpg thumb : thumbnail-image.jpg #keep it square 200x200 px is good To add a feature image to a post or page just include the filename in the front matter like so. The two layouts make the assumption that the feature images live in the images/ folder. If you want to serve these images responsively I’d suggest looking at the Jekyll Picture Tag plugin 2. An image cropped around around 1024 x 256 pixels will keep file size down with an acceptable resolution for most devices.

Feature ImagesĪ good rule of thumb is to keep feature images nice and wide so you don’t push the body text too far down. By default posts and pages will be created in MarkDown using the. There are a few configuration variables that can be changed in Rakefile.rb. Example below: rake new_postĮnter a title for your post: My Awesome PostĮnter category name to group your post in (leave blank for none ): blogĮnter tags to classify your post (comma separated ): web development, codeĬreating new post: _posts/-my-awesome-post.md Using either rake new_post or rake new_page will prompt you for a title and tags to classify them. There are two rake tasks that can be used to create a new post or page with all YAML Front Matter. Both have large feature images that span the full-width of the screen, and both are meant for long form articles and blog posts. There are two main content layouts: post.html (for posts) and page.html (for pages). # sample top navigation links links : - title : About Page url : /about/ - title : Posts url : /posts/ - title : Other Page url : /other-page/ - title : External Page url : external : true Adding Posts and Pages Top Navigation LinksĮdit page/post titles and URLs to include in the site’s navigation. If you want to waste time watching analytics, your Google Analytics ID goes here along with meta tags for Google Webmaster Tools and Bing Webmaster Tools site verification. If you want to link to an external image on Gravatar or something similar you’ll need to edit the path in _author-profile.html since it assumes it is located in /images. Owner/Author InformationĬhange your name, bio, and avatar photo (100x100 pixels or larger), Twitter url, email, etc. Just remember to set url back to the live domain before deploying or pushing to GitHub Pages. When working locally use or comment out url to avoid broken links prefixed with 1 in the various _includes and _layouts. A good place to start would be to change the title, description, and url of your site. html files found in _includes if you need to add or remove anything. Most of the variables found here are used in the. Pro-tip: Delete the gh-pages branch after cloning and start fresh by branching off master.