-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathcontribute.html
101 lines (89 loc) · 4.09 KB
/
contribute.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Architectural Katas: Practicing Architecture</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
<meta name="author" content="">
<!-- Le styles -->
<link href="./css/bootstrap.css" rel="stylesheet">
<style>
body {
padding-top: 60px;
padding-bottom: 40px;
}
.sidebar-nav {
padding: 9px 0;
}
</style>
<link href="./css/bootstrap-responsive.css" rel="stylesheet">
<!-- Le HTML5 shim, for IE6-8 support of HTML5 elements -->
<!--[if lt IE 9]>
<script src="//html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
</head>
<body>
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container-fluid">
<a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</a>
<a class="brand" href="#">Architectural Katas</a>
<div class="nav-collapse">
<ul class="nav">
<li><a href="index.html">Home</a></li>
<li><a href="about.html">About</a></li>
<li><a href="rules.html">Rules</a></li>
<li class="active"><a href="contribute.html">Contribute</a></li>
<li><a href="invite.html">Invite</a></li>
<li><a href="lead.html">Lead</a></li>
<li><a href="contact.html">Contact</a></li>
</ul>
</div>
</div>
</div>
</div>
<div class="container-fluid">
<div class="row-fluid">
<div class="span12">
<div class="hero-unit">
<h1>Contribute</h1>
<p>Part of the point of this website is to ensure that the Architectural Katas don't die out
due to lack of creativity on one man's part. Thus, getting community participation into
the kata mindset is kind of important.</p>
<h2>Contribute a Kata idea</h2>
<p>The easiest way to contribute is to take an idea you have for an architectural kata
(whether it's totally made up, a project you heard a buddy of yours working on, or a
project that you yourself are working on) and send it to us. Doing this couldn't be
easier--clone the <a href="https://github.com/tedneward/ArchKatas">GitHub repository
containing all the katas</a> and post a PR. Or, if you don't like the website,
post a PR to the <a href="https://github.com/tedneward/ArchKatasCode">website repo</a>.</p>
<p>Alternatively, you could join the
<a target="_blank" href="http://groups.google.com/group/architecturalkatas">Google Group</a>
and post your kata idea, and we can iterate on it, but the group is pretty quiet and the PR
approach is likely to get faster response. Any kata idea will often need some
iteration/revision, and to protect any intellectual property concerns I often try to change
the domain somewhat as well (if necessary or requested).</p>
<h2>Host an architectural kata gathering</h2>
<p>But if you're more the event-planner type, why not host one? All you need is a room
capable of holding somewhere from 12 to 75 people, with rearrangeable furniture and,
ideally, some whiteboards or notepads and such. If you can do it regularly, we'll
see that you get some kind of Web-link love from this site.</p>
</div>
</div><!--/span-->
</div><!--/row-->
<hr>
<footer>
<p>© Neward & Associates 2012</p>
</footer>
</div><!--/.fluid-container-->
<!-- Le javascript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<script src="./js/jquery-1.7.1.min.js"></script>
</body>
</html>