Paula Lavalle paulathevalley

## html-tags-details-summary.html
<!DOCTYPE html>
<html>
  <head>
    <style>
      summary {
        cursor: pointer;
        list-style: none;
      }
      details[open] summary ~ * {
        animation: toggle 0.1s ease-in-out;

## Classes.js
class Spiderman {
  lookOut() {
    alert('My Spider-Sense is tingling.');
  }
}

let miles = new Spiderman();
miles.lookOut();

## Reach Philosophy.md

      
              1 file
            
          
              13 forks
            
          
              6 comments
            
          
              89 stars
            
          
                ryanflorence
                / Reach Philosophy.md
            
            
              Last active
              November 28, 2023 09:50
            
          
    Reach UI Philosophy

Reach UI is an accessible foundation for React applications and design systems.
The three equally important goals are to be:

Accessible
Composable
Stylable


## uselayouteffect-ssr.md

      
              1 file
            
          
              10 forks
            
          
              76 comments
            
          
              211 stars
            
          
                gaearon
                / uselayouteffect-ssr.md
            
            
              Last active
              May 16, 2024 14:13
            
              
                useLayoutEffect and server rendering
              
          
    If you use server rendering, keep in mind that neither useLayoutEffect nor useEffect can run until the JavaScript is downloaded.
You might see a warning if you try to useLayoutEffect on the server. Here's two common ways to fix it.
Option 1: Convert to useEffect

If this effect isn't important for first render (i.e. if the UI still looks valid before it runs), then useEffect instead.
function MyComponent() {

  
## MyResponsiveComponent.js
function MyResponsiveComponent() {
  const width = useWindowWidth(); // Our custom Hook
  return (
    <p>Window width is {width}</p>
  );
}

## shh.rb
require "rubygems"
require "twitter"

# get these from apps.twitter.com
CONSUMER_KEY = "foo"
CONSUMER_SECRET = "bar"
OAUTH_TOKEN = "blee"
OAUTH_TOKEN_SECRET = "baz"

TWITTER_USER = "your_username" # needs to be the one associated with keys above

## coordinating-async-react.md

      
              1 file
            
          
              22 forks
            
          
              9 comments
            
          
              150 stars
            
          
                acdlite
                / coordinating-async-react.md
            
            
              Last active
              March 20, 2022 12:27
            
              
                Demo: Coordinating async React with non-React views
              
          
    Demo: Coordinating async React with non-React views

tl;dr I built a demo illustrating what it might look like to add async rendering to Facebook's commenting interface, while ensuring it appears on the screen simultaneous to the server-rendered story.
A key benefit of async rendering is that large updates don't block the main thread; instead, the work is spread out and performed during idle periods using cooperative scheduling.
But once you make something async, you introduce the possibility that things may appear on the screen at separate times. Especially when you're dealing with multiple UI frameworks, as is often the case at Facebook.
How do we solve this with React?

  
## reactiveconf-slam-poetry.md

      
              2 files
            
          
              1 fork
            
          
              5 comments
            
          
              193 stars
            
          
                jevakallio
                / reactiveconf-slam-poetry.md
            
            
              Last active
              July 7, 2021 19:57
            
              
                #ReactiveConf 2017 Lightning Talk Submission: JavaScript Slam Poetry
              
          
    TL;DR: If you want to see me perform a spoken word poem about JavaScript in front of 1000 people (and on video), please ⭐ star this gist. If you're on mobile, you'll need to request desktop site.

  
JavaScript Slam Poetry


## iOSViewport.md

      
              1 file
            
          
              2 forks
            
          
              4 comments
            
          
              80 stars
            
          
                claus
                / iOSViewport.md
            
            
              Last active
              April 28, 2024 17:39
            
          
    Mobile Safari's 100% Height Dilemma

Whether you're developing a web application with native-ish UI, or just a simple modal popup overlay that covers the viewport, when it comes to making things work on iDevices in Mobile Safari, you're in for a decent amount of pain and suffering. Making something "100% height" is not as easy as it seems.
This post is a collection of Mobile Safari's gotchas and quirks on that topic, some with solutions and fixes, some without, in good parts pulled from various sources across the internets, to have it all in one place. Things discussed here apply to iOS8, iOS9 and iOS10.
The Disappearing Browser Chrome

Screen real estate on smartphones is limited, so Mobile Safari collapses the browser chrome (address bar and optional tab bar at the top, and tool bar at the bottom) when the user scrolls down. When you want to make something span exactly the height of the viewport, or pin something to the bottom of the screen, this can get tricky because the viewport changes size (or

  
## good-git-practices.md

      
              1 file
            
          
              0 forks
            
          
              2 comments
            
          
              2 stars
            
          
                coopy
                / good-git-practices.md
            
            
              Last active
              March 26, 2019 22:50
            
              
                Good git practices
              
          
    Good Git Practices

1. Commit often!


Each commit in a final pull request should contain one logical change, and tests + checks should run.
While you're working on a branch, you should commit often, but you don't have to follow these rules. Instead, once your work is complete, you can use interactive rebase or reset to create new, better organized commits.

2. Squashing commits: No rebase required
	<!DOCTYPE html>
	<html>
	<head>
	<style>
	summary {
	cursor: pointer;
	list-style: none;
	}
	details[open] summary ~ * {
	animation: toggle 0.1s ease-in-out;
	class Spiderman {
	lookOut() {
	alert('My Spider-Sense is tingling.');
	}
	}

	let miles = new Spiderman();
	miles.lookOut();
	function MyResponsiveComponent() {
	const width = useWindowWidth(); // Our custom Hook
	return (
	<p>Window width is {width}</p>
	);
	}
	require "rubygems"
	require "twitter"

	# get these from apps.twitter.com
	CONSUMER_KEY = "foo"
	CONSUMER_SECRET = "bar"
	OAUTH_TOKEN = "blee"
	OAUTH_TOKEN_SECRET = "baz"

	TWITTER_USER = "your_username" # needs to be the one associated with keys above