Skip to content

Instantly share code, notes, and snippets.

View rafszul's full-sized avatar

rafal szulczewski rafszul

View GitHub Profile
rafszul / public-defer-javascript.html
Created August 14, 2021 01:19 — forked from freddielore/public-defer-javascript.html
[Defer Third Party Scripts] Defer third party scripts #javascript #html #public
<script type="text/javascript">
var app = {
init: function() {
window.addEventListener('scroll', function() {
if (window.__he == undefined) {
window.addEventListener('mousemove', function() {
rafszul / cool-game-programming-blogs.opml
Created July 28, 2021 11:55 — forked from Reedbeta/cool-game-programming-blogs.opml
List of cool blogs on game programming, graphics, theoretical physics, and other random stuff
<?xml version="1.0" encoding="UTF-8"?>
<opml version="1.0">
<title>Graphics, Games, Programming, and Physics Blogs</title>
<outline text="Tech News" title="Tech News">
<outline type="rss" text="Ars Technica" title="Ars Technica" xmlUrl="" htmlUrl=""/>
<outline type="rss" text="Polygon - Full" title="Polygon - Full" xmlUrl="" htmlUrl=""/>
<outline type="rss" text="Road to VR" title="Road to VR" xmlUrl="" htmlUrl=""/>
rafszul /
Created July 28, 2021 11:54 — forked from lancejpollard/
Complete List of HTML Meta Tags

Copied from

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">
rafszul / yoast_seo_title_change-variable.php
Created July 28, 2021 00:27 — forked from amboutwe/yoast_seo_title_change-variable.php
Change existing or add custom title or meta template variables
/* Remove Yoast SEO Change existing title or meta template variable
* Credit: Moshe Harush
* Last Tested: Unknown
// define the wpseo_replacements callback
function filter_wpseo_replacements( $replacements ) {
rafszul /
Last active July 3, 2021 13:01 — forked from whoisryosuke/
Bring your feature branch up to date with master. Deploying from Git branches adds flexibility. Bring your branch up to date with master and deploy it to make sure everything works. If everything looks good the branch can be merged. Otherwise, you can deploy your master branch to return production to its stable state.

Updating a feature branch

First we'll update your local master branch. Go to your local project and check out the branch you want to merge into (your local master branch)

$ git checkout master

Fetch the remote, bringing the branches and their commits from the remote repository. You can use the -p, --prune option to delete any remote-tracking references that no longer exist in the remote. Commits to master will be stored in a local branch, remotes/origin/master

rafszul /
Created June 19, 2021 00:01 — forked from wojteklu/
Summary of 'Clean code' by Robert C. Martin

Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.

General rules

  1. Follow standard conventions.
  2. Keep it simple stupid. Simpler is always better. Reduce complexity as much as possible.
  3. Boy scout rule. Leave the campground cleaner than you found it.
  4. Always find root cause. Always look for the root cause of a problem.

Design rules

rafszul / gist:44d3182cee0de90dd9c7a5daf2ac4e5d
Created June 19, 2021 00:00 — forked from sreez/gist:c624b3e440b66f9d16a9dc39a2297ed1
taiwindcss default list of padding , font size and line height against equivalent pixels for font base 16px
0px 0rem .p-0
4px 0.25rem .p-1
8px 0.5rem .p-2
12px 0.75rem .p-3, .leading-3, .text-xs
14px 0.875rem .text-sm
16px 1rem .p-4, .leading-4, .text-base
18px 1.125rem .text-lg
20px 1.25rem .p-5, .leading-5, .text-xl
24px 1.5rem .p-6, .leading-6, .text-2xl
28px 1.75rem .leading-7
rafszul /
Created June 18, 2021 23:58 — forked from sandren/
Tailwind CSS best practices

Tailwind CSS best practices

Utility classes

  1. When writing a string of multiple utility classes, always do so in an order with meaning. The "Concentric CSS" approach works well with utility classes (i.e,. 1. positioning/visibility 2. box model 3. borders 4. backgrounds 5. typography 6. other visual adjustments). Once you establish a familiar pattern of ordering, parsing through long strings of utility classes will become much, much faster so a little more effort up front goes a long way!

  2. Always use fewer utility classes when possible. For example, use mx-2 instead of ml-2 mr-2 and don't be afraid to use the simpler p-4 lg:pt-8 instead of the longer, more complicated pt-4 lg:pt-8 pr-4 pb-4 pl-4.

  3. Prefix all utility classes that will only apply at a certain breakpoint with that breakpoint's prefix. For example, use block lg:flex lg:flex-col lg:justify-center instead of block lg:flex flex-col justify-center to make it very clear that the flexbox utilities are only applicable at the

rafszul / Tailwind Config - Stripped Version
Created June 16, 2021 00:57 — forked from benjtinsley/Tailwind Config - Stripped Version
Tailwind Config Stripped Version, which has been stripped of all default Tailwind values in order to ensure only the absolute necessary styles are generated into classes.
Tailwind - The Utility-First CSS Framework
A project by Adam Wathan (@adamwathan), Jonathan Reinink (@reinink),
David Hemphill (@davidhemphill) and Steve Schoger (@steveschoger).
Welcome to the Tailwind config file. This is where you can customize
Tailwind specifically for your project. Don't be intimidated by the