2017-04-05

• How to setup Storybook to be used as your default site for GitHub Pages
  /schibsted-martin/roc-notify/HOWTO.md#publish-storybook-to-github-pages

There are a few different ways to provide your docs/example site to users. Some peope uses the gh-pages branch (obviously more related to GitHub users); while others uses the /docs folder in the master branch. Which one is used does not really matter in my oppinion, since they are essentially the same, but it could be good to know this and probably the "docs" option is more agnostic.

2017-03-27

A sheep teaching other sheep how to be a wolf

What's new

• Auto generated changelogs
• Mono repos
• Storybook
• github pages
• Hyperion reference
• Artifactory
• "White label" theming

Roc basics

Roc solves JS fatigue and provides a better developer experionce (DX) Read more http://www.getroc.org/, https://github.com/rocjs/roc, documentation.

Roc project components (packages, plugins, templates...)

A little confusing to what is what and how it should be used. A little sparse documentation.

Roc extensions (packages & plugins)

Create a project using one or many Roc extension as a starting point. npm i --save-dev <package> Essentially a predefined collection of npm libraries with minimal and working configuration.

The difference between a package and a plugin is not that big. Plugins are smaller and cannot be used on its own, it adds capabitilites but has no "base". At least on package always needs to be included.

Roc template

Will help you set up a project through interactive CLI. roc init <template> Essentially a wrapper to Roc extensions with interaction.

Artifactory

Not so open source. Needed for most new Roc components.

Setup with variables to be able to use cross projects.

Storybook

Minimal app to run/test/develop React components.

White label theming

New! All web components should use white label theming. Meaning; designed to always take a theme as input to the component. Default theme included in the package, easilly overwritten. Sort of synced with UX DNA.

Reflections building "Notifications"

Truly stand-alone requires some thinking. Do we go full retard?

API integrations a bit messy because of cross site scripting. We should either expose everything via a proxy or find a nice "local proxy" solution.

Not having Redux is a context switch.

Passing parameters to API needs maybe a standard (even if it is ours)

Picking up data from cookies - is it really the best practice?

2017-03-23

• Reference implementation of a "hyperion" app; consuming web components
  /smp-distribution/hyperion-reference

2017-03-21

• Reference implementation of a web component
  /smp-distribution/web-components/
• A step-by-step guide to creating a stand-alone React component using roc-plugin-mono.
  /schibsted-martin/roc-notify/HOWTO.md