-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
198 lines (183 loc) · 9.14 KB
/
index.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
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
<meta http-equiv="X-UA-Compatible" content="ie=edge">
<title>Eole Project</title>
<link rel="stylesheet" href="http://fonts.googleapis.com/css?family=Montserrat:400,700" type="text/css">
<link rel="stylesheet" href="bower_components/components-font-awesome/css/font-awesome.min.css" type="text/css">
<link rel="stylesheet" href="bower_components/tether/dist/css/tether.min.css">
<link rel="stylesheet" href="bower_components/bootstrap/dist/css/bootstrap.min.css">
<link rel="stylesheet" href="css/all.css">
</head>
<body>
<header>
<div class="jumbotron">
<div class="container">
<h1 class="display-3">Eole</h1>
</div>
</div>
</header>
<div class="container">
<section>
<h2>What is Eole ?</h2>
<p class="lead text-xs-center elevator-spitch">
<span class="bigger-1">Eole</span> is an online <span class="bigger-3">board games website</span>
for people who <span class="bigger-3">want to play</span>
to their favorite board game, but don't find
an <span class="bigger-2">online version of the game</span>.
</p>
<p class="lead text-xs-center">
<a class="btn btn-success" href="http://eole-io.github.io/eole-angular/">
<i class="fa fa-gamepad fa-lg" aria-hidden="true"></i>
Demo application
</a>
</p>
<p>
It is an <strong>open-source project</strong>, and a <strong>free web application</strong>.
</p>
<p>
It aims to be an oasis for both <strong>board game players</strong> and <strong>developers</strong>.
</p>
</section>
<section>
<h2>Project News</h2>
<div class="row">
<div class="col-md-6">
<article class="card">
<div class="card-block">
<h4 class="card-title">Sandstone release</h4>
<time pubdate="pubdate" datetime="2016-06-17" class="text-muted">17th June, 2016</time>
<p>
Eole Api uses an extended version of Silex which nicely handle websocket topics,
push server based on ZMQ... So I decided to "extract" this component
as a standalone library. I named it Sandstone, it is open-source,
and it is on Github.
</p>
<p class="text-xs-center">
<a href="https://github.com/eole-io/sandstone" class="btn btn-primary text-lg-center">
<i class="fa fa-github fa-lg" aria-hidden="true"></i>
Eole/Sandstone
</a>
</p>
</div>
</article>
</div>
</div>
</section>
<section>
<h2>Architecture</h2>
<p>
As is, Eole is just a game platform,
and provides (or will provides in futur)
features like:
</p>
<ul>
<li>creating a game,</li>
<li>waiting for people to join your game,</li>
<li>real-time playing,</li>
<li>creating an account,</li>
<li>chat room,</li>
<li>organizing tournaments,</li>
<li>poker chips for bet games,</li>
<li>ranking system with Elo, win/loss/draw...</li>
</ul>
<p>
The project consists on a PHP Rest Api, working together with a websocket server for real-time notifications,
and a front-side AngularJS application.
</p>
<div class="card-deck-wrapper">
<div class="card-deck">
<div class="card">
<h4 class="card-header">
Eole Api
</h4>
<div class="card-block">
<p class="card-text">
The Api provides a Rest Api
and a websocket server for real-time notification
(i.e a player made a move).
</p>
<p class="card-text">
It is built with following technologies/libraries:
</p>
<ul>
<li>PHP 5.5</li>
<li>Symfony</li>
<li>Silex 2, <a href="https://github.com/eole-io/sandstone">Sandstone</a></li>
<li>ReactPHP</li>
<li>WAMP v1 protocol</li>
<li>php-zmq extension</li>
<li>ZMQ</li>
</ul>
<p class="card-text">
<a class="btn btn-primary" href="https://github.com/eole-io/eole-api">
<i class="fa fa-github fa-lg" aria-hidden="true"></i>
See project on Github
</a>
</p>
<small class="text-muted">License GNU GPL-v3</small>
</div>
</div>
<div class="card">
<h4 class="card-header">
Eole Angular
</h4>
<div class="card-block">
<p class="card-text">
The AngularJS project provides a front-side application.
</p>
<p class="card-text">
It is built with following technologies/libraries:
</p>
<ul>
<li>Javascript</li>
<li>AngularJS 1</li>
<li>Bootstrap 3</li>
<li>Autobahn 0.8</li>
</ul>
<p class="card-text">
<a class="btn btn-primary" href="https://github.com/eole-io/eole-angular">
<i class="fa fa-github fa-lg" aria-hidden="true"></i>
See project on Github
</a>
</p>
<small class="text-muted">License GNU GPL-v3</small>
</div>
</div>
</div>
</div>
</section>
<section>
<h2>Extendability</h2>
<p>
Eole architecture allows to be extended easily by adding:
</p>
<ul>
<li>more endpoints for RestApi,</li>
<li>more topics for websocket server</li>
<li>and more AngularJS modules for web application.</li>
</ul>
<p>
So games can be developed independently of Eole domain and components,
and then just create a layer/bridge to extend Eole with your game endpoints, topics...
</p>
</section>
</div>
<footer class="footer">
<div class="container">
<p class="text-muted text-xs-center">And then the footer...</p>
<p class="text-xs-center">
<a href="https://github.com/eole-io" class="btn btn-success">
<i class="fa fa-github fa-lg" aria-hidden="true"></i>
Eole Github organization
</a>
</p>
</div>
</footer>
<script src="bower_components/tether/dist/js/tether.min.js"></script>
<script src="bower_components/jquery/dist/jquery.min.js"></script>
<script src="bower_components/bootstrap/dist/js/bootstrap.min.js"></script>
</body>
</html>