Merott

This is a simple Tailwind plugin to expose all of Tailwind's colors, including any custom ones, as custom css properties on the :root element.

There are a couple of main reasons this is helpful:

• You can reference all of Tailwind's colors—including any custom ones you define—from handwritten CSS code.
• You can define all of your colors within the Tailwind configuration, and access the final values programmatically, which isn't possible if you did it the other way around: referencing custom CSS variables (defined in CSS code) from your Tailwind config.

See the Tailwind Plugins for more info on plugins.

hangxingliu

// Refrence from: https://gist.github.com/beevelop/a0f2c76e79610dca01550c9a93f83876
// Copy following scripts in the developer console of page included markdown content you want to print:

(function () {
	var $ = document.querySelector.bind(document);
	$('#readme').setAttribute('style', 'position:absolute;top:0;left:0;right:0;bottom:0;z-index:100;background-color:white');
	$('#readme>article').setAttribute('style', 'border: none');
	$('body').innerHTML = $('#readme').outerHTML;
	window.print();
})();

beevelop

document.querySelector('#readme').setAttribute('style', 'position: absolute; top: 0; left: 0; right: 0; bottom: 0; z-index: 100; background-color: white')
document.querySelector('body').appendChild(document.querySelector('#readme'))
window.print()

sktse

How to Keep Pull Requests Manageable

• There are a lot different things you can try to keep pull requests manageable.
• These pointers are not meant to be rules, but merely guidelines when possible. Due to the nature of what you are working on, some of these techniques may not be possible (or incredibly difficult).

• Either way, here are some tips to help make people not want to claw their eyes out reviewing a pull request.

The Basics

• These are the fundamental basics to a pull request and ALL pull requests should have these, regardless of how small or meaningless it is.