Install Storybook JS into the docs repo

https://storybook.js.org/

https://github.com/listingslab-software/docs

OSM or Open Source Management is a methodology based on sound Agile concepts

Cut & Paste

• branch feature/17_open-source-management

Cut & Paste

• branch feature/sharky-drivebys

Toggle button which switches on or off the expansion panels in the Navigation component
it's going to need some kind of redux trigger/flag mechanism

.jsx file which takes an object which looks like the json below and renders it using the correct library so it looks noice

{
    title: "A Page Title",
    icon: "icon.svg",
    markdown: '"## Markdown String',
    ...etc,
}

the PWA in the /localify repo is a good place to bootstrap a clean PWA for docsify

• Do the switch
• fix the theme
• edit the config file
• read the config file
• create menu
• route to md pages
• render markdown

Please create a markdown page called md/080_stories.md which describes how to write a good story because

Everything starts with a story, so first thing it to go to GitHub and create one. In the GitHub world it's called and Issue, which makes it sound like a bug, but bugs are a type of issue, not the other way around. Basic rule of thumb is; If you can write a good story, you will get a good outcome

EPIC

Menu & Navigation

.jsx component which wraps the entire Menu/Navigation concept

Requires

• A parser for structure
• a list system the parsed results can slip back into
• a routed solution to trigger the rendering of the correct content

Cut & Paste

• branch feature/18_routing_solution

Requirement

The app works by asynchronously loading markdown files defined in config.json. The MarkDown is then rendered as HTML using the component src/components/Markdown.jsx

The Routing Solution should be created here src/appRouter.js

we also want a new action called goRoute It needs to;

• Replace with the goTo action
• Clear the loaded redux markdown when run
• start loading new markdown
• show a loader
• handle error

• title Working with multiple Git branches
• slug /agile/git/working-with-multiple-branches
• file 010_working-with-multiple-branches.md
• branch feature/010_working-with-multiple-branches

Let's say you are in the middle of doing something on the branch feature/branch1 and you get a new request for something which needs to take priority. How do you successfully shelve the first branch and deliver the new feature?