Elm is complaining about name convention

A module must be CamelCase, a module line must come **before** the comments (documentation), and removing some files that Elm creates.

Author: badlydrawnrob

Diff for: elm-in-action/.gitignore

@@ -1 +1,6 @@
-__ANKI__
+__ANKI__
+
+# elm-package generated files
+elm-stuff
+# elm-repl generated files
+repl-temp-*

Diff for: elm-in-action/02/notes/notes.elm

@@ -5,7 +5,33 @@
 
 -- 2.1.1
 
--- HTML is shorthand for "virtual DOM node"
+-- Filename conventions --
+-- Although I prefer lisp's (kebab-case ...), in Elm you
+-- MUST be `CamelCase`. Variables should also be `camelCase`. 
+-- : @ https://en.wikipedia.org/wiki/Camel_case
+-- : @ https://elmprogramming.com/constant.html
+-- : @ http://tinyurl.com/programming-cases
+--
+-- : 🚫 `src/photo-groove.elm` wrong naming convention
+-- : I expect all files follow module naming convention:
+--
+--   | Module name  | File Path          |
+--   |--------------|--------------------|
+--   | Main         | ./Main.elm         |
+--   | HomePage     | ./HomePage         |
+--   | Http.Helpers | ./Http/Helpers.elm |
+
+
+-- Documentation and comments --
+--
+-- Module declaration _must come before_ `module` statement.
+-- Repeat! DO NOT put comments before `module` statement:
+--
+-- : @ https://package.elm-lang.org/help/documentation-format
+
+
+-- Working with the Document Object Model (DOM)
+-- HTML is shorthand for "virtual DOM node" ...
 -- : We generally don't use `node` directly, but use the HTML elements
 --   such as `img`, `button`, so on.
 -- : The following two lines are equivalent:
@@ -17,6 +43,7 @@ node "img" [ src "logo.png" ] []
 --   fall back on `node` only when no alternative is available.
 
 -- Commas --
+-- Commas first takes some getting used to, but ...
 -- : 🚫 Beware of mistakes!
 -- : It's best to have commas at the start of the line, as lines can be mistaken
 --   for syntactically valid Elm code — but NOT the code you intended to write.
@@ -35,3 +62,40 @@ rules = [
 ]
 
 -- Instead of 3 distinct lines.
+-- : instead of calling `rule` 3 times, with one argument,
+--   the second call to `rule` is receiving 3 arguments.
+
+rules = [
+  rule "Do not ..."
+  rule "Do NOT"            -- I'm missing a comma!
+  , rule "No eating ..."
+]
+
+-- The above commas first is easier to check mistakes.
+
+
+-- More on the DOM structure --
+-- The PhotoGroove module will render a basic DOM
+--
+-- : The functions that create elements — in this case, div, h1, and img
+--   take exactly _two arguments_ in all cases:
+--
+--   1. A list of attributes (or an empty `[]` list)
+        h1 [] [ text "Photo Groove" ]
+--   2. A list of _child DOM nodes_ (or an empty `[]` list)
+        img [ src "1.jpeg" ] []
+-- : If an element has neither attributes nor children?
+        br [] []
+
+
+-- Qualified -vs- unqualified style
+--
+-- `String.filter` (qualified style)
+-- : Uses the module's name here and now.
+--
+-- `import HTML exposing (div, h1, img, text)` allows for:
+-- : Using `div` instead of `Html.div`
+--   (this is an unqualified style.)
+--
+-- We can use unqualified style when we _expose_ the module.
+-- It imports the module, and exposes `Html.function`

Diff for: elm-in-action/02/src/photo-groove.elm renamed to elm-in-action/02/src/PhotoGroove.elm

@@ -1,3 +1,5 @@
+module PhotoGroove exposing (main)
+
 {-| Beginning our Elm app:
     Photo Groove!
 
@@ -15,10 +17,7 @@
     : Only exposed values can be accessed by other modules.
       As a general rule, it's best for our modules to expose
       _as little as possible_.
-|-}
-
--- #1
-module PhotoGroove exposing (main)
+-}
 
 -- #2
 import Html exposing (div, h1, img, text)
@@ -34,3 +33,6 @@ view model =
       , img [ src "http://elm-in-action.com/3.jpeg" ] []
       ]
     ]
+
+main =
+  view "no model yet"