Document what we found in closed issues:

• #214 (shelljs)
• #217 (nodemon) -- Note: Adding --raw seems to solve the issue.
• (potentially) #218 (concurrently)

As part of clarifying what is part of the open source offering and what is examples or private code, we should signal these differences using package names/namespaces.

Suggested solution:

• Let all public, published packages retain their @backstage namespace.
• Change all private packages in the open source project (plugins/home-page, plugins/welcome) to be under an @internal names

Hello there,

I really loved the idea of Crana and i want to contribute as much as i can. I believe that the most funtumental thing about a project is how you present it to the public.

So what do you think about developing a simple website with documentation, maybe with docsify, docusaurous, docz or a similar framework-generator or even a custom made minimalistic site?

Comment your thoug

check if dupe package names in same folder cause issues - write a test that should capture this problem, only resolution is to ignore the path/folder that contains the dupe package(s).

1. suman should link global to local if local suman copy does not exist.

2. suman should link a project to itself, if configuration tells it to do so.

include naming convention for containers and loadable components as well as the dir structure following the component owner-ownee relationship and the use of 'lib'.

• don't duplicate usage of commands in readme, just refer users to the -h flag. no, better yet, auto-generate README.md with a script (gen-doc.sh?)
• write an overview of the git-flux model, specifically the levels.
• elaborate on teams and the ability to switch teams with the join action
• state the fact that git-flux addresses some of the issues in git-flow (e.g. we never use `--no-

Expected Behavior

I should be able to just select an object with the log effect and have it automatically know if it is not a string and then it should turn it into one with stringify.

Current Behavior

Right now it just prints something like [Object object] which is not useful at all and means that I have to have a step that explicitly converts it to a string. It should be easier to l