phpjs/_octopress/source/_posts/2012-09-26-new-site.markdown

php.js offers community built php functions in javascript

---
layout: post
title: "New site"
date: 2012-09-26 17:39
comments: true
categories: [ website, octopress, future ]
---

Hi everybody,

Welcome to our new site.
The old one had a lot of dead weight that nobody used and was basically unmaintained.

This one is generated by Octopress as plain html, and then stored on Github pages.

The source to do that is inside the php.js directory in the `_octopress` dir,
and freely available.

For instance, you can now very easily:

 - [edit the about page](https://github.com/kvz/phpjs/edit/master/_octopress/source/about/index.markdown)
 - [change this blog post](https://github.com/kvz/phpjs/edit/master/_octopress/source/_posts/2012-09-26-new-site.markdown)
 - [checkout the navigation](https://github.com/kvz/phpjs/blob/master/_octopress/source/_includes/custom/navigation.html)
 - [improve the way function pages are built](https://github.com/kvz/phpjs/blob/master/_octopress/Rakefile#L30)

Next, any [php.js contributor](https://github.com/kvz/phpjs/graphs/contributors)
who has [Octopress set up](http://kvz.io/blog/2012/09/25/blog-with-octopress/)
(this mostly involves having the right ruby & gem versions) can then run
`make site MSG="describe what you did"` in the
project's root dir to deploy the changes.

This should make it easy for [php.js contributors](https://github.com/kvz/phpjs/graphs/contributors)
(or any Github user really, using pull requests)
to update the site, making it less dependent on few core members, and more a
community effort.

This is also the way I want to do regular php.js development. Less via comments,
more via the power of Github.

To people wondering where the compiler has gone to, I'm discontinuing that feature.
It was more often broken then working, and I think this site should focus on
being a simple resource and discussion platform, and not much else.

Now that everything is open sourced more I think there's room for anyone to build
a better alternative.

While I'm not actively involved with php.js anymore, I hope taking this step will
make the project ready for the future.


Best wishes,

[Kevin](http://twitter.com/kvz)