geet-geet 0.2.0 → 0.3.0

package/README.md

@@ -9,7 +9,7 @@ Only Git's *view* of the filesystem changes.
 
 ## Why?
 >   “I built something useful, and I think that **SOME but not all of my code is re-usable**.
-    I want to publish some of my code for other's to use (or to re-use myself)...
+    I want to publish some of my code for others to use (or to re-use myself)...
     but **I don't want to spend weeks refactoring** to split apart the reusable code from the implementation-specific code.
     In fact, it may not even be possible to move around all my files without breaking things. 
     Plus, supporting this template is my **secondary task** which I want to do in tandem with my **primary development**, using my main repository's working directory and publishing some pieces to the template repo.”

package/lib/why.sh

@@ -5,23 +5,33 @@
 #   whynot
 
 why() {
-cat <<'EOF'
-Why use geet?
+printf '%b' "$(cat <<'EOF'
+Use geet if this resonates with you...
+\033[3m
+   "I built something useful, and I think that SOME but not all of my code is re-usable.
+    I want to publish some of my code for others to use (or to re-use myself)...
+    but I don't want to spend weeks refactoring to split apart the reusable code from the implementation-specific code.
+    In fact, it may not even be possible to move around all my files without breaking things.
+    Plus, supporting this template is my secondary task which I want to do in tandem with my primary development,
+    using my main repository's working directory and publishing some pieces to the template repo."
+
+\033[0m
 
-I built something useful, and I think that SOME but not all of my code is re-usable.
-I want to publish some of my code for other's to use (or to re-use myself)...
-but I don't want to spend weeks refactoring to split apart the reusable code from the implementation-specific code.
-In fact, it may not even be possible to move around all my files without breaking things.
-Plus, supporting this template is my secondary task which I want to do in tandem with my primary development,
-using my main repository's working directory and publishing some pieces to the template repo.
 EOF
+)"
+
 }
 
 whynot() {
-cat <<'EOF'
-Why NOT use geet?
+printf '%b' "$(cat <<'EOF'
+As much as I love this package, it is not for every use case...
+\033[3m
+    You probably do not need geet if you can super cleanly separate your template from your app or make your source code fully modular.
+    If you can use a package distribution like pypi or npm that is probably best. If git submodules work for you, that is good too.
+    If those solutions are not working for you, then check back here.
+
+\033[0m
 
-If you can super cleanly separate your template from your app or make your sourcecode fully modular,
-you don't need geet, use a normal repo or maybe submodules.
 EOF
+)"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "geet-geet",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "private": false,
   "bin": {
     "geet": "bin/geet.sh",