Skip to content

Instantly share code, notes, and snippets.

View ElyasSalar's full-sized avatar
🏠
Working from home

Elyas ElyasSalar

🏠
Working from home
View GitHub Profile
@monokee
monokee / define-component.js
Last active December 7, 2024 17:07
Tiny customElement wrapper that enables scalable web component architecture. Define custom elements with a configuration object that separates markup from css and javascript. Uses a slotted light DOM (no shadow DOM) to allow for powerful component extension, composition and easier styling with external stylesheets and global css variables. Expor…
/**
* Tiny customElement wrapper that enables scalable web component architecture.
* Define custom elements with a configuration object that separates markup from css and javascript.
* Uses a slotted light DOM (no shadow DOM) to allow for powerful component extension,
* composition and easier styling with external stylesheets and global css variables.
* Exports a component class that can be imported and explicitly used to be picked up by module bundlers.
* See comments for examples and GNU license below.
*/
export function defineComponent(name, config) {
@cblanquera
cblanquera / css-properties.json
Last active May 6, 2025 12:44
CSS properties via JSON
{
"align-content": {
"moz": false,
"webkit": true,
"syntax": "(stretch)|(center)|(flex-start)|(flex-end)|(space-between)|(space-around)|(initial)|(inherit)",
"initial": "stretch",
"values": [
"stretch",
"center",
"flex-start",
@wojteklu
wojteklu / clean_code.md
Last active June 7, 2025 22:45
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