Home.md
... ...
@@ -8,18 +8,15 @@ started looking like Design Patterns. So in the tradition of the original
8 8
[WikiWikiWeb](https://www.c2.com) we decided to create a pattern repository that
9 9
we could grow and evolve over time.
10 10
11
-Thus Tea Garden was born. Eventually, it is our goal to grow a friendly and
12
-useful garden of knowledge, something you can come and enjoy if you have a spare
13
-moment to learn a new concept, or pluck a few useful morsels from the next time
14
-you are starting a new project. We also want to create a home on the web for
15
-these patterns, a place to point to to quickly get others up to speed about what
16
-you are talking about.
17
-
18
-We will publish a companion newsletter, _Tea Leaves_, whenever there is
19
-something of note to highlight. We will let you know when interesting new
20
-patterns appear, or alert you about existing patterns that have seen significant
21
-edits, together with commentary and insights, so you can find out what's on our
22
-mind, and why we're writing about certain patterns at a given time.
11
+Thus Tea Garden was born. It is our goal to grow a friendly and useful garden of
12
+knowledge, something you can come browse and learn from. We also want to create
13
+a home on the web for these patterns, a place to point to to quickly get others
14
+up to speed about what you are talking about.
15
+
16
+We publish a companion newsletter, _Tea Leaves_. In it we let you know when
17
+interesting new patterns appear, or alert you about existing patterns that have
18
+seen significant edits, together with commentary and insights, so you can find
19
+out what's on our mind, and why we're writing about certain patterns.
23 20
24 21
<!-- Ghost sign up form, see https://gaiwan.co/ghost/#/settings/embed-signup-form/show -->
25 22
<!-- see custom.js -->
... ...
@@ -34,13 +31,13 @@ see us cover, or just any random pattern-related chat.
34 31
## A Pattern Language
35 32
36 33
The patterns in this wiki together form [A Pattern Language](PatternLanguage),
37
-we recommend starting [there](PatternLanguage) to understand what we mean exactly when we say
38
-"Pattern" or "Pattern Language".
34
+we recommend starting [there](PatternLanguage) to understand what we mean
35
+exactly when we say "Pattern" or "Pattern Language".
39 36
40 37
Patterns exist to resolve tensions, so any exploration of a pattern must start
41
-with an exploration of the tensions which are present. A good problem statement
42
-is always the hardest part, after that we can consider solutions. When it comes
43
-to documenting patterns, we try to separate three different aspects.
38
+with an exploration of the tensions which are present. Finding good solutions
39
+starts with a good problem statement. When it comes to documenting patterns, we
40
+try to separate three different aspects.
44 41
45 42
1. **The Pattern itself** This is an abstract description of the tensions that the
46 43
pattern seeks to resolve, and how it resolves them. We try to document the
custom.css
... ...
@@ -10,3 +10,7 @@ h1,h2,h3,h4,h5 { font-family: Railway, sans-serif; }
10 10
font-size: 17px;
11 11
font-family: Alice, serif;
12 12
}
13
+
14
+.gh-signup-root {
15
+ height: 200px;
16
+}