Vincent V. Toscano VincentVToscano

## meta-tags.md

      
              1 file
            
          
              462 forks
            
          
              75 comments
            
          
              1412 stars
            
          
                lancejpollard
                / meta-tags.md
            
            
              Created
              March 5, 2012 13:54
            
              
                Complete List of HTML Meta Tags
              
          
    Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/
Basic HTML Meta Tags

<meta name="keywords" content="your, tags"/>
<meta name="description" content="150 words"/>
<meta name="subject" content="your website's subject">
<meta name="copyright"content="company name">
<meta name="language" content="ES">

  
## meta-tags.md

      
              1 file
            
          
              390 forks
            
          
              59 comments
            
          
              1167 stars
            
          
                kevinSuttle
                / meta-tags.md
            
            
              Last active
              March 31, 2024 14:26
                — forked from lancejpollard/meta-tags.md
            
              
                List of Usable HTML Meta and Link Tags
              
          
    DEPRECATED

Please see: https://github.com/kevinSuttle/html-meta-tags, thanks for the idea @dandv!

Copied from http://code.lancepollard.com/complete-list-of-html-meta-tags/
Basic HTML Meta Tags


## 01-before.html
<!-- using the truncate filter -->
{% for post in site.posts limit:10 %}
   <h2><a href="{{ post.url }}">{{ post.title }}</a></h2>
   <span class="post-date">{{ post.date | date: "%B %d, %Y" }}</span>
   {% if post.content.size > 2000 %}
      {{ post.content | truncatewords: 300 }} <!-- bad! content gives you rendered html and you will truncate in the middle of a node -->
      <a href="{{ post.url }}">read more</a>
   {% else %}
      {{ post.content }}
   {% endif %}

## dabblet.css
/*
Fadeout and marquee
*/
.fadeout-text {
  overflow: hidden;
  width: 130px;
  /* Fallback solution for browsers that
     doesn't support the next set of rules. */
  text-overflow: ellipsis;
  white-space: nowrap;

## gist:3440492
<!DOCTYPE html>
<html>
	<head>
            <meta http-equiv="Content-Type"
                  content="text/html; charset=utf-8" />

	    <script src="jquery-1.7.2.min.js" ></script>
	    <script src="handlebars-1.0.0.beta.6.js" ></script>
	    <script src="underscore-min.js" ></script>
	    <script src="backbone-min.js" ></script>

## webkit-pseudo-elements.md

      
              1 file
            
          
              76 forks
            
          
              24 comments
            
          
              390 stars
            
          
                leostratus
                / webkit-pseudo-elements.md
            
            
              Created
              September 21, 2012 01:44
            
              
                Webkit Pseudo-Element Selectors (Shadow DOM Elements)
              
          
    An ongoing project to catalogue all of these sneaky, hidden, bleeding edge selectors as I prepare my JSConf EU 2012 talk.
Everything is broken up by tag, but within each the selectors aren't particularly ordered.
I have not tested/verified all of these. Have I missed some or got it wrong? Let me know. - A
A friendly reminder that you may need to set this property on your target/selected element to get the styling results you want:
-webkit-appearance:none;

  
## mixins.less
//
// LESS Utility Mixins
// -------------------

// Fill the parent element
.fill(@spacing: 0) {
  position: absolute;
  top: @spacing; bottom: @spacing;
  left: @spacing; right: @spacing;
}

## environment-variables-jekyll-templates.md

      
              2 files
            
          
              2 forks
            
          
              16 comments
            
          
              49 stars
            
          
                nicolashery
                / environment-variables-jekyll-templates.md
            
            
              Last active
              January 22, 2023 15:56
            
              
                Make environment variables available in Jekyll Liquid templates
              
          
    Environment variables in Jekyll templates

This is one way to pass some data (API tokens, etc.) to your Jekyll templates without putting it in your _config.yml file (which is likely to be committed in your GitHub repository).
Copy the environment_variables.rb plugin to your _plugins folder, and add any environment variable you wish to have available on the site.config object.
In a Liquid template, that information will be available through the site object. For example, _layouts/default.html could contain:


## git_create_orphan.sh
cd repository
git checkout --orphan orphan_name
git rm -rf .
rm '.gitignore'
echo "#Title of Readme" > README.md
git add README.md
git commit -a -m "Initial Commit"
git push origin orphan_name

## Localhost Wordpress Permissions
On Mac OS X (Leopard+), the Apache HTTP Server runs under the user account, _www which belongs to the group _www. To allow WordPress to configure wp-config.php during installation, update files during upgrades, and update the .htaccess file for pretty permalinks, give the server write permission on the files.

One way to do this is to change the owner of the wordpress directory and its contents to _www. Keep the group as staff, a group to which your user account belongs and give write permissions to the group.

$ cd /<wherever>/Sites/<thesite>
$ sudo chown -R _www wordpress
$ sudo chmod -R g+w wordpress

This way, the WordPress directories have a permission level of 775 and files have a permission level of 664. No file nor directory is world-writeable.
	<!-- using the truncate filter -->
	{% for post in site.posts limit:10 %}
	<h2><a href="{{ post.url }}">{{ post.title }}</a></h2>
	<span class="post-date">{{ post.date \| date: "%B %d, %Y" }}</span>
	{% if post.content.size > 2000 %}
	{{ post.content \| truncatewords: 300 }} <!-- bad! content gives you rendered html and you will truncate in the middle of a node -->
	<a href="{{ post.url }}">read more</a>
	{% else %}
	{{ post.content }}
	{% endif %}
	/*
	Fadeout and marquee
	*/
	.fadeout-text {
	overflow: hidden;
	width: 130px;
	/* Fallback solution for browsers that
	doesn't support the next set of rules. */
	text-overflow: ellipsis;
	white-space: nowrap;
	<!DOCTYPE html>
	<html>
	<head>
	<meta http-equiv="Content-Type"
	content="text/html; charset=utf-8" />

	<script src="jquery-1.7.2.min.js" ></script>
	<script src="handlebars-1.0.0.beta.6.js" ></script>
	<script src="underscore-min.js" ></script>
	<script src="backbone-min.js" ></script>
	//
	// LESS Utility Mixins
	// -------------------

	// Fill the parent element
	.fill(@spacing: 0) {
	position: absolute;
	top: @spacing; bottom: @spacing;
	left: @spacing; right: @spacing;
	}
	cd repository
	git checkout --orphan orphan_name
	git rm -rf .
	rm '.gitignore'
	echo "#Title of Readme" > README.md
	git add README.md
	git commit -a -m "Initial Commit"
	git push origin orphan_name
	On Mac OS X (Leopard+), the Apache HTTP Server runs under the user account, _www which belongs to the group _www. To allow WordPress to configure wp-config.php during installation, update files during upgrades, and update the .htaccess file for pretty permalinks, give the server write permission on the files.

	One way to do this is to change the owner of the wordpress directory and its contents to _www. Keep the group as staff, a group to which your user account belongs and give write permissions to the group.

	$ cd /<wherever>/Sites/<thesite>
	$ sudo chown -R _www wordpress
	$ sudo chmod -R g+w wordpress

	This way, the WordPress directories have a permission level of 775 and files have a permission level of 664. No file nor directory is world-writeable.