Devalloc informational website

This includes deployment and implementation.

As part of sprint-49, here are the startup progress questions:

- Are you on track?
  - Yes? I'm making progress toward a proper launch.
- Are you launched?
  - No
- How many weeks to launch?
  - I would say 4 but it's probably more like 8
- How many (prospective) users have you talked to in the last week?
  - 2, Kyle and his manager, see below
- What have you learned from them?
  - Kyle thought the metrics were interesting.
  - His manager thought the metrics were kinda useful but didn't think they
    really helped people ship higher quality code faster. So that's the rub: I
    have to show how this can make devs ship higher quality code faster; or,
    develop a set of features that improve those things.
  - Kyle pointed out that the clustering feature of devalloc will find optimal
    pairings *and* identify team silos that could be improved, so that's
    important to remember and might be a good angle in the future.
- On a scale of 1-10, what is your morale?
  - 6 maybe
- What most improved your primary metric?
  - Well I was able to deploy something within in the week, whereas before I had
    zero deploys per week. So that's an improvement.
- What is your biggest obstacle?
  - Finding customers to talk to.
  - Also the thing isn't really built yet, I just have a python script. I need
    to build  the real SaaS product
- What are your top 1-3 goals for next week?
  - Find a single customer I can work with on an ongoing basis
    - I should ask around my network to see if I have any second-order
      connections  that would be willing to work with me (Asher, Chad,
      previous bosses, etc)
  - Build out the front-end of the website (it's very simple, would just need a
    basic miso module and deployment)
  - Figure out how to connect/auth to the Github API so I can start building the
    SaaS version of the product

Some user feedback from my friend Kyle. This comes from his engineering manager:

> "Looks neat. If it were priced low enough I could see using it to run reports
> as part of an overall package. A lot of those metrics don't matter too much to
> me as a manager though A lot of these code quality tools are handy info but I
> don't feel like they make people ship code any faster or any higher quality
> Things like CodeClimate work well for Jrs though to avoid obvious static type
> mistakes"

Kyle provided some additional comments:

> he might have been an unusual case. Jared's not big into metrics, Pivotal
> Tracker point estimates, or things like that... He's far more into qualitative
> feedback, like retrospectives and 1:1s
>
> I think it's definitely neat data! I certainly like the collaboration analysis
>
> It's interesting, we recently had a pair where two devs didn't work well
> together, that could be represented here.  Though, we didn't want to avoid
> having them work together, we wanted them to find a work style that worked for
> both of them

And that's a good point: devalloc will find optimal pairings *and* points where
you could improve team cohesiveness.

1 files changed, 95 insertions, 0 deletions

diff --git a/Devalloc/Page/Home.hs b/Devalloc/Page/Home.hs
new file mode 100644
index 0000000..f183881
--- /dev/null
+++ b/Devalloc/Page/Home.hs
@@ -0,0 +1,95 @@
+{-# LANGUAGE OverloadedStrings #-}
+{-# LANGUAGE NoImplicitPrelude #-}
+
+module Devalloc.Page.Home
+  ( Move (..),
+    Path,
+    Form (..),
+    path,
+    view,
+    host,
+  )
+where
+
+import Alpha
+import Biz.App (HtmlApp (..))
+import Miso
+import Miso.String
+import Servant.API
+import Servant.Links
+import Servant.Server (Handler)
+
+data Move = NoMove
+
+type Path = View Move
+
+newtype Form = Form
+  { uri :: URI
+  }
+
+path :: URI
+path = linkURI <| safeLink (Proxy :: Proxy Path) (Proxy :: Proxy Path)
+
+host :: Handler (HtmlApp (View Move))
+host =
+  Form {uri = path}
+    |> view
+    |> HtmlApp
+    |> pure
+
+signup :: View Move
+signup =
+  p_
+    []
+    [ a_
+        [href_ "mailto:ben@bsima.me?subject=Devalloc+signup"]
+        [text "Request access via email"]
+    ]
+
+view :: Form -> View Move
+view _ =
+  div_
+    []
+    [ h1_ [] [text "Devalloc"],
+      p_
+        []
+        [ text
+            "Devalloc analyzes your codebase trends, finds patterns \
+            \ in how your developers work, and protects against tech debt."
+        ],
+      p_ [] [text "Just hook it up to your CI system - it will warn you when it finds a problem."],
+      signup,
+      h2_ [] [text "Identify blackholes in your codebase"],
+      p_
+        []
+        [ text
+            <| Miso.String.intercalate
+              " "
+              [ "What if none of your active employees have touched some part of the codebase?",
+                "This happens too often with legacy code, and then it turns into a huge source of tech debt.",
+                "Devalloc finds these \"blackholes\" and warns you about them so you can be proactive in eliminating tech debt."
+              ]
+        ],
+      h2_
+        []
+        [text "Protect against lost knowledge"],
+      p_
+        []
+        [text "Not everyone can know every part of a codebase. By finding pieces of code that only 1 or 2 people have touched, devalloc identifes siloed knowledge. This allows you to protect against the risk of this knowledge leaving the company if an employee leaves."],
+      h2_
+        []
+        [text "Don't just measure code coverage - also know your dev coverage"],
+      p_
+        []
+        [text "No matter how smart your employees are, if you are under- or over-utilizing your developers then you will never get optimal performance from your team."],
+      ul_
+        []
+        [ li_ [] [text "Find developer hot spots in your code: which pieces of code get continually rewritten, taking up valuable dev time?"],
+          li_ [] [text "Know how your devs work best: which ones have depth of knowledge, and which ones have breadth?"]
+        ],
+      p_ [] [text "(Paid only)"],
+      h2_ [] [text "See how your teams *actually* organize themselves with cluster analysis"],
+      p_ [] [text "Does your team feel splintered or not cohesive? Which developers work best together? Devalloc analyzes the collaboration patterns between devs and helps you form optimal pairings and teams based on shared code and mindspace."],
+      p_ [] [text "(Paid only)"],
+      signup
+    ]