Update the docs for the new Ghidra support

Author: mahaloz

docs/decompilers/ghidra.md

@@ -5,19 +5,26 @@ sidebar_position: 3
 # Ghidra
 
 ## Extra Install Steps
-You must install using `pip3 install binsync[ghidra]` for the extra dependencies.  After doing this, continue with [installation via Script](/quickstart/install#installation-via-script).
-- Install extra dependencies using `pip3 install binsync[ghidra]`
-- Continue with [installation via Script](/quickstart/install#installation-via-script)
-- From the main window, go to Edit -> Plugin Path and make sure the plugin path created by BinSync is included
-- From CodeBrowser, go to Window -> Script Manager -> find `binsync_plugin.py` and tick the "In Tool" box in its line
-- Start BinSync in CodeBrowser via Tools -> BinSync -> Start UI
-
-## Extra Info
-BinSync is written in Python 3, however, Ghidra only has a Python 2 backend. 
-To deal with this, we use a vendored version of [ghidra_bridge](https://github.com/justfoxing/ghidra_bridge).
-We copy a BinSync stub, along with Ghidra Bridge code, into the `ghidra_scripts` folder, which is Python 2. 
-Inside Ghidra, when you start BinSync, we use the Python 2 side to start the Python 3 GUI in another thread. 
-We use Ghidra Bridge to make change requests to the Ghidra UI.
+After doing the traditional install, you must activate the BinSync script in Ghidra. 
+Note, you should have launched in [PyGhidra mode](https://github.com/NationalSecurityAgency/ghidra/blob/stable/GhidraDocs/GettingStarted.md#pyghidra-mode), which can be done using the Ghidra `support/pyghidraRun` script.
+Once launched, open any binary, then:
+
+1. On the top menu bar, click `Window->Script Manager`
+2. Using the `Filter` search bar on the bottom of that window, search for `binsync`
+3. Check the box next to the found `binsync_plugin.py`
+4. Close the script manager
+5. BinSync can now be started on the top menu bar `Tools->BinSync->Connect`
+
+## Useful Info
+Ghidra's GUI engine is written in Java, but BinSync's GUI is written in Python.
+To make BinSync's GUI reusable in Ghidra, we run a Python server in Ghidra that exposes BinSync APIs.
+Then, in another Python process, we connect to that server with the GUI window (which is the client).
+This gives us the speed of native Python 3 execution in Ghidra, with the bottleneck being GUI operations.
+
+The technicals go like this when you click `Connect` in Ghidra:
+1. We start `DecompilerServer` [in Ghidra's Python process](https://github.com/binsync/binsync/blob/b032aeff37155867f76042c721d4da164b630145/binsync/interface_overrides/ghidra.py#L83)
+2. We subprocess out the command `binsync -s ghidra`, which [starts the GUI in a new process](https://github.com/binsync/binsync/blob/b032aeff37155867f76042c721d4da164b630145/binsync/interface_overrides/ghidra.py#L83).
+3. The user uses the new GUI, which is a client, to their server
 
 ## Support Progress
 

docs/intro.md

@@ -21,18 +21,17 @@ center of BinSync's syncing ability. Here are the supported REAs:
 - Enums
 - Comments
 
-Note: all types support user-created types like structs. In short, with BinSync you can track, manage, and sync
-changes you make in your decompiler with any decompiler supported by BinSync.
+Note: all types support user-created types like structs.
 
-For synchronous help, or a more vocal discussion, join our discord:
+**Join our discord below for more online help**:
 
 [![Discord](https://img.shields.io/discord/900841083532087347?label=Discord&style=plastic)](https://discord.gg/wZSCeXnEvR)
 
 ## Supported Platforms
 - IDA Pro: **>= 8.4** (if you have an older version, use [BinSync v4.10.1](https://github.com/binsync/binsync/commit/bac7b9d4a6cca64810bb07428391415702765cd4))
 - Binary Ninja: **>= 2.4**
 - angr-management: **>= 9.0**
-- Ghidra: **>= 10.1**
+- Ghidra: **>= 12.0** (launched in [PyGhidra mode](https://github.com/NationalSecurityAgency/ghidra/blob/stable/GhidraDocs/GettingStarted.md#pyghidra-mode))
 
 All versions require **Python >= 3.10** and **Git** installed on your system.
 

docs/quickstart/install.md

@@ -4,9 +4,10 @@ sidebar_position: 1
 
 # Installation
 
-There are two main ways to install BinSync: via pip and an installation script, or via pip and manual configuration.
+Installing BinSync on most decompilers is a two step process: first you install the binsync library which
+provides functionality, than you copy (automated or manual) as stub into the decompiler to call that code.
 
-**Before proceeding, please see specific instructions for [Binary Ninja](/decompilers/binja) and [Ghidra](/decompilers/ghidra)**
+**Before proceeding, please see specific instructions for [Binary Ninja](/decompilers/binja) if you are using it.**
 
 ## Installation via Script
 
@@ -39,11 +40,10 @@ If you are not able to find the `binsync` command, you might be able to access i
 please jump to the [Manual Install](#manual-install) section.
 
 
-## Manual Install
+## Manual Install (optional)
 If you were able to use a plugin manager or the built-in Python script, skip this.
 
-If you are unable to install using the earlier method, you are probably on Windows. In that case, installing
-BinSync is a two-step process:
+If you are unable to install using the earlier method, you are probably on Windows. In that case:
 1. Install the core with the Python version associated with your decompiler: `pip3 install binsync`
 2. Install the decompiler stub directly into your decompilers `plugin` folder.
 
@@ -65,7 +65,9 @@ A [Git credential helper](https://git-scm.com/doc/credential-helpers) can secure
 You'll need to use this method if you cloned your BinSync repo via HTTPS.
 
 ## Install Validation and Usage
-After you are done installing BinSync with the steps above, you should validate that the install works by syncing data from an example repo we have setup.
+If you are using Ghidra, follow the extra steps needed to finish the install [here](/decompilers/ghidra.md#extra-install-steps).
+
+After you are done installing BinSync with the steps above, you should validate that the install works by syncing data from an example repo we have set up.
 You can find a tutorial to validate this install, with some basic usage, in the [Install Validation](./install-validation) section.
 
 After validating your installation, it's **highly** recommended that you read the [Usage Guide](/ui-guide), since BinSync can be rather complicated to