Forking questions

[d...@openassembly.com]

Hi,

We are looking to fork this project to host OER on our own site.  I installed and ran oerpub/Aloha-Editor, bookish and github-bookeditor, and I see these all are totally dependent on the Github authentication process, which is too much 'overhead' for our users.  I wonder if anyone could speak on the feasibility of running an instance of any of these applications as an 'integrated' component in a Rails application (versus the NodeJS it's built on?).  My two ideas for approaches to this were:

   a) API/interprocess-messaging style communication between the two apps, with replacement of the Github authentication component with our own git server, and alternately, 

   b) simply ripping out the modified version of Aloha-Editor itself (minus the textbook/module functionality, which would have to be recreated), and integrating that on the front-end of the Rails app.    

Since you guys are the developers, I thought this would be the best place to ask.  b sounds much cleaner to me as a developer, so I guess the more central question is, what changes were actually made to the base Aloha-Editor?

Thanks in advance,

Dustin

[Philip Schatz]

Hello Dustin,

Thanks for trying it out!

There are probably 3 points where it may be easy to "peel off" and use parts of the editor.

The smallest way would be to use the https://github.com/oerpub/Aloha-Editor . That would allow you to create HTML in the https://github.com/oerpub/TextbookHTML format (based on O’Reilly’s HTMLBook format). Aloha can be seen in the bottom of the right panel in http://oerpub.github.io/github-bookeditor.

If you wanted a bit more, like dragging and dropping to assemble a book, you could take a look at https://github.com/oerpub/bookish .

This repository uses Aloha-Editor and adds the Table of Contents and none of which is specific to GitHub.

If you wanted to use github-bookeditor without github.com I wrote a little NodeJS server that understands “just enough" enough of the GitHub API. This would allow you to:

1. use version control

2. create a valid EPUB book

3. resolve some conflicts when multiple people edit at the same time

With it you can load and save a single Git repository. It was written quickly and mostly because I often develop without an internet connection. It also shows how little of the GitHub API would need to be rewritten.

https://github.com/philschatz/local-api.github.com

Also, if you are interested in automatically making a PDF for a book there’s https://github.com/philschatz/pdf-ci

Hope that helps!

- Phil

PS: Since you are making books here are a couple side projects that might be useful:

http://philschatz.github.io/css-polyfills.js/ implements several W3C Drafts that are useful for Print Media but not implemented in browsers.

https://github.com/philschatz/css-coverage.js runs on the command line and plugs into BlanketJS to do CSS coverage after every JS unit test.

--
You received this message because you are subscribed to the Google Groups "oerpub-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to oerpub-dev+...@googlegroups.com.
To post to this group, send email to oerpu...@googlegroups.com.
Visit this group at http://groups.google.com/group/oerpub-dev.
For more options, visit https://groups.google.com/groups/opt_out.

[Dustin van Schouwen]

Wow, thanks a lot!  You've obviously done a lot of work on this yourself.  I'll review all this shortly.

Thanks,
Dustin

You received this message because you are subscribed to a topic in the Google Groups "oerpub-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/oerpub-dev/6yDug8jGuHk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to oerpub-dev+...@googlegroups.com.