The purpose of the notification-feed-all collection is to allow the client to retrieve a list of manual and automatic collections, including:
notification-feed-info (manual)notification-feed-new-shows (automatic)
notification-feed-expiring-shows (automatic)
The goal of the project is to build an optimised version of the Commerce Journey to improve the user experience and maximise conversion. Why? Because in the last 4 months, less than 6% of all visits to the pass pages resulted in a sale.
We will create a fully working interactive prototype of the desired Commerce Journey using mocked data on a production environment with production ready code.
We will use extensive usability research, purchase funnel and commercial requirements to build the prototype.
The prototype will consist of a single responsive web application alongside multiple variants.
| $ sudo npm install pm2 -g | |
| /opt/bitnami/nodejs/bin/pm2 -> /opt/bitnami/nodejs/lib/node_modules/pm2/bin/pm2 | |
| /opt/bitnami/nodejs/bin/pm2-dev -> /opt/bitnami/nodejs/lib/node_modules/pm2/bin/pm2-dev | |
| /opt/bitnami/nodejs/bin/pm2-runtime -> /opt/bitnami/nodejs/lib/node_modules/pm2/bin/pm2-runtime | |
| /opt/bitnami/nodejs/bin/pm2-docker -> /opt/bitnami/nodejs/lib/node_modules/pm2/bin/pm2-docker | |
| + pm2@3.0.0 | |
| added 242 packages in 15.45s | |
| bitnami@~/www/commerce-api$ pm2 |
| # Path to your oh-my-zsh installation. | |
| export ZSH="/Users/fed/.oh-my-zsh" | |
| # Set name of the theme to load --- if set to "random", it will | |
| # load a random theme each time oh-my-zsh is loaded, in which case, | |
| # to know which specific one was loaded, run: echo $RANDOM_THEME | |
| # See https://github.com/robbyrussell/oh-my-zsh/wiki/Themes | |
| ZSH_THEME="robbyrussell" | |
| # Set list of themes to pick from when loading at random |
| code --install-extension christian-kohler.path-intellisense | |
| code --install-extension davidbwaters.macos-modern-theme | |
| code --install-extension dbaeumer.vscode-eslint | |
| code --install-extension esbenp.prettier-vscode | |
| code --install-extension formulahendry.code-runner | |
| code --install-extension jpoissonnier.vscode-styled-components | |
| code --install-extension kumar-harsh.graphql-for-vscode | |
| code --install-extension mikaelkristiansson87.react-theme-vscode | |
| code --install-extension msjsdiag.debugger-for-chrome | |
| code --install-extension nemesarial.dust |
| import React, { useState, useEffect } from 'react'; | |
| import PropTypes from 'prop-types'; | |
| import throttle from 'lodash.throttle'; | |
| import { Container, Placeholder } from './scroll-container.styles'; | |
| const ScrollContainer = ({ children, mode, offsetTop }) => { | |
| const [containerPosition, setContainerPosition] = useState('static'); | |
| const [placeholderHeight, setPlaceholderHeight] = useState(null); | |
| const placeholderRef = React.useRef(null); |
| git checkout master \ | |
| && git fetch -p origin \ | |
| && git branch -r --merged master \ | |
| | egrep -v "^ *origin/(master|develop|HEAD -> origin/master)$" \ | |
| | grep origin | sed 's/origin\///' \ | |
| | xargs -n 1 git push --delete origin |
The main goal of the Site Reliability Engineering (SRE) team is to create scalable and highly reliable software systems that fit any particular situation, and feedback mechanisms to provide insight into options for optimising these systems.
The contribution of the SRE team results in strict improvements across the following areas: software development, availability, performance, efficiency, change management, monitoring, emergency response, and capacity planning.
| function lerna_lint() { | |
| npx lerna exec $(for package_dir in `npx lerna changed -p`; do echo -n " --scope $(basename ${package_dir})"; done) -- yarn lint | |
| } | |
| function lerna_test() { | |
| npx lerna exec $(for package_dir in `npx lerna changed -p`; do echo -n " --scope $(basename ${package_dir})"; done) -- yarn test | |
| } | |
| function validate() { | |
| lerna_lint |