Update README.md

Author: mchev

README.md

@@ -2,19 +2,6 @@
 
 Welcome to the official Extensions Repository for **InvoiceShelf**. This repository serves as a central hub for creating, managing, and submitting extensions to enhance the functionality of InvoiceShelf.
 
-## 📖 Table of Contents
-- [Introduction](#introduction)
-- [Getting Started](#getting-started)
-  - [Requirements](#requirements)
-  - [Repository Structure](#repository-structure)
-- [Creating an Extension](#creating-an-extension)
-  - [Metadata File](#metadata-file)
-  - [Code Structure](#code-structure)
-- [Submitting an Extension](#submitting-an-extension)
-- [Versioning and Updates](#versioning-and-updates)
-- [Extension Guidelines](#extension-guidelines)
-- [Support](#support)
-
 ---
 
 ## 🧩 Introduction
@@ -25,22 +12,26 @@ Extensions are modular pieces of functionality that you can add to your InvoiceS
 ## 🚀 Getting Started
 
 ### Requirements
+
 To develop an extension, you need the following:
+
 - Basic knowledge of InvoiceShelf's API or extension architecture.
 - GitHub, GitLab, or other Git hosting platforms for managing your extension.
 
 ### Repository Structure
+
 Your extension repository should follow this structure:
 
 > TBD
 
 
 ---
 
-## ✍️ Creating an Extension
+## ✍️ Adding an Extension to the InvoiceShelf markeplace
 
 ### Metadata File
-The `extension.json` file is a mandatory file that provides metadata about your extension. Below is a sample:
+
+The `extensions.json` lists all available extensions for InvoiceShelf. Below is a sample:
 
 ```json
 {
@@ -59,6 +50,14 @@ The `extension.json` file is a mandatory file that provides metadata about your
 }
 ```
 
+To add your extension to the extensions.json file:
+
+1. Fork the InvoiceShelf extensions repository.
+2. Add your extension's metadata to the extensions.json file.
+3. Submit a pull request (PR) with your changes.
+
+> Once submitted, your extension will be reviewed for inclusion in the marketplace.
+
 ***Metadata Fields***
 
 - name: A unique name for your extension.
@@ -71,19 +70,6 @@ The `extension.json` file is a mandatory file that provides metadata about your
 - repository: URL of your extension's Git repository.
 - download_url: Direct link to the downloadable package (ZIP file).
 
-***Code Structure***
-
-Write your extension's functionality in the src/ directory. Follow coding standards for [Your Project Name]. Include documentation in README.md and tests in the tests/ folder (if applicable).
-📝 Submitting an Extension
-
-To submit your extension to the marketplace:
-
-- Create a public repository on GitHub, GitLab, or similar.
-- Add a README.md and LICENSE file.
-- Create a PR in order to add your extension in the list
-
-Once submitted, your extension will be reviewed for inclusion in the marketplace.
-
 🔄 Versioning and Updates
 
 - Tag releases in your repository using Git tags.