This repository has been archived by the owner on Dec 21, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 529
Discussion around general improvements of the documentation #633
Comments
We may distinguish
For example the 10 minute tutorial are pretty fine as they are now, but parallel execution is too specific and could be moved elsewhere. On my own, I think a dedicated documentation website for basic usage still makes sense. It is still easier for some user. |
I agree with slimming down what's on the website. I had a quick scan and there's quite a bit of JS content that's now outdated that I didn't previously know about - so it's doing more harm than if it wasn't there at all. |
6 tasks
Quite a while ago the idea was just the opposite, see #188. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We've discussed this previously in the open source weekly meetings.
I think we should abandon the whole language tab idea and move more of the platform-specific documentation to plain old GitHub Markdown files in the respective Cucumber-* repositories. We're doing this already here: https://github.com/cucumber/cucumber-js#documentation
The reason I want to abandon it is that it's too difficult to write documentation this way. There are lots of
if
statements in the Markdown code to display/hide contents for various languages.if
statements are cumbersome to editWe can keep high-level platform-agnostic content where it is now though.
Originally posted by @aslakhellesoy in #628 (comment)
The text was updated successfully, but these errors were encountered: