create placeholders and move content into drivers section

website_and_docs/content/documentation/webdriver/drivers/_index.en.md

@@ -1,11 +1,47 @@
 ---
-title: "Configuring driver parameters"
+title: "Driver Sessions"
 linkTitle: "Drivers"
-weight: 12
+weight: 3
 ---
 
-We learned how to [install drivers]({{< ref "../getting_started/install_drivers.md" >}}) in the Getting Started section.
+Starting and stopping a session is for opening and closing a browser.
 
-Selenium provides access to Service classes which are used to determine how the server is started
+## Creating Sessions
 
+Creating a new session corresponds with the W3C command for [New session](https://w3c.github.io/webdriver/#new-session)
 
+The session is created automatically by initializing a new Driver class object.
+
+Each language allows a session to be created with arguments from one of these classes (or equivalent):
+
+* [Options]({{< ref "options.md" >}}) to describe the kind of session you want; default values are used for local, but this is required for remote
+* Some form of [CommandExecutor]({{< ref "executors.md" >}}) (the implementation varies between languages)
+* [Listeners]({{< ref "listeners.md" >}})
+
+### Local Driver
+
+The primary unique argument for starting a local driver includes information about starting the required driver service
+on the local machine.
+
+* [Service]({{< ref "service.md" >}}) object applies only to local drivers and provides information about the browser driver
+
+{{< alert-code >}}
+Show Starting Local driver with multiple arguments.
+{{< /alert-code >}}
+
+### Remote Driver
+
+The primary unique argument for starting a remote driver includes information about where to execute the code.
+Read the details in the [Remote Driver Section]()
+
+
+## Quitting Sessions
+
+Quitting a session corresponds to W3C command for [Deleting a Session](https://w3c.github.io/webdriver/#delete-session).
+
+Important note: the `quit` method is different from the `close` method, 
+and it is recommended to always use `quit` to end the session
+
+{{< alert-code >}}
+Show quitting a session.
+{{< /alert-code >}}

website_and_docs/content/documentation/webdriver/drivers/_index.ja.md

@@ -1,12 +1,47 @@
 ---
-title: "Configuring driver parameters"
+title: "Driver Sessions"
 linkTitle: "Drivers"
-weight: 12
-needsTranslation: true
+weight: 3
 ---
 
-We learned how to [install drivers]({{< ref "../getting_started/install_drivers.md" >}}) in the Getting Started section.
+Starting and stopping a session is for opening and closing a browser.
 
-Selenium provides access to Service classes which are used to determine how the server is started
+## Creating Sessions
 
+Creating a new session corresponds with the W3C command for [New session](https://w3c.github.io/webdriver/#new-session)
 
+The session is created automatically by initializing a new Driver class object.
+
+Each language allows a session to be created with arguments from one of these classes (or equivalent):
+
+* [Options]({{< ref "options.md" >}}) to describe the kind of session you want; default values are used for local, but this is required for remote
+* Some form of [CommandExecutor]({{< ref "executors.md" >}}) (the implementation varies between languages)
+* [Listeners]({{< ref "listeners.md" >}})
+
+### Local Driver
+
+The primary unique argument for starting a local driver includes information about starting the required driver service
+on the local machine.
+
+* [Service]({{< ref "service.md" >}}) object applies only to local drivers and provides information about the browser driver
+
+{{< alert-code >}}
+Show Starting Local driver with multiple arguments.
+{{< /alert-code >}}
+
+### Remote Driver
+
+The primary unique argument for starting a remote driver includes information about where to execute the code.
+Read the details in the [Remote Driver Section]()
+
+
+## Quitting Sessions
+
+Quitting a session corresponds to W3C command for [Deleting a Session](https://w3c.github.io/webdriver/#delete-session).
+
+Important note: the `quit` method is different from the `close` method, 
+and it is recommended to always use `quit` to end the session
+
+{{< alert-code >}}
+Show quitting a session.
+{{< /alert-code >}}

website_and_docs/content/documentation/webdriver/drivers/_index.pt-br.md

@@ -1,10 +1,47 @@
 ---
-title: "Configurando o driver"
+title: "Driver Sessions"
 linkTitle: "Drivers"
-weight: 12
-needsTranslation: true
+weight: 3
 ---
 
-Nós aprendemos como [instalar drivers]({{< ref "../getting_started/install_drivers.md" >}}) na sessão de Introdução.
+Starting and stopping a session is for opening and closing a browser.
 
-Selenium concede o acesso para classes de serviço que são usadas para determinar como o servidor será iniciado.
+## Creating Sessions
+
+Creating a new session corresponds with the W3C command for [New session](https://w3c.github.io/webdriver/#new-session)
+
+The session is created automatically by initializing a new Driver class object.
+
+Each language allows a session to be created with arguments from one of these classes (or equivalent):
+
+* [Options]({{< ref "options.md" >}}) to describe the kind of session you want; default values are used for local, but this is required for remote
+* Some form of [CommandExecutor]({{< ref "executors.md" >}}) (the implementation varies between languages)
+* [Listeners]({{< ref "listeners.md" >}})
+
+### Local Driver
+
+The primary unique argument for starting a local driver includes information about starting the required driver service
+on the local machine.
+
+* [Service]({{< ref "service.md" >}}) object applies only to local drivers and provides information about the browser driver
+
+{{< alert-code >}}
+Show Starting Local driver with multiple arguments.
+{{< /alert-code >}}
+
+### Remote Driver
+
+The primary unique argument for starting a remote driver includes information about where to execute the code.
+Read the details in the [Remote Driver Section]()
+
+
+## Quitting Sessions
+
+Quitting a session corresponds to W3C command for [Deleting a Session](https://w3c.github.io/webdriver/#delete-session).
+
+Important note: the `quit` method is different from the `close` method, 
+and it is recommended to always use `quit` to end the session
+
+{{< alert-code >}}
+Show quitting a session.
+{{< /alert-code >}}

website_and_docs/content/documentation/webdriver/drivers/_index.zh-cn.md

@@ -1,12 +1,47 @@
 ---
-title: "配置驱动参数"
-linkTitle: "驱动"
-weight: 12 
+title: "Driver Sessions"
+linkTitle: "Drivers"
+weight: 3
 ---
 
-我们在入门部分学习了如何[安装驱动]({{< ref "../getting_started/install_drivers.md" >}}) .
+Starting and stopping a session is for opening and closing a browser.
 
-Selenium提供对服务类的访问, 
-这些服务类用于确定服务器的启动方式
+## Creating Sessions
 
+Creating a new session corresponds with the W3C command for [New session](https://w3c.github.io/webdriver/#new-session)
 
+The session is created automatically by initializing a new Driver class object.
+
+Each language allows a session to be created with arguments from one of these classes (or equivalent):
+
+* [Options]({{< ref "options.md" >}}) to describe the kind of session you want; default values are used for local, but this is required for remote
+* Some form of [CommandExecutor]({{< ref "executors.md" >}}) (the implementation varies between languages)
+* [Listeners]({{< ref "listeners.md" >}})
+
+### Local Driver
+
+The primary unique argument for starting a local driver includes information about starting the required driver service
+on the local machine.
+
+* [Service]({{< ref "service.md" >}}) object applies only to local drivers and provides information about the browser driver
+
+{{< alert-code >}}
+Show Starting Local driver with multiple arguments.
+{{< /alert-code >}}
+
+### Remote Driver
+
+The primary unique argument for starting a remote driver includes information about where to execute the code.
+Read the details in the [Remote Driver Section]()
+
+
+## Quitting Sessions
+
+Quitting a session corresponds to W3C command for [Deleting a Session](https://w3c.github.io/webdriver/#delete-session).
+
+Important note: the `quit` method is different from the `close` method, 
+and it is recommended to always use `quit` to end the session
+
+{{< alert-code >}}
+Show quitting a session.
+{{< /alert-code >}}

website_and_docs/content/documentation/webdriver/drivers/executors.en.md

@@ -0,0 +1,9 @@
+---
+title: "Command executors"
+linkTitle: "Executors"
+weight: 3
+---
+
+These allow you to set various parameters for the HTTP library
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/executors.ja.md

@@ -0,0 +1,9 @@
+---
+title: "Command executors"
+linkTitle: "Executors"
+weight: 3
+---
+
+These allow you to set various parameters for the HTTP library
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/executors.pt-br.md

@@ -0,0 +1,9 @@
+---
+title: "Command executors"
+linkTitle: "Executors"
+weight: 3
+---
+
+These allow you to set various parameters for the HTTP library
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/executors.zh-cn.md

@@ -0,0 +1,9 @@
+---
+title: "Command executors"
+linkTitle: "Executors"
+weight: 3
+---
+
+These allow you to set various parameters for the HTTP library
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/listeners.en.md

@@ -0,0 +1,9 @@
+---
+title: "Command Listeners"
+linkTitle: "Listeners"
+weight: 3
+---
+
+These allow you to execute custom actions in every time specific Selenium commands are sent
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/listeners.ja.md

@@ -0,0 +1,9 @@
+---
+title: "Command Listeners"
+linkTitle: "Listeners"
+weight: 3
+---
+
+These allow you to execute custom actions in every time specific Selenium commands are sent
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/listeners.pt-br.md

@@ -0,0 +1,9 @@
+---
+title: "Command Listeners"
+linkTitle: "Listeners"
+weight: 3
+---
+
+These allow you to execute custom actions in every time specific Selenium commands are sent
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/drivers/listeners.zh-cn.md

@@ -0,0 +1,9 @@
+---
+title: "Command Listeners"
+linkTitle: "Listeners"
+weight: 3
+---
+
+These allow you to execute custom actions in every time specific Selenium commands are sent
+
+{{< alert-code />}}

website_and_docs/content/documentation/webdriver/capabilities/shared.en.md → website_and_docs/content/documentation/webdriver/drivers/options.en.md

@@ -1,10 +1,11 @@
 ---
-title: "Shared capabilities"
-linkTitle: "Shared"
+title: "Browser Options"
+linkTitle: "Options"
 weight: 2
 description: >-
   These capabilities are shared by all browsers.
 aliases: [
+"/documentation/en/capabilitis/shared/",
 "/documentation/en/driver_idiosyncrasies/shared_capabilities/",
 "/documentation/webdriver/capabilities/shared_capabilities/",
 "/documentation/en/webdriver/http_proxies/",
@@ -16,14 +17,13 @@ aliases: [
 ]
 ---
 
-In order to create a new session by Selenium WebDriver, 
-the local end should provide the basic capabilities to the remote end. 
-The remote end uses the same set of capabilities to 
-create a session and describes the current session features. 
+In Selenium 3, capabilities were defined in a session by using Desired Capabilities classes.
+As of Selenium 4, you must use the browser options classes. 
+For remote driver sessions, a browser options instance is required as it determines which browser will be used.
 
-WebDriver provides capabilities that each remote 
-end will/should support the implementation. 
-The following capabilities are supported by WebDriver:
+These options are described in the w3c specification for [Capabilities](https://w3c.github.io/webdriver/#capabilities).
+
+Each browser has [custom options]() that may be defined in addition to the ones defined in the specification.
 
 ## browserName
 

website_and_docs/content/documentation/webdriver/capabilities/shared.ja.md → website_and_docs/content/documentation/webdriver/drivers/options.ja.md

@@ -1,10 +1,11 @@
 ---
-title: "共通のCapability"
-linkTitle: "共通のCapability"
+title: "Browser Options"
+linkTitle: "Options"
 weight: 2
 description: >-
   これらのCapabilityはすべてのブラウザで共通です。
 aliases: [
+"/documentation/ja/capabilitis/shared/",
 "/documentation/ja/driver_idiosyncrasies/shared_capabilities/",
 "/ja/documentation/webdriver/capabilities/shared_capabilities/",
 "/documentation/ja/webdriver/http_proxies/",
@@ -25,11 +26,13 @@ aliases: [
 </p>
 {{% /pageinfo %}}
 
-Selenium WebDriverで新しいセッションを作成するには、ローカルエンドがリモートエンドに基本的なCapabilities（ブラウザの設定情報）を提供する必要があります。
-リモートエンドは、一連の同じCapabilityを使用してセッションを作成し、現在のセッション機能を描きます。
+In Selenium 3, capabilities were defined in a session by using Desired Capabilities classes.
+As of Selenium 4, you must use the browser options classes.
+For remote driver sessions, a browser options instance is required as it determines which browser will be used.
 
-WebDriverは、各リモートエンドがCapabilityをサポートする/すべきCapabilityを提供します。
-WebDriverがサポートするCapabilityは次のとおりです。
+These options are described in the w3c specification for [Capabilities](https://w3c.github.io/webdriver/#capabilities).
+
+Each browser has [custom options]() that may be defined in addition to the ones defined in the specification.
 
 ## browserName
 

website_and_docs/content/documentation/webdriver/capabilities/shared.pt-br.md → website_and_docs/content/documentation/webdriver/drivers/options.pt-br.md

@@ -1,11 +1,12 @@
 ---
-title: "Recursos compartilhados"
-linkTitle: "Recursos compartilhados"
+title: "Browser Options"
+linkTitle: "Options"
 weight: 2
 needsTranslation: true
 description: >-
   These capabilities are shared by all browsers.
 aliases: [
+"/documentation/pt-br/capabilitis/shared/",
 "/documentation/pt-br/driver_idiosyncrasies/shared_capabilities/",
 "/pt-br/documentation/webdriver/capabilities/shared_capabilities/",
 "/documentation/pt-br/webdriver/http_proxies/",
@@ -26,14 +27,13 @@ aliases: [
 </p>
 {{% /pageinfo %}}
 
-Para criar uma nova sessão por Selenium WebDriver,
-a extremidade local deve fornecer os recursos básicos para a extremidade remota.
-A extremidade remota usa o mesmo conjunto de recursos para
-cria uma sessão e descreve os recursos da sessão atual.
+In Selenium 3, capabilities were defined in a session by using Desired Capabilities classes.
+As of Selenium 4, you must use the browser options classes.
+For remote driver sessions, a browser options instance is required as it determines which browser will be used.
 
-WebDriver fornece recursos que cada controle extremidade
-remota irá/deverá apoiar a implementação.
-A seguir estão os recursos que o WebDriver suporta:
+These options are described in the w3c specification for [Capabilities](https://w3c.github.io/webdriver/#capabilities).
+
+Each browser has [custom options]() that may be defined in addition to the ones defined in the specification.
 
 ## browserName