rafal szulczewski rafszul

## Update-branch.md

      
              2 files
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                rafszul
                / Update-branch.md
            
            
              Last active
              July 3, 2021 13:01
                — forked from whoisryosuke/Update-branch.md
            
              
                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


## clean_code.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              2 stars
            
          
                sreez
                / clean_code.md
            
            
              Created
              September 6, 2020 18:31
                — forked from wojteklu/clean_code.md
            
              
                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


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

Design rules


## lazy-zendesk.js
(function () {

    function loadZendeskChat(callback) {
      var zdscript = document.createElement('script');
      zdscript.setAttribute('id','ze-snippet');
      zdscript.src = 'https://static.zdassets.com/ekr/snippet.js?key=XXX-XXX-XXX-XXX';
      (document.getElementsByTagName('body')[0]).appendChild(zdscript);

      window.zdonload = setInterval(function(){
        if(typeof zE !== "undefined" && typeof zE.activate !== "undefined") {

## gist:c624b3e440b66f9d16a9dc39a2297ed1
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

## tailwind.md

      
              1 file
            
          
              18 forks
            
          
              6 comments
            
          
              196 stars
            
          
                sandren
                / tailwind.md
            
            
              Last active
              March 20, 2024 09:37
            
              
                Tailwind CSS best practices
              
          
    Tailwind CSS best practices

Utility classes


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!


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.


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


## 1. highcharts.component.ts
import { AfterViewInit, Component, ElementRef, Input, OnChanges, SimpleChanges, ViewChild } from '@angular/core';
import { HighChartService } from './highchart.service';

@Component({
  selector: 'fb-highchart',
  template: '<div *ngIf="config"></div>',
  providers: [HighChartService]
})
export class HighChartComponent implements OnChanges, AfterViewInit {
  @Input() config: any;

## wordpress-PurgeCSS-whitelist.js
const WordpressPurgeCSS = {
    whitelist: [
        "rtl",
        "home",
        "blog",
        "archive",
        "date",
        "error404",
        "logged-in",
        "admin-bar",

## content.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              1 star
            
          
                rafszul
                / content.md
            
            
              Last active
              July 14, 2017 04:38
            
              
                Create a new project based on the
              
          
    Create a new project based on the QuickStart

Discard everything "git-like" by deleting the .git folder.
rm -rf .git
Create a new git repo

You could start writing code now and throw it all away when you're done.

  
## index.html
<!-- change 'app-root' tag and class -->

<body>
    <app-root>
        <style>
            app-root {
                background-image: url('/assets/gplaypattern_@2X.png');
                display: flex;
                justify-content: center;
                align-items: center;

## heyBarista-cupping.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              2 stars
            
          
                rafszul
                / heyBarista-cupping.md
            
            
              Last active
              July 28, 2020 10:25
            
              
                ng new heyBarista-cupping --ng4 --routing --style=scss --prefix cupping
              
          
    ng new heyBarista-cupping --ng4 --routing --style=scss --prefix cupping
https://github.com/angular/angular-cli/wiki/stories-include-angular-material
npm install --save @angular/material
npm install --save @angular/animations
in app.module.ts:
	(function () {

	function loadZendeskChat(callback) {
	var zdscript = document.createElement('script');
	zdscript.setAttribute('id','ze-snippet');
	zdscript.src = 'https://static.zdassets.com/ekr/snippet.js?key=XXX-XXX-XXX-XXX';
	(document.getElementsByTagName('body')[0]).appendChild(zdscript);

	window.zdonload = setInterval(function(){
	if(typeof zE !== "undefined" && typeof zE.activate !== "undefined") {
	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
	import { AfterViewInit, Component, ElementRef, Input, OnChanges, SimpleChanges, ViewChild } from '@angular/core';
	import { HighChartService } from './highchart.service';

	@Component({
	selector: 'fb-highchart',
	template: '<div *ngIf="config"></div>',
	providers: [HighChartService]
	})
	export class HighChartComponent implements OnChanges, AfterViewInit {
	@Input() config: any;
	const WordpressPurgeCSS = {
	whitelist: [
	"rtl",
	"home",
	"blog",
	"archive",
	"date",
	"error404",
	"logged-in",
	"admin-bar",
	<!-- change 'app-root' tag and class -->

	<body>
	<app-root>
	<style>
	app-root {
	background-image: url('/assets/gplaypattern_@2X.png');
	display: flex;
	justify-content: center;
	align-items: center;