-
Notifications
You must be signed in to change notification settings - Fork 365
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
Textile documentation generator #83
Conversation
to prepare Textile and Markdown writers.
of HtmlIndex and HtmlExample.
Textile Index Cucumber Feature and Steps.
with new api.
textile_documentation feature.
textile for new test api.
to test presence of generated examples.
I have this merged in and passing locally. The only thing that was failing was the docs dir changed so the textile feature needed updating. I like what you did with the Views. My only concern is that the textile index doesn't link to examples, it just has the description. |
…ges_from_zipmark Conflicts: spec/api_documentation_spec.rb
DSL and path generation changes.
I pushed new commits.
|
Textile documentation generator
Hi,
I've added writers, templates, etc. to generate the documentation in textile. I noticed that you have pushed some new commits on your master branch since I forked your repo. I wanted to merge your changes into my repo and then send you a pull request, however I saw that running
rspec
generates warnings and runningcucumber
fails. I guess you haven't finished what you wanted to do yet and I gave up the merge.Additionally, I will do some tests of the textile docs generation with real projects. If the tests are ok, I'll merge my develop branch into my master branch.