-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate a project’s readme #11
Comments
Strange, I was thinking about the exact same thing. I even submitted a ticket to github asking them to add this to their API since I need this in another project. |
I independently thought the same thing. Saves a step, and the user wont have to leave the site every time to view it. |
The big thing with this is that you need to worry about the following:
|
Yes, let me add that to the Gemfile so that my ruby application that indexes CakePHP code can consume markup on github. |
just gathering the pieces together to make this happen eventually, yes i On Sat, Jun 25, 2011 at 10:22 AM, josegonzalez <
|
Then do so. |
Found a project that may be the best solution. I can look into forking it and adding missing parsers needed. I opened a bug ticket so that the project would support file extension scanning: joebeeson/embellish#1 |
They had a discussion on the github markup repo about how useful or useless On Mon, Jun 27, 2011 at 4:50 PM, ProLoser <
|
Checking the file extension would be good enough, and then mapping these to some library for parsing. What would need to occur is, on repository update, the readme would be detected (through use of some regex) and then turned into some standard, like, idk, html. It's sanitized and stored, then rendered whenever the user accesses the page for that package. Could be stored in a viewcache, or even just raw html that is then included via php. Pandoc would be nice, if it compiled on my mac and didn't require 9 million other things. |
Is anyone working on this at the moment? I'd be happy to add you guys as contributors so we can assign things to people. |
it's a bitch to parse all the different readme formats... perhaps a textarea with the source would be enough (since we can all read most of the formats by site)... just enough to get a summary of an unfamiliar project
The text was updated successfully, but these errors were encountered: