Wow, the UI on that is gorgeous. I noticed a trend to add features and capability to GitHub which makes a lot of sense because it must have something like millions of users by now and it's something many of here personally use. I'm also working on something for GitHub (a work in progress, <a href="http://gitify.me" rel="nofollow">http://gitify.me</a> - better notifications). I think we're going to see a lot of growth in the ecosystem around GitHub and tools. Using git and GitHub is going to become more important as time passes by.<p>For Prose, the front-end architecture makes a great deal of sense, and they must be using a proxy to get around same origin on API requests. I think some server side operations for caching might make sense to enable speed and reduce the number of requests on GitHub.
Using this thread to extend the discussion about digital content authoring...<p>Prose relies on Markdown, the current de-facto standard for content authoring on the web.<p>But what comes after?<p>If you ask me the answer is clearly: Semantic Rich Text Editing.<p>So if you like Prose, you might also like the idea of Substance, which is essentially about considering content as data and separating it from presentation. The challenging part here is to come up with web-based tools, that reliably maintain plaintext and annotations separately. Once these tools are ready, a new generation of application for collaborative content composition can be built. The resulting structured content is ready to be analyzed, visualized, turned into arbitrary output formats (PDF,ePub, …) or integrated with other applications.<p>Imagine Prose, providing WYSIWYG editing in realtime, plus the concept of patches to suggest improvements to a particular document.<p>Related links:<p>- <a href="http://github.com/substance" rel="nofollow">http://github.com/substance</a> (see composer, surface, text as well as architecture and document repositories)<p>- <a href="https://github.com/prose/prose/issues/139" rel="nofollow">https://github.com/prose/prose/issues/139</a><p>So if (and only if) you like that idea, pls support our entry for the Knight News Challenge's data call.<p><a href="http://newschallenge.tumblr.com/post/25422992783/substance-towards-open-digital-publishing" rel="nofollow">http://newschallenge.tumblr.com/post/25422992783/substance-t...</a><p>Or even better, start contributing! :)<p>Thanks,<p>Michael
Very nice that it's open source. Some of the fun client-side bits appear to be available here:<p><a href="https://github.com/prose/prose/tree/gh-pages/_includes" rel="nofollow">https://github.com/prose/prose/tree/gh-pages/_includes</a>
I would LOVE to be able to drop this and jekyll into a rails app as a gem (say a standard SaaS app) and serve/manage the about/blog part of the app with this. Is there anything like that?
This is quite awesome… I would love to see support for uploading files though! For a Jekyll based site you also want to be able to put images etcetera in there…<p>A lot of similar functionality is provided in GitHub’s wiki editor Gollum… which you can use on any git repository, actually. Thought it was quite fun to try out as well.<p>These solutions get more useful when there are more mixed repositories with code and other content. In our design studio we have all kinds of content usually in our Git: so the standard git viewing interface doesn’t do it justice.<p>We’ve been trying to hack up a viewer for our git repositories, here is an example: <a href="http://osp.schr.fr/work/constant-flyer/view/latest/" rel="nofollow">http://osp.schr.fr/work/constant-flyer/view/latest/</a> the code of the viewer itself is here: <a href="http://osp.schr.fr/tools/visualculture/" rel="nofollow">http://osp.schr.fr/tools/visualculture/</a>
I've been working on an obtvse fork that uses github gists as its backend. However, looking at this, I'm thinking of possibly just shifting to a jekyll-like repository base structure, instead of the complex gist+json based stuff I was using.<p>Thanks for the github.js. I'll try to add gists related stuff to it.<p>Btw,it didn't work on my iPad. Got to the repo choosing screen,but it gets stuck after I choose a branch, or even if it autoselects master.
How easy is it to integrate with other git providers or git from my own servers? Jekyll is not the best for content management and has its own drawbacks. But, this is something orthogonal to Jekyll, in that it call be used to edit any git files. Definitely looking forward to tinkering with this :)
Does this work with hosted jekyll sites or just those that live within github? The documentation only mentions github, but after a quick look at the source code I can't see any reason this wouldn't work (at least with some minor modifications) on any hosted jekyll blog.
Wonderful! The Ctrl + Shift + Left/Right key is handy.<p>Would you add an option to show a live preview side by side?<p>I'm a big fan of live preview, that's why I'm evening developer LIVEditor (my live html/css/js coder at <a href="http://liveditor.com" rel="nofollow">http://liveditor.com</a>)
Feature Request: SEO stuff<p>One thing I miss about wordpress was the SEO plugins to look at my article, heading, meta, etc. This is the only thing I actually miss from wordpress. However, I miss it so much, I am thinking of going back. Please save me this frustration.
How are you guys making the Explanation videos like the one on the prose website or the the substance.io website? Is it some open source tool where you can provide the strings or just low level flash tweens or some thing?
Does Github's support for Jekyll mean that Github automatically "publishes" a blog post? I'm using something similar(Pelican), and I know I can't publish a post using Prose only, is that different for Jekyll sites?
I've been wanting a tool like this for some time. I've considered migrating simple websites running on a CMS into Jekyll but the lack of content editing for "humans" has always been the blocker.
This is really cool. And a little bit depressing that the typography in the preview is better than the typography on my actual site. I should really fix that.
Fantastic work. I've been toying with a CMS backed by a Git repository on-and-off for a while, and this sets a great precedent.<p>Very impressed by the way you've pushed all of the interesting bits to the client side.