getting started quick tour needs details #69
Comments
Let me take it up. Would start sending pull requests once I have considerable work. On a different note, do we use https://gitter.im/ or some other resource for doc only conversations? I am hesitant to use selenium-developer group for doc only conversations as it might distract selenium developers. |
selenium-developers@, the #selenium IRC channel, or Github issues would probably be the best places to do documentation discussions to include the right people. |
I would like to submit incremental pull requests for it, here is the first pull request - #80 |
I seek opinions/suggestions on following -
|
The thinking here was originally that start.html would be a very brief introduction to the basics of WebDriver to get you started, and that webdriver.html would be the corresponding full-text nitty-gritty “authoritative” documentation on the details surrounding WebDriver. Does this make sense?
We already do this in a number of places by annotating the container with the language, for example |
I yet find it out of sync but that might be just me :)
Not an html/css expert but I tried and got following. Default Java sample on page load - Other language samples display when reader clicks on a specific language link - What is your opinion of this display? |
With regards to the chapter reorganisation, I suggest we write the content first and then re-evaluate. The language selection looks great! |
Updates: I closed the pull request as not comfortable with whole idea of tackling code examples in html, getting rid of encoding etc. Was there a specific reason to not use rst for writing doc line in existing doc? Probably code examples other than java be writtem once pull request #81 is done. |
New pull request - #83 Couple of questions -
|
I don't think we should spend any time documenting Selenium RC, other than potentially something about migration to WebDriver. But even that I consider a low priority. We can replace "2.53.1" with something like "x.y.z" so we don't have to update it every time there's a new release. |
I see there is a small chat here about formatting - wanted to ask here instead of opening a new issue. Should we prepend to them a '$' (dollar sign) like it's commonly done? This will remove things like the coloring added to the |
Fixed on new site, please head to https://github.com/SeleniumHQ/seleniumhq.github.io and raise a PR ther if needed. |
my initial thought is we need separate ones for each client language binding and then also each browser needs a section on what you may need to download / configure to run with it. Thoughts? :)
needed to log this as a placeholder for a google code issue.
https://code.google.com/p/selenium/issues/detail?id=8327
The text was updated successfully, but these errors were encountered: