Skip to content

Commit 7e98ba4

Browse files
memphysmemphys
committed
Fix #2: updated main page and README
1 parent 937eebd commit 7e98ba4

File tree

3 files changed

+84
-25
lines changed

3 files changed

+84
-25
lines changed

Diff for: ‎README.md

+28-22
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,35 @@
1-
ZCE-guide is a small project that provides step by step guide on information needed to pass PHP5.3 ZCE certification: [http://www.zend.com/en/services/certification/php-5-certification/](http://www.zend.com/en/services/certification/php-5-certification/).
1+
# PHP Study Guide
22

3-
Also, it is a good place to start your experience with PHP5.3 or, if you are already an experienced web developer, to return to the basics and remember some details.
3+
## What?
44

5-
Project uses [Jekyll](https://github.com/mojombo/jekyll) (blog-aware, static site generator in Ruby) with some staff from [Jekyll Bootstrap](http://jekyllbootstrap.com) and is hosted with [GitHub Pages](http://pages.github.com/).
5+
Originally PHP Study Guide was a small project that provides step by step guide on information needed to pass PHP5.3 ZCE certification: [http://www.zend.com/en/services/certification/php-5-certification/](http://www.zend.com/en/services/certification/php-5-certification/).
66

7-
If you want to contribute, please, read the following guide.
7+
For now it aims to go little bit beyond the Zend Certification and is a good place to start your experience with PHP5.3 or, if you are already an experienced web developer, to return to the basics and remember some details.
88

9-
# How to contribute
9+
## Where?
1010

11-
## Workflow
11+
At the moment project is placed at <http://zce.evercodelab.com/> and hosted on [GitHub.Pages](http://pages.github.com).
1212

13-
In general, all development happens in master and topic branches. When changes are ready for publishing they are merged into gh-pages. GitHub processes new content and then automatically publishes it.
13+
## Sources
14+
15+
All content is assembled from different sources and tutorials.
16+
17+
* Zend PHP 5.0 Certification Course by Paul Reinheimer
18+
* Zend PHP 5 Certification Study Guide
19+
* Zend PHP 5.3 Study Guide v1
20+
* [Read The Web Blog](http://readtheweb.info/index.php?s=Zend+PHP+5+Certification+Exam&submit=Go)
21+
* <http://www.php.net/manual/en/>
22+
* <http://zend-php.appspot.com/>
23+
24+
Original guide was structured in Google Docs and then published as [pdf](http://victimofbabylon.com/zce-php-53-study-guide).
25+
26+
## Who?
27+
28+
Mainly project is done by me, [Roma Lapin](https://github.com/memphys) and supported by [Evercode Lab](http://www.evercodelab.com/).
29+
30+
## How to contribute
31+
32+
At first all content was assembled to be used for PHP5.3 ZCE certification. So it aimed to be short and kind of limited. For now feel free to contribute to it. All suggestions to content and design is appreciated.
1433

1534
In order to contribute, please, do the following.
1635

@@ -31,20 +50,7 @@ Pygments is used for code highlighting.
3150

3251
Each page should have following variables in YAML Front Matter:
3352

34-
* title – post/page title
53+
* title – page title
3554
* layout - usually it is "page"
3655

37-
Menu is written in `_includes/menu.html`.
38-
39-
## Content
40-
41-
Original guide was structured in Google Docs and then published as [pdf](http://victimofbabylon.com/zce-php-53-study-guide). While the content transfer is happening, original doc is [available for anybody](https://docs.google.com/document/d/1GiLHFPV9dvLLsQfPj1f0WzYD1kBZ_EdAhspcxEEMWys/edit).
42-
43-
In order to help transfer contents from doc to this guide, please, do the following:
44-
45-
* Choose subsection to transfer
46-
* Create an issue with subsection title in it and state that you are working on it.
47-
* Format content using markdown as described earlier
48-
* Send Pull Request
49-
* Profit!
50-
56+
Menus is stored in `_includes/menu`.

Diff for: ‎_config.yml

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
title: PHP study guide
1+
title: PHP Study Guide
22
auto: true
33
pygments: true
44
# markdown: rdiscount

Diff for: ‎index.md

+55-2
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,60 @@
11
---
22
layout: page
3-
title: Main page
3+
title: PHP Study Guide
44
---
55
{% include JB/setup %}
66

7-
Here will be some content soon!
7+
## What?
8+
9+
Originally PHP Study Guide was a small project that provides step by step guide on information needed to pass PHP5.3 ZCE certification: [http://www.zend.com/en/services/certification/php-5-certification/](http://www.zend.com/en/services/certification/php-5-certification/).
10+
11+
For now it aims to go little bit beyond the Zend Certification and is a good place to start your experience with PHP5.3 or, if you are already an experienced web developer, to return to the basics and remember some details.
12+
13+
## Where?
14+
15+
At the moment project is placed at <http://zce.evercodelab.com/> and hosted on [GitHub.Pages](http://pages.github.com).
16+
17+
## Sources
18+
19+
All content is assembled from different sources and tutorials.
20+
21+
* Zend PHP 5.0 Certification Course by Paul Reinheimer
22+
* Zend PHP 5 Certification Study Guide
23+
* Zend PHP 5.3 Study Guide v1
24+
* [Read The Web Blog](http://readtheweb.info/index.php?s=Zend+PHP+5+Certification+Exam&submit=Go)
25+
* <http://www.php.net/manual/en/>
26+
* <http://zend-php.appspot.com/>
27+
28+
Original guide was structured in Google Docs and then published as [pdf](http://victimofbabylon.com/zce-php-53-study-guide).
29+
30+
## Who?
31+
32+
Mainly project is done by me, [Roma Lapin](https://github.com/memphys) and supported by [Evercode Lab](http://www.evercodelab.com/).
33+
34+
## How to contribute
35+
36+
At first all content was assembled to be used for PHP5.3 ZCE certification. So it aimed to be short and kind of limited. For now feel free to contribute to it. All suggestions to content and design is appreciated.
37+
38+
In order to contribute, please, do the following.
39+
40+
* [Fork the project](http://help.github.com/fork-a-repo/)
41+
* Clone down your fork
42+
* Create a topic branch to contain your change ( git checkout -b my_awesome_feature )
43+
* Add some code
44+
* Push the branch up ( git push origin my_awesome_feature )
45+
* [Send a Pull Request](http://help.github.com/send-pull-requests/)
46+
47+
## Project layout and details
48+
49+
On the whole project follows standart [jekyll project layout](https://github.com/mojombo/jekyll/wiki/usage).
50+
51+
Each certification section is presented as page in `pages` directory. Each subsection is a part of a page.
52+
53+
Pygments is used for code highlighting.
54+
55+
Each page should have following variables in YAML Front Matter:
56+
57+
* title – page title
58+
* layout - usually it is "page"
59+
60+
Menus is stored in `_includes/menu`.

0 commit comments

Comments
 (0)