Voting starts in March for the Drupal Association Board election.
Initially designed to allow seamless cloud-hosted visualizations for the forthcoming VizCloud Drupal distribution, it supplies a bit of functionality that isn't available anywhere else in the Drupal module ecosystem. As such, this makes it a good candidate to be released as a module unto itself.
There are two major reasons why saving nodes on GitHub is cool:
- It provides a way for a basic Drupal installation to be used as an offline content creation and management tool (Somewhat like the FrontPages and Dreamweavers of yore) — users create content using a local installation, which is then hosted independently on GitHub Pages. This may be preferable in some situations where a user wants to leverage Drupal's advanced tools (Views, Panels, etc.) for a particular task, even if there's no possibility of that Drupal installation ever being used to host content itself (I.e., it's behind a corporate firewall).
Usage is simple: an admin configures a central repository, which gets added to every time a user with appropriate permissions clicks the big "Push to GitHub" button on the edit node page.
Some code is based off SaveToFTP -- http://drupal.org/project/savetoftp
- User repos -- push to the shared central repo, or define a personal GitHub repo to push to.
- Integration with GitHub Connect.
Project Page: http://drupal.org/sandbox/aendrew/1914226
PAReview.sh results: http://ventral.org/pareview/httpgitdrupalorgsandboxaendrew1914226git
git clone --recursive --branch 7.x-1.x http://git.drupal.org/sandbox/aendrew/1914226.git github_pages