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.
Prose relies on Markdown, the current de-facto standard for content authoring on the web.
But what comes after?
If you ask me the answer is clearly: Semantic Rich Text Editing.
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.
Imagine Prose, providing WYSIWYG editing in realtime, plus the concept of patches to suggest improvements to a particular document.
Related links:
- http://github.com/substance (see composer, surface, text as well as architecture and document repositories)
- https://github.com/prose/prose/issues/139
So if (and only if) you like that idea, pls support our entry for the Knight News Challenge's data call.
http://newschallenge.tumblr.com/post/25422992783/substance-t...
Or even better, start contributing! :)
Thanks,
Michael
Well and I really don't think inline styles / annotations are good.
We use Pandoc to support a variety of output formats already.
E.g. goto: http://substance.io/michael/data-js and open the export dialogue.
However, we're working on a new architecture (https://github.com/substance/architecture) because we don't want to treat the symptoms of the current implementation and instead fix the problems we've identified at heart.
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.
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.
We’ve been trying to hack up a viewer for our git repositories, here is an example: http://osp.schr.fr/work/constant-flyer/view/latest/ the code of the viewer itself is here: http://osp.schr.fr/tools/visualculture/
Thanks for the github.js. I'll try to add gists related stuff to it.
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.
Definitely love using Prose.io with it. It has made my writing process much simpler.
Would you add an option to show a live preview side by side?
I'm a big fan of live preview, that's why I'm evening developer LIVEditor (my live html/css/js coder at http://liveditor.com)
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.
So SEO is not in the scope of the project.
http://prose.io/#MyOrganization/my-repo
Worked for me.
http://prose.io#:org/:repo/:branch
In future we'll also allow browsing user and organisation profiles by accessing:
http://prose.io#:user http://prose.io#:org
Need to find out if there's a way to fetch the default branch, so you can just
The ui is beautiful.
So what about code highlighting?
Very impressed by the way you've pushed all of the interesting bits to the client side.
