-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdocs.html
executable file
·742 lines (631 loc) · 26.1 KB
/
docs.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
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
<!DOCTYPE html>
<html class="no-js">
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<meta name="viewport" content="width=device-width,initial-scale=1">
<meta name="title" content="Docs - PhileCMS">
<meta property="og:title" content="Docs - PhileCMS">
<meta name="description" content="PhileCMS - the flat-file PHP CMS">
<meta itemprop="description" content="Docs - PhileCMS - the flat-file PHP CMS">
<meta property="og:description" content="Docs - PhileCMS - the flat-file PHP CMS">
<meta itemprop="url" content="http://philecms.github.io/">
<meta property="og:url" content="http://philecms.github.io/">
<meta property="og:site_name" content="PhileCMS">
<meta property="article:author" content="PhileCMS" />
<meta itemprop="image logo" content="img/phile-logo.png">
<meta property="og:image" content="img/phile-logo.png">
<link href='//fonts.googleapis.com/css?family=Lato:300,400,900' rel='stylesheet' type='text/css'>
<link href="//netdna.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.css" rel="stylesheet">
<link rel="stylesheet" href="css/style.min.css" media="screen" />
<!--[if IE]><script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script><![endif]-->
<title>Docs - Flat-File PHP CMS - PhileCMS</title>
<link rel="shortcut icon" type="image/x-icon" href="favicon.ico">
</head>
<body class="home-page">
<nav class="top-menu section-1">
<div class="grid">
<div class="col-1-3 top-menu-hero">
<p>
<a href="index.html">
<img src="img/phile-logo.svg" alt="phile-logo">
</a>
<span id="pageTitle">
<a href="">Docs
</a>
</span>
</p>
</div>
<div class="col-2-3 top-menu-nav right">
<ul>
<li>
<a href="index.html" class="">
<i class="fa fa-home"></i>
PhileCMS
</a>
</li>
<li>
<a href="wiki/Home.html" class="item-active">
<i class="fa fa-book"></i>
Docs
</a>
</li>
<li>
<a href="api/">
<i class="fa fa-sitemap"></i>
PhpDoc
</a>
</li>
<li>
<a href="https://github.com/PhileCMS/Phile">
<i class="fa fa-github"></i>
Source
</a>
</li>
</ul>
</div>
</div>
</nav>
<div class="container">
<div class="container">
<section id="main_content">
<!-- Content Start -->
<h3 id="creatingcontent">Creating Content</h3>
<p>Phile is a flat file CMS, this means there is no administration backend and database to deal with. You simply create <code>.md</code> files in the “content”
folder and that becomes a page. For example, this file is called <code>index.md</code> and is shown as the main landing page.</p>
<p>If you create a folder within the content folder (e.g. <code>content/sub</code>) and put an <code>index.md</code> inside it, you can access that folder at the URL
<code>http://yousite.com/sub</code>. If you want another page within the sub folder, simply create a text file with the corresponding name (e.g. <code>content/sub/page.md</code>)
and you will be able to access it from the URL <code>http://yousite.com/sub/page</code>. Below we’ve shown some examples of content locations and their corresponding URL’s:</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">Physical Location</th>
<th style="text-align:left;">URL</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;">content/index.md</td>
<td style="text-align:left;">/</td>
</tr>
<tr>
<td style="text-align:left;">content/sub.md</td>
<td style="text-align:left;">/sub</td>
</tr>
<tr>
<td style="text-align:left;">content/sub/index.md</td>
<td style="text-align:left;">/sub (same as above)</td>
</tr>
<tr>
<td style="text-align:left;">content/sub/page.md</td>
<td style="text-align:left;">/sub/page</td>
</tr>
<tr>
<td style="text-align:left;">content/a/very/long/url.md</td>
<td style="text-align:left;">/a/very/long/url</td>
</tr>
</tbody>
</table>
<p>If a file cannot be found, the file <code>content/404.md</code> will be shown.</p>
<h3 id="textfilemarkup">Text File Markup</h3>
<p>Text files are marked up using <a href="http://daringfireball.net/projects/markdown/syntax">Markdown</a>. They can also contain regular HTML.</p>
<p>At the top of text files you can place a block comment and specify certain attributes of the page. For example:</p>
<pre><code class="markdown">
/*
Title: Welcome
Description: This description will go in the meta description tag
Author: Joe Bloggs
Date: 2013/01/01
Robots: noindex,nofollow
*/
</code></pre>
<p>Phile also allows HTML or YAML style block comments:</p>
<pre><code>
<!--
Title: Welcome
…
-->
</code></pre>
<pre><code>
---
Title: Welcome
…
---
</code></pre>
<h4 id="custommeta">Custom Meta</h4>
<p>You can create custom meta attributes by default in Phile. If you want to add a date, author, or even something else, this can be done easily. These values will be contained in the <code>{{ meta }}</code> variable in themes (see below).</p>
<h4 id="custommetaordering">Custom Meta Ordering</h4>
<p>You can order pages by their custom meta attributes. Like creating an <code>Order</code> meta for each page, then you can use <code>$config['pages_order'] = "meta.order:asc";</code> in your <code>config.php</code> file.</p>
<h3 id="themes">Themes</h3>
<p>You can create themes for your Phile installation in the “themes” folder. Check out the default theme for an example of a theme. Phile uses
<a href="http://twig.sensiolabs.org/documentation">Twig</a> for it’s templating engine. You can select your theme by setting the <code>$config['theme']</code> variable
in config.php to your theme folder.</p>
<p>All themes must include an <code>index.html</code> file to define the HTML structure of the theme. Below are the Twig variables that are available to use in your theme:</p>
<ul>
<li><code>{{ config }}</code> - Contains the values you set in config.php (e.g. <code>{{ config.theme }}</code> = “default”)</li>
<li><code>{{ base_dir }}</code> - The path to your Phile root directory</li>
<li><code>{{ base_url }}</code> - The URL to your Phile site</li>
<li><code>{{ theme_dir }}</code> - The path to the Phile active theme directory</li>
<li><code>{{ theme_url }}</code> - The URL to the Phile active theme directory</li>
<li><code>{{ content_dir }}</code> - The path to the content direcotry</li>
<li><code>{{ content_url }}</code> - The URL to the content directory</li>
<li><code>{{ site_title }}</code> - Shortcut to the site title (defined in config.php)</li>
<li><code>{{ meta }}</code> - Contains the meta values from the current page</li>
<li><code>{{ meta.title }}</code></li>
<li><code>{{ meta.description }}</code></li>
<li><code>{{ content }}</code> - The content of the current page (after it has been processed through Markdown)</li>
<li><code>{{ pages }}</code> - A collection of all the content in your site</li>
<li><code>{{ page.title }}</code></li>
<li><code>{{ page.url }}</code></li>
<li><code>{{ page.content }}</code></li>
<li><code>{{ current_page }}</code> - A page object of the current_page</li>
</ul>
<p>Page listing example:</p>
<pre><code class="html"><ul class="nav">
{% for page in pages %}
<li><a href="{{ page.url }}">{{ page.title }}</a></li>
{% endfor %}
</ul>
</code></pre>
<h3 id="config">Config</h3>
<p>You can override the default Phile settings (and add your own custom settings) by editing config/config.php. The config.php file
lists all of the settings and their defaults. To override a setting, simply uncomment it in config.php and set your custom value.</p>
<h3 id="events">Events</h3>
<p>In the core we trigger a lot of events, which help to manipulate content or other stuff within a plugin.
To use the event system, you only have to register your plugin for a specific event, look at the example plugin for more an example.</p>
<p>The following list shows all events.</p>
<h4 id="plugins_loaded">plugins_loaded</h4>
<p>this event is triggered after the plugins loaded</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>plugins</code></td>
<td style="text-align:left;">array</td>
<td style="text-align:left;"><code>Plugin</code> classes of all loaded plugins</td>
</tr>
</tbody>
</table>
<h4 id="config_loaded">config_loaded</h4>
<p>this event is triggered after the configuration is fully loaded</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>config</code></td>
<td style="text-align:left;">array</td>
<td style="text-align:left;">the complete configuration</td>
</tr>
</tbody>
</table>
<h4 id="after_init_core">after_init_core</h4>
<p>this event is triggered after the core is initialized</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>response</code></td>
<td style="text-align:left;">\Phile\Core\Response</td>
<td style="text-align:left;">the response, set a PSR–7 response to send output early</td>
</tr>
</tbody>
</table>
<h4 id="request_uri">request_uri</h4>
<p>this event is triggered after the request uri is detected.</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>uri</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the requested uri (without install_path)</td>
</tr>
<tr>
<td style="text-align:left;"><code>response</code></td>
<td style="text-align:left;">Psr\Http\Message\ResponseInterface</td>
<td style="text-align:left;">set a PSR–7 response to send output early</td>
</tr>
</tbody>
</table>
<h4 id="after_404">after_404</h4>
<p>this event is triggered after a requested page is not found</p>
<h4 id="after_resolve_page">after_resolve_page</h4>
<p>this event is triggered after a request is resolved to a page</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>pageId</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the requested page-ID</td>
</tr>
<tr>
<td style="text-align:left;"><code>page</code></td>
<td style="text-align:left;">Phile\Model\Page</td>
<td style="text-align:left;">the page served</td>
</tr>
<tr>
<td style="text-align:left;"><code>response</code></td>
<td style="text-align:left;">Psr\Http\Message\ResponseInterface</td>
<td style="text-align:left;">set a PSR–7 response to send output early</td>
</tr>
</tbody>
</table>
<h4 id="before_init_template">before_init_template</h4>
<p>this event is triggered before the the template engine is init</p>
<h4 id="before_render_template">before_render_template</h4>
<p>this event is triggered before the template is rendered</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>templateEngine</code></td>
<td style="text-align:left;">\Phile\Template\TemplateInterface</td>
<td style="text-align:left;">the template engine</td>
</tr>
<tr>
<td style="text-align:left;"><code>response</code></td>
<td style="text-align:left;">Psr\Http\Message\ResponseInterface</td>
<td style="text-align:left;">set a PSR–7 response to send output early</td>
</tr>
</tbody>
</table>
<h4 id="template_engine_registered">template_engine_registered</h4>
<p>this event is triggered before the template is rendered</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>engine</code></td>
<td style="text-align:left;">\Phile\Template\TemplateInterface</td>
<td style="text-align:left;">the raw template engine</td>
</tr>
<tr>
<td style="text-align:left;"><code>data</code></td>
<td style="text-align:left;">array</td>
<td style="text-align:left;">the variables being sent to the template engine</td>
</tr>
</tbody>
</table>
<h4 id="after_render_template">after_render_template</h4>
<p>this event is triggered after the template is rendered</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>templateEngine</code></td>
<td style="text-align:left;">\Phile\Template\TemplateInterface</td>
<td style="text-align:left;">the template engine</td>
</tr>
<tr>
<td style="text-align:left;"><code>output</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the parsed and ready output</td>
</tr>
</tbody>
</table>
<h4 id="before_read_file_meta">before_read_file_meta</h4>
<p>this event is triggered before the meta data is read and parsed</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>rawData</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the unparsed data</td>
</tr>
<tr>
<td style="text-align:left;"><code>meta</code></td>
<td style="text-align:left;">\Phile\Model\Meta</td>
<td style="text-align:left;">the meta model</td>
</tr>
</tbody>
</table>
<h4 id="after_read_file_meta">after_read_file_meta</h4>
<p>this event is triggered after the meta data is read and parsed</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>rawData</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the unparsed data</td>
</tr>
<tr>
<td style="text-align:left;"><code>meta</code></td>
<td style="text-align:left;">\Phile\Model\Meta</td>
<td style="text-align:left;">the meta model</td>
</tr>
</tbody>
</table>
<h4 id="before_load_content">before_load_content</h4>
<p>this event is triggered before the content is loaded</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>filePath</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the path to the file</td>
</tr>
<tr>
<td style="text-align:left;"><code>page</code></td>
<td style="text-align:left;">\Phile\Model\Page</td>
<td style="text-align:left;">the page model</td>
</tr>
</tbody>
</table>
<h4 id="after_load_content">after_load_content</h4>
<p>this event is triggered after the content is loaded</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>filePath</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the path to the file</td>
</tr>
<tr>
<td style="text-align:left;"><code>rawData</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the raw data</td>
</tr>
<tr>
<td style="text-align:left;"><code>page</code></td>
<td style="text-align:left;">\Phile\Model\Page</td>
<td style="text-align:left;">the page model</td>
</tr>
</tbody>
</table>
<h4 id="before_parse_content">before_parse_content</h4>
<p>this event is triggered before the content is parsed</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>content</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the raw data</td>
</tr>
<tr>
<td style="text-align:left;"><code>page</code></td>
<td style="text-align:left;">\Phile\Model\Page</td>
<td style="text-align:left;">the page model</td>
</tr>
</tbody>
</table>
<h4 id="after_parse_content">after_parse_content</h4>
<p>this event is triggered after the content is parsed</p>
<table>
<colgroup>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
<col style="text-align:left;"/>
</colgroup>
<thead>
<tr>
<th style="text-align:left;">param</th>
<th style="text-align:left;">type</th>
<th style="text-align:left;">description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align:left;"><code>content</code></td>
<td style="text-align:left;">string</td>
<td style="text-align:left;">the raw data</td>
</tr>
<tr>
<td style="text-align:left;"><code>page</code></td>
<td style="text-align:left;">\Phile\Model\Page</td>
<td style="text-align:left;">the page model</td>
</tr>
</tbody>
</table>
<!-- Content End -->
<h2 id="service-_locator">Service Locator</h2>
<p>Within in the core we use a lot of service class, which will be received over the ServiceLocator class. This makes it possible to replace a service with a complete new logic. In the following section, we tell you, which service classes available and how to replace a service with your own.</p>
<h3>Service: Phile_Parser</h3>
<p>You can replace the markdown parser with your own parser, if you like. This works by overloading the default parser with a plugin. To show you, check out the Markdown plugin that comes with Phile. Or, take a look at the <a href="https://github.com/PhileCMS/Sundown-Parser-Plugin">Sundown-Parser-Plugin</a>.</p>
<p>To replace the parser, you need only one line of code to register a new parser:</p>
<p><code>\Phile\ServiceLocator::registerService('Phile_Parser', new \Phile\Parser\Sundown($this->settings));</code></p>
<h3>Service: Phile_Parser_Meta</h3>
<p>You can override the meta data parser with your own. The default parser handles meta in either a HTML block comment or a Javascript/PHP block comment. If you wanted to support YAML, this would be the service you would override.</p>
<h3>Service: Phile_Template</h3>
<p>The template engine is also a service, you can replace the default template engine (twig) with your own. The way you can do this, is the same like the Phile_Parser:</p>
<p><code>\Phile\ServiceLocator::registerService('Phile_Template', new \Phile\Template\MyTemplateEngine());</code></p>
<h3>Service: Phile_Cache</h3>
<p>Internal PhileCMS use an object cache to improve the performance. however if you want another cache system, register your own:</p>
<p><code>\Phile\ServiceLocator::registerService('Phile_Cache', new \Phile\Cache\MyCacheEngine());</code></p>
<h3>Service: Phile_Data_Persistence</h3>
<p>Yes, Phile works without any database, but if you need the possiblity to persist data, you can use the Phile_Data_Persistence service. with the core we provide you a simple file based data storage, you can implement your own or maybe found a plugin with another storage engine, replace it like this:</p>
<p><code>\Phile\ServiceLocator::registerService('Phile_Data_Persistence', new \Phile\Persistence\MyPersistenceEngine());</code></p>
</section>
</div>
</div>
<div class="clearfix"></div>
<footer class="section-1">
<div class="grid">
<div class="col-1-2">
<h3>
<a href="https://github.com/orgs/PhileCMS/people">
Core Authors
</a>
</h3>
<ul>
<li>
<a href="https://github.com/james2doyle" target="_blank">
James Doyle - great ideas, code a lot of plugins and worked on the
core
</a>
</li>
<li>
<a href="https://github.com/NeoBlack" target="_blank">
Frank Nägler - refactoring of the core and introducing OOP concepts
</a>
</li>
<li>
<a href="https://github.com/Schlaefer" target="_blank">
Schlaefer
</a>
</li>
</ul>
</div>
<div class="col-1-2 center">
<p>
<a href="https://github.com/PhileCMS">
Hosted on Github. Maintained by the PhileCMS community</a>.
</p>
</div>
</div>
</footer>
<script src="js/script.min.js"></script>
</body>
</html>