Merge pull request #4250 from NathanLovato/organization/split-getting-started-workflow

Create new sections from Project Workflow

classes/class_editorscenepostimport.rst

@@ -42,7 +42,7 @@ The :ref:`post_import<class_EditorScenePostImport_method_post_import>` callback
 Tutorials
 ---------
 
-- `#custom-script <../getting_started/workflow/assets/importing_scenes.html#custom-script>`_ in :doc:`../getting_started/workflow/assets/importing_scenes`
+- `#custom-script <../tutorials/assets_pipeline/importing_scenes.html#custom-script>`_ in :doc:`../tutorials/assets_pipeline/importing_scenes`
 
 Methods
 -------

classes/class_javascript.rst

@@ -21,7 +21,7 @@ The JavaScript singleton is implemented only in the HTML5 export. It's used to a
 Tutorials
 ---------
 
-- `#calling-javascript-from-script <../getting_started/workflow/export/exporting_for_web.html#calling-javascript-from-script>`_ in :doc:`../getting_started/workflow/export/exporting_for_web`
+- `#calling-javascript-from-script <../tutorials/export/exporting_for_web.html#calling-javascript-from-script>`_ in :doc:`../tutorials/export/exporting_for_web`
 
 Methods
 -------

classes/class_os.rst

@@ -1331,7 +1331,7 @@ Returns ``true`` if an environment variable exists.
 
 - :ref:`bool<class_bool>` **has_feature** **(** :ref:`String<class_String>` tag_name **)** const
 
-Returns ``true`` if the feature for the given feature tag is supported in the currently running instance, depending on platform, build etc. Can be used to check whether you're currently running a debug build, on a certain platform or arch, etc. Refer to the `Feature Tags <https://docs.godotengine.org/en/latest/getting_started/workflow/export/feature_tags.html>`_ documentation for more details.
+Returns ``true`` if the feature for the given feature tag is supported in the currently running instance, depending on platform, build etc. Can be used to check whether you're currently running a debug build, on a certain platform or arch, etc. Refer to the `Feature Tags <https://docs.godotengine.org/en/latest/tutorials/export/feature_tags.html>`_ documentation for more details.
 
 **Note:** Tag names are case-sensitive.
 

getting_started/workflow/index.rst

@@ -1,11 +0,0 @@
-Project workflow
-================
-
-.. toctree::
-   :maxdepth: 1
-   :name: toc-learn-workflow
-
-   project_setup/index
-   assets/index
-   export/index
-   best_practices/index

getting_started/workflow/project_setup/index.rst

@@ -1,11 +0,0 @@
-Project setup
-=============
-
-.. toctree::
-   :maxdepth: 1
-   :name: toc-learn-workflow-project_setup
-
-   project_organization
-   version_control_systems
-
-.. plugins_from_assetlib

index.rst

@@ -67,33 +67,36 @@ The main documentation for the site is organized into the following sections:
 
    getting_started/introduction/index
    getting_started/step_by_step/index
-   getting_started/workflow/index
 
 
+.. The sections below are sorted alphabetically. Please keep them that way.
 .. toctree::
    :maxdepth: 1
    :caption: Tutorials
    :name: sec-tutorials
 
-   tutorials/scripting/index
    tutorials/2d/index
    tutorials/3d/index
+   tutorials/animation/index
+   tutorials/assets_pipeline/index
    tutorials/audio/index
-   tutorials/physics/index
+   tutorials/best_practices/index
    tutorials/editor/index
-   tutorials/math/index
-   tutorials/animation/index
+   tutorials/export/index
+   tutorials/i18n/index
    tutorials/inputs/index
    tutorials/io/index
-   tutorials/i18n/index
-   tutorials/ui/index
+   tutorials/math/index
+   tutorials/networking/index
+   tutorials/performance/index
+   tutorials/physics/index
+   tutorials/platform/index
+   tutorials/plugins/index
    tutorials/rendering/index
+   tutorials/scripting/index
    tutorials/shaders/index
-   tutorials/networking/index
+   tutorials/ui/index
    tutorials/vr/index
-   tutorials/plugins/index
-   tutorials/platform/index
-   tutorials/performance/index
 
 
 .. toctree::

getting_started/workflow/assets/importing_scenes.rst → tutorials/assets_pipeline/importing_scenes.rst

@@ -405,7 +405,7 @@ simple or dynamic objects that require mostly-accurate collision detection.
 
 However, in both cases, the visual geometry may be too complex or not smooth
 enough for collisions. This can create physics glitches and slow down the engine
-unneccesarily.
+unnecessarily.
 
 To solve this, the ``-colonly`` modifier exists. It will remove the mesh upon
 importing and will create a :ref:`class_staticbody` collision instead.

getting_started/workflow/assets/index.rst → tutorials/assets_pipeline/index.rst

@@ -1,4 +1,4 @@
-Assets workflow
+Assets pipeline
 ===============
 
 .. toctree::

getting_started/workflow/best_practices/index.rst → tutorials/best_practices/index.rst

@@ -15,3 +15,5 @@ Best practices
    godot_notifications
    data_preferences
    logic_preferences
+   project_organization
+   version_control_systems

getting_started/workflow/best_practices/scene_organization.rst → tutorials/best_practices/scene_organization.rst

@@ -385,7 +385,7 @@ own place in the hierarchy as a sibling or some other relation.
   of game connections and the like.
 
 The key to scene organization is to consider the SceneTree in relational terms
-rather than spatial terms. Are the nodes dependent on their parent's existance?
+rather than spatial terms. Are the nodes dependent on their parent's existence?
 If not, then they can thrive all by themselves somewhere else.
 If they are dependent, then it stands to reason that they should be children of
 that parent (and likely part of that parent's scene if they aren't already).