AB testing client library.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// NOTE: placeholders do not work in media queries. | |
// Remaining initial topography placeholders | |
%button { | |
color: $white; | |
font-family: $platform-w; | |
font-size: 20px; //shouldBe 24px | |
letter-spacing: .2px; //shouldBe 1.2px |
Get all of the apps running with the latest hieradata updates.
- see current IP list here
- run
sudo puppet agent -t
// the following takes place on initial load and subsequent renders
var riverSoloItems = bundle.containers.river[0].items;
var riverSoloComponents = _.map(riverSoloItems, function (item) {
return <RiverSolo {...item} />;
});
var trioItems = bundle.containers.trio[0].items;
Upon receiving technical designs from the Design team, or advising in their buildout, we should be thinking immediately about how those designs translate to application presentation and functionality. The purpose of this document is to outline a few of the key questions to ask about designs.
- Do the designs relate to the application's grid system? Are components within the designs defined by the grid?
We want to be able to stream all media posts to the song-of-the-day
slack channel via a web browser
- Outbound event when user posts to channel - see https://api.slack.com/slack-apps
- Users use a slash-command to trigger external event
- Utilize Slack's events API
- Web service receives these events
- Web service publishes to client via web socket
- Client-side code interprets payload and makes API call to appropriate service (youtube, spotify, etc) to generate a page embed
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// A pseudocode proposal setup for facilitating animation effects on scroll depth for longform article | |
// sample effect: https://readymag.com/u59457328/681360/ | |
// | |
// Utilizes the ScrollMonitor from Self: | |
// https://github.com/CondeNast/autopilot-self/blob/master/src/app/views/components/ScrollMonitor.js | |
class LongformPage extends React.Component { | |
render() { | |
return ( | |
<BasePage> |
Ticket: AUT-XXXX
Briefly describe the problem, solution, goal. Keep in mind reviewers may need some context for this work.
- JSDoc and other useful documentation
- Automated tests added or updated
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
const myComponent = () => { | |
return ( | |
<div>Hello, world!</div> | |
); | |
}; | |
const Foo = ({ bar, baz = [], quux }) => { | |
return ( | |
<div className="component-foo"> |
- Intro, why this topic, disclaimer
- note about TDD versus traditional dev
- Show an example of a complex view component
- Points why it is difficult to work with
- Walk through breaking it up into smaller components
- If you need helper functions - make them pure!
- React component philosophy
- stateless when possible
- as little business logic in the view layer as possible
NewerOlder