The popular open-source contract for web designers and developers by Stuff & Nonsense
- Originally published: 23/12/2008
- Revised date: 15/12/2013
- Original post
<link rel="import" href="../core-scaffold/core-scaffold.html"> | |
<link rel="import" href="../core-header-panel/core-header-panel.html"> | |
<link rel="import" href="../core-menu/core-menu.html"> | |
<link rel="import" href="../core-item/core-item.html"> | |
<link rel="import" href="../core-icon-button/core-icon-button.html"> | |
<link rel="import" href="../core-toolbar/core-toolbar.html"> | |
<link rel="import" href="../core-menu/core-submenu.html"> | |
<link rel="import" href="../google-map/google-map.html"> | |
<polymer-element name="my-element"> |
{"v":"5.1.16","fr":23.9759979248047,"ip":0,"op":218.999981044888,"w":1920,"h":1080,"nm":"Comp w Joysticks","ddd":0,"assets":[{"layers":[{"ddd":0,"ind":1,"ty":3,"nm":"Eyes Blinking","sr":1,"ks":{"o":{"a":0,"k":0,"ix":11},"r":{"a":0,"k":0,"ix":10},"p":{"a":0,"k":[960,540,0],"ix":2},"a":{"a":0,"k":[0,0,0],"ix":1},"s":{"a":0,"k":[100,100,100],"ix":6}},"ao":0,"ef":[{"ty":5,"nm":"Slider Control","np":3,"mn":"ADBE Slider Control","ix":1,"en":1,"ef":[{"ty":0,"nm":"Slider","mn":"ADBE Slider Control-0001","ix":1,"v":{"a":0,"k":0,"ix":1,"x":"var $bm_rt;\nvar lyr = comp('Comp w Joysticks').layer('Left Eye');\nvar s = lyr.startTime;\n$bm_rt = comp('Comp w Joysticks').layer('Eyes Blinking')('ADBE Effect Parade')(1)('ADBE Slider Control-0001').valueAtTime(sum(time, s));"}}]}],"ip":0,"op":243.999978881062,"st":0,"bm":0},{"ddd":0,"ind":2,"ty":4,"nm":"eye lid l top","sr":1,"ks":{"o":{"a":0,"k":100,"ix":11},"r":{"a":0,"k":0,"ix":10},"p":{"a":0,"k":[749.478,175.444,0],"ix":2,"x":"var $bm_rt;\nfunction slider(inputValue) {\n v |
import React from "react" | |
import { motion } from "framer-motion" | |
import { addPropertyControls, ControlType } from "framer" | |
function BlotterText({ | |
text, | |
color1, | |
color2, | |
color3, | |
fontFamily, |
import React, { useState, useEffect } from "react" | |
import { motion } from "framer-motion" | |
import { addPropertyControls, ControlType } from "framer" | |
function CursorRGB(props) { | |
const [offset, setOffset] = useState(0.018) | |
const [cursorPosition, setCursorPosition] = useState({ x: 0, y: 0 }) | |
useEffect(() => { | |
const handleMouseMove = (e) => { |
import React, { useState, useEffect } from "react"; | |
import { motion } from "framer-motion"; | |
const getLiveStatus = async (channelId) => { | |
const response = await fetch( | |
`https://www.googleapis.com/youtube/v3/search?part=snippet&eventType=live&type=video&channelId=${"channelId"}&key=YOUR_API_KEY` | |
); | |
const data = await response.json(); | |
// Check if any items were returned |
We're writing a Product Requirements Document (PRD) for the business. | |
Why Do Product Teams Use PRDs? | |
A PRD aligns all stakeholders. If teams don’t take the time to think deeply about what the goals are, clearly define success, scope, and assess risk, at some point inevitably someone will run into challenges. Without a PRD, the great risk is that each team member has a slightly different understanding of the project, which will later require backtracking to clarify and correct further down the line resulting in wasted time. So why should designers care about a PRD and why should you? So we have a deep understanding of what we're trying to achieve—as a business. | |
So we can be involved in planning. We should be an active participant and not passively receive the PRD from a product manager. Understand what we're being given by a product manager in order to contribute and even disagree. As a design team we're probably directly or indirectly involved in processes that influence the PRD such as customer interviews. |
A Pen by Josh Miller on CodePen.
A Pen by Josh Miller on CodePen.
A Pen by Josh Miller on CodePen.