Merge branch 'dev' into installing_lib

Author: diemol

.github/workflows/deploy.yml

@@ -11,6 +11,8 @@ jobs:
     steps:
       - name: Checkout repo
         uses: actions/checkout@v2
+        with:
+          fetch-depth: 0
       - name: Setup Hugo
         uses: peaceiris/actions-hugo@v2
         with:

README.md

@@ -54,7 +54,7 @@ repo [settings](https://github.com/SeleniumHQ/seleniumhq.github.io/settings) (if
 you should be able to access the link).
 
 The selenium.dev domain is managed at https://www.gandi.net/en, if you need access to it, reach out to
-any of the [PLC](https://www.selenium.dev/structure/#plc) or [TLC](https://www.selenium.dev/structure/#tlc)
+any of the [PLC](https://www.selenium.dev/project/structure/#plc) or [TLC](https://www.selenium.dev/project/structure/#tlc)
 members, who can help you with that.
 
 If for any reason, you need to setup the domain redirection again,

website_and_docs/config.toml

@@ -58,46 +58,26 @@ title = "Selenium"
 description = "Selenium automates browsers. That's it!"
 languageName ="English"
 weight = 1
-[languages.es]
-title = "Selenium"
-description = "Selenium automates browsers. That's it!"
-languageName ="Español"
-weight = 2
-[languages.de]
-title = "Selenium"
-description = "Selenium automates browsers. That's it!"
-languageName ="Deutsch"
-weight = 3
 [languages.pt-br]
 title = "Selenium"
 description = "Selenium automates browsers. That's it!"
 languageName ="Português (Brasileiro)"
-weight = 4
-[languages.nl]
-title = "Selenium"
-description = "Selenium automates browsers. That's it!"
-languageName ="Nederlands"
-weight = 5
+weight = 2
 [languages.zh-cn]
 title = "Selenium"
 description = "Selenium automates browsers. That's it!"
 languageName = "中文简体"
-weight = 6
-[languages.fr]
-title = "Selenium"
-description = "Selenium automates browsers. That's it!"
-languageName = "Français"
-weight = 7
+weight = 3
 [languages.ja]
 title = "Selenium"
 description = "Selenium automates browsers. That's it!"
 languageName = "日本語"
-weight = 8
-[languages.ko]
+weight = 4
+[languages.other]
 title = "Selenium"
 description = "Selenium automates browsers. That's it!"
-languageName = "한국어"
-weight = 9
+languageName ="Other"
+weight = 5
 
 
 
@@ -162,6 +142,9 @@ offlineSearchMaxResults = 30
 # Enable Algolia DocSearch
 algolia_docsearch = true
 
+# Enable Plausible.io
+plausible_analytics = true
+
 # Enable syntax highlighting and copy buttons on code blocks with Prism
 prism_syntax_highlighting = true
 

website_and_docs/content/_index.es.html

@@ -14,7 +14,26 @@
 </div>
 {{< /blocks/cover >}}
 
-{{< language-alert locale="de" language="German" >}}
+<div class="row td-box--200 justify-content-center">
+	<div class="alert alert-orange bg-transparent col-6 pl-lg-5 my-4 alert-dismissible fade show" role="alert">
+		<h2 class="alert-heading pb-3 text-center">Welcome!</h2>
+		<div class="w-100">
+			<p>
+				<strong>Note:</strong> only
+				<a href="/documentation/">documentation</a> gets translated into other languages. The rest
+				of the website will remain in English.
+			</p>
+			<p class="font-italic">
+				Is there another translation you'd like to see? We're only supporting translations for which we have
+				a dedicated translator. If you'd like to volunteer to be a translator, read how
+				<a href="https://www.selenium.dev/getinvolved/#translating_site">you can help</a>.
+			</p>
+		</div>
+		<button type="button" class="close" data-dismiss="alert" aria-label="Close">
+			<span aria-hidden="true">&times;</span>
+		</button>
+	</div>
+</div>
 
 {{< getting-started color="100" height="auto" title="Getting Started" >}}
 

website_and_docs/content/_index.fr.html

@@ -3,14 +3,10 @@
 linkTitle: About
 aliases:
           [
-            "/es/about/",
-            "/de/about/",
             "/pt-br/about/",
-            "/nl/about/",
             "/zh-cn/about/",
-            "/fr/about/",
             "/ja/about/",
-            "/ko/about/",
+            "/other/about/",
           ]
 ---
 

website_and_docs/content/_index.ko.html

@@ -0,0 +1,82 @@
+---
+title: "A Tour of 4: New Commands"
+linkTitle: "A Tour of 4: New Commands"
+date: 2021-10-13
+tags: ["selenium", "webdriver"]
+author: Simon Stewart ([@shs96c](https://twitter.com/shs96c))
+description: >
+  There's more to Selenium 4 than just the server
+---
+
+Before we ship Selenium 4, I thought it would be nice to introduce
+some of the new features in-depth. Of course, all of the features
+we're covering are in the main [WebDriver documentation][docs], so if
+you're not one for reading blog posts, then feel free to dive in
+there!
+
+You may well be familiar with how to start a Selenium server: you just
+do something like `java -jar selenium-server-4.0.0.jar standalone` and
+away you go! But with Selenium 4, there are some more things you can
+do with this jar.
+
+Least obviously, the server jar is an exectuable on its own. If you're
+using Linux or macOS, and have Java installed, you can make the jar
+executable (eg. `chmod 755 selenium-server-4.0.0.jar`), rename it to
+something like `selenium` and put it on your `$PATH`. That way, rather
+than writing `java -jar ...` you can simply run `selenium`.
+
+Now you've done that, if you run `selenium` with `selenium --help`
+you'll get a handy list of the available sub-commands you can
+execute. There are the old favourites, such as `standalone` (for
+starting a standalone selenium server), and `hub` and `node` (for
+starting a Selenium [Hub and Node][hub and node] setup), but there are
+other interesting commands that are new to Selenium 4.
+
+The first of these is `info`. We've added this to provide easy to find
+and access documentation on common tasks when using the selenium
+server. If you run `selenium info` on its own, you'll see something
+like this:
+
+```shell
+Info
+====
+
+You can find out more about topics concerning Selenium Grid by running the
+"info" command followed by: 
+
+* config - Help on how to configure Selenium
+* tracing - Help on how distributed tracing works with selenium
+* security - Help on how how to secure communications to and within selenium
+* sessionmap - Help on different types of sessionmap and how to start them.
+
+
+Each topic will give you enough information to help you get started, and contains
+some pointers on our site to provide more complete information. 
+```
+
+To get more information on a particular topic, just add the name of
+the topic, for example `selenium info security`. The hope is that this
+will make it less daunting to deal with Selenium, and give you a great
+place to get started with some of the more complicated topics around
+running a Selenium Grid.
+
+Although it's incredibly flexible, the `selenium` command offers a
+daunting list of command line flags. How are you supposed to remember
+them all? You're not! Instead, let `selenium completion` take the
+strain for you. If you're a zsh user, then just `source <(selenium
+completion zsh)`, and now you have tab completion for the
+sub-commands, as well as for all the flags, including examples of how
+to use them.
+
+And, finally, there are some hidden flags. We hid them because they
+can be a little bit confusing to use or understand what they're meant
+to do, but one that can be very useful when debugging how your Grid is
+configured is the `--dump-config` flag. When run with a server command
+such as `standalone` or `hub`, it will dump the configuration options
+used by the Grid as a JSON blob. This can be helpful for tracking down
+subtle issues with configurations, especially when using environment
+properties for configuration.
+
+
+[docs]: /documentation/webdriver/
+[hub and node]: /documentation/grid/setting_up_your_own_grid/#hub-and-nodes