feat: add instructions about frontend development

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>

Author: vitormattos

developer_manual/getting-started/development-environment/frontend.rst

@@ -0,0 +1,48 @@
+Frontend
+========
+
+By default, the Nextcloud server repository ships with the frontend already built for production.  
+For development purposes, you may want to rebuild it in **development mode**.  
+This allows you, for example, to inspect server components using the Vue Devtools browser extension.
+
+Building server for development
+-------------------------------
+
+To rebuild the frontend in development mode:
+
+1. Access the Nextcloud container:
+
+   .. code-block:: bash
+
+      docker compose exec -u www-data nextcloud bash
+
+2. Go to the root folder of the Nextcloud server:
+
+   .. code-block:: bash
+
+      cd /var/www/html
+
+3. Install dependencies and build in dev mode:
+
+   .. code-block:: bash
+
+      npm ci && npm run dev
+
+Reverting the server build
+--------------------------
+
+If you build the frontend in development mode, you must revert the changes before pulling new updates from the Nextcloud **master** branch.  
+Otherwise, you may run into conflicts.
+
+To revert the build:
+
+1. Exit the container.  
+2. From your host machine, go to the Nextcloud server root folder.  
+3. Remove the ``dist`` folder and restore it from Git:
+
+   .. code-block:: bash
+
+      rm -rf dist
+      git checkout -- dist
+
+After pulling the latest changes, you can rebuild the frontend in development mode again if needed.

developer_manual/getting-started/development-environment/index.rst

@@ -0,0 +1,10 @@
+=======================
+Development environment
+=======================
+
+.. toctree::
+   :maxdepth: 2
+
+   setup
+   updating
+   frontend

…ting-started/development-environment.rst …tarted/development-environment/setup.rstdeveloper_manual/getting-started/development-environment.rst renamed to developer_manual/getting-started/development-environment/setup.rst developer_manual/getting-started/development-environment.rst renamed to developer_manual/getting-started/development-environment/setup.rst

@@ -1,5 +1,11 @@
-Development environment
-=======================
+Setup
+=====
+
+.. note::
+   If the project does not have an issue for what you want to work on, please create one first.
+
+If you would like to start contributing code, you may wish to begin with our list of good first issues.  
+See the respective sections below for further instructions.
 
 Prerequisites
 -------------
@@ -29,15 +35,6 @@ Additional dependencies
 - ``poppler-utils``  
 - System locale configured with UTF-8 charset  
 
-Developing for LibreSign
-------------------------
-
-.. note::
-   If the project does not have an issue for what you want to work on, please create one first.
-
-If you would like to start contributing code, you may wish to begin with our list of good first issues.  
-See the respective sections below for further instructions.
-
 Setting up Nextcloud
 --------------------
 
@@ -78,12 +75,35 @@ Inside the container, go to ``apps-extra/libresign`` and run:
     # Build and watch JS changes
     npm run watch
 
-Final configuration
--------------------
+Configuring LibreSign
+---------------------
 
 After setting up the environment and installing LibreSign, open  
 ``Administration Settings > LibreSign`` in Nextcloud and:
 
 - Click the **Download binaries** button.  
 - Once all items show status **successful** (except “root certificate not configured”),  
   continue to the next section to configure the root certificate.
+
+
+Extra apps
+----------
+
+LibreSign also integrates with the following Nextcloud apps:
+
+.. list-table::
+   :header-rows: 1
+   :widths: 20 80
+
+   * - **App**
+     - **Description**
+   * - `guests <https://apps.nextcloud.com/apps/guests>`__
+     - Allows inviting guest users to sign documents.
+   * - `notifications <https://github.com/nextcloud/notifications>`__
+     - Sends notifications about signature requests and updates.
+   * - `activity <https://github.com/nextcloud/activity>`__
+     - Logs activities such as signature requests and confirmations.
+   * - `viewer <https://github.com/nextcloud/viewer>`__
+     - Enables PDF viewing inside LibreSign without leaving the app.
+   * - `files_pdfviewer <https://apps.nextcloud.com/apps/files_pdfviewer>`__
+     - Required in combination with *viewer* for proper PDF rendering.

developer_manual/getting-started/development-environment/updating.rst

@@ -0,0 +1,43 @@
+Updating
+========
+
+It is recommended to periodically update both Nextcloud and LibreSign in your local environment to ensure compatibility.
+
+Updating Nextcloud
+------------------
+
+- First, check if there are any local modifications in your Nextcloud repository:
+
+  .. code-block:: bash
+
+     cd path/to/nextcloud
+     git status
+
+  .. note::
+     If there are uncommitted changes, resolve them (commit, stash, or discard) before pulling updates.  
+     This avoids conflicts when updating from the master branch.
+
+- Pull the latest changes from the Nextcloud **master** branch:
+
+  .. code-block:: bash
+
+     git pull origin master
+
+- After pulling, the ``3rdparty`` folder may be outdated. In that case, run:
+
+  .. code-block:: bash
+
+     git submodule update --init --recursive
+
+Updating LibreSign
+------------------
+
+- Before starting a new task, always make sure your local ``main`` branch is up to date with the upstream repository:
+
+  .. code-block:: bash
+
+     cd path/to/libresign
+     git checkout main
+     git pull upstream main
+
+- Then create your feature or fix branch from the updated ``main``.

developer_manual/getting-started/index.rst

@@ -6,4 +6,4 @@ Getting started
    :maxdepth: 2
 
    branch-policies
-   development-environment
+   development-environment/index