@silexlabs/silex 3.0.0-alpha.29 → 3.0.0-alpha.32

package/.silex.js

@@ -5,14 +5,7 @@ module.exports = function (silexConfig, options) {
     __dirname + '/src/plugins/StaticPlugin.js',
     __dirname + '/src/plugins/WebsitePlugin.js',
     __dirname + '/src/plugins/PublishPlugin.js',
-  ], {
-    'src/plugins/WebsitePlugin.js': {
-      backend: 'src/plugins/DefaultBackend.js',
-    },
-    'src/plugins/PublishPlugin.js': {
-      backend: 'src/plugins/DefaultBackend.js',
-    },
-  })
+  ])
 
   // Return an object to be merged with Silex config
   return {}

package/CONTRIBUTING.md

@@ -1,13 +1,36 @@
 ### Overview
 
-To contribute code (features, bug fixes, design changes etc.) to the Silex code base, you'll need to complete a few steps to get a local working copy of our repository. Below are the steps you'll need to fork, clone, branch, and create a pull request. 
+This page is about contributing code, but other types of contribution are welcome, [let's chat](https://github.com/silexlabs/Silex/discussions)!
 
-Please be sure to conform to the coding standards used throughout our project and bear in mind that, by contributing to this project, you agree to our [Code of Conduct](https://github.com/silexlabs/Silex/wiki/Silex-Code-of-Conduct). 
+Useful links
+
+* [Silex meta repository](https://github.com/silexlabs/silex-meta)
+* [Open positions, join the team](https://github.com/silexlabs/Silex/issues?q=is%3Aissue+is%3Aopen+label%3A%22open+position%22)
+* [Become a core contributor with these issues to get started](https://github.com/silexlabs/Silex/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
+* [Testers, docs and other help wanted annoucements](https://github.com/silexlabs/Silex/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22)
+
+To contribute code (features, bug fixes, design changes etc.) to the Silex code base, you'll need to complete a few steps to get a local working copy of our repository. Below are the steps you'll need to fork, clone, branch, and create a pull request.
+
+Please be sure to conform to the coding standards used throughout our project and bear in mind that, by contributing to this project, you agree to our [Code of Conduct](https://github.com/silexlabs/Silex/wiki/Silex-Code-of-Conduct).
+
+## Code base overview
+
+The Silex API is primarily divided into two parts: the client-side and the server-side.
+
+### Client-side
+
+The client-side is primarily handled by the files in the `src/ts/client` directory. The main entry point is defined in `index.ts`, which initializes the Silex application. The `config.ts` file contains the `SilexConfig` class that holds the configuration for the client-side application, including the GrapesJS editor configuration and the client config URL. The `grapesjs` directory contains the GrapesJS editor configuration and plugins. The `utils.ts` file contains utility functions.
+
+### Server-side
+
+The server-side is primarily handled by the files in the `src/ts/server` directory. The main entry point is defined in `index.ts`, which initializes the server-side application. The `config.ts` file contains the `ServerConfig` class that holds the configuration for the server-side application. The `express.ts` file sets up the Express.js application and starts the server. The `cli.ts` file handles the command-line interface for the server, parsing command-line arguments and setting environment variables accordingly. The `events.ts` file defines events for the startup process.
+
+## Code contribution process
 
 ### Steps
 
-   If you don't have a GitHub account, start [here](https://github.com/join).  
-   
+   If you don't have a GitHub account, start [here](https://github.com/join).
+
 1. **Fork the project**
 
 	 Open the [Silex Project](https://github.com/silexlabs/Silex/) in GitHub. Click `Fork` in the upper right corner of the window. This adds a copy of the Silex repository to your GitHub account.
@@ -18,42 +41,42 @@ Please be sure to conform to the coding standards used throughout our project an
 
    ```bash
    # Open command line terminal
-   # Navigate to your desired working directory 
+   # Navigate to your desired working directory
    cd <your-desired-working-directory>
    git clone https://github.com/<your-username>/Silex.git
     ```
 
 3. **Set the upstream repository**
 
-   Assign Silex as the upstream repository. Setting the upstream repository tells Git where to pull from when you use the pull command (which you'll do in the next step).  
-   
+   Assign Silex as the upstream repository. Setting the upstream repository tells Git where to pull from when you use the pull command (which you'll do in the next step).
+
 	 ```bash
 	 cd Silex
 	 git remote add upstream https://github.com/silexlabs/Silex.git
 	 ```
-      
+
 4. **Pull the latest upstream changes**
 
    ```bash
-   git pull upstream develop
+   git pull upstream main
    ```
 
 5. **Create a new branch** (Recommended)
 
-	 Though you can work directly in the default develop branch, it is best practice to keep that branch synced with Silex and create a new working branch for your changes. Name the new branch whatever you'd like.
+	 Though you can work directly in the default dev branch, it is best practice to keep that branch synced with Silex and create a new working branch for your changes. Name the new branch whatever you'd like.
 
    ```bash
    git checkout -b <new-branch-name>
    ```
-      
-    You'll need to set the upstream branch so git knows where to point your new branch's pull and push commands. Below you set your local develop branch as the upstream branch to your new branch.
+
+    You'll need to set the upstream branch so git knows where to point your new branch's pull and push commands. Below you set your local dev branch as the upstream branch to your new branch.
 
    ```bash
-   git branch --set-upstream-to=develop <new-branch-name>
+   git branch --set-upstream-to=dev <new-branch-name>
    ```
 
-   **Notes on branch management:**  
-   You can easily see a list of all of the branches in the local repository. The branch with [*] is the current working branch. 
+   **Notes on branch management:**
+   You can easily see a list of all of the branches in the local repository. The branch with [*] is the current working branch.
 
    ```bash
    git branch
@@ -63,26 +86,26 @@ Please be sure to conform to the coding standards used throughout our project an
    ```bash
    git checkout <branch to which you wish to switch>
    ```
-  
-6. **Make your changes**  
+
+6. **Make your changes**
    Once changes are complete, use one of the following commands to stage the changes to be committed.
 
    ```bash
    # Add all changes to commit
    git add .
-   
+
    # Add changes from one file to commit
    git add <file-name>
    ```
 
-   **Note on change management:**  
-   You can always use this command to see which changes are staged for commit and which aren't. 
-  
+   **Note on change management:**
+   You can always use this command to see which changes are staged for commit and which aren't.
+
    ```bash
    git status
    ```
 
-7. **Prepare to commit your changes**  
+7. **Prepare to commit your changes**
    Once your changes are ready and all files you wish to commit have been added (step #5), you'll create your commit.
 
    ```bash
@@ -94,7 +117,7 @@ Please be sure to conform to the coding standards used throughout our project an
 8. **Rebase the upstream branch** into your local branch(es)
 
    ```bash
-   git pull [--rebase] upstream develop
+   git pull [--rebase] upstream dev
    ```
 
 9. **Push your local branch** up to your fork
@@ -103,6 +126,6 @@ Please be sure to conform to the coding standards used throughout our project an
    git push origin <branch-name>
    ```
 
-10. **Create a pull request** 	
+10. **Create a pull request**
 
-	 [Create your request](https://help.github.com/articles/creating-a-pull-request/), making sure the title is as clear and descriptive as possible. 
+	 [Create your request](https://help.github.com/articles/creating-a-pull-request/), making sure the title is as clear and descriptive as possible.

package/README.md

@@ -0,0 +1,94 @@
+[![status of silex.me instance](https://monitoshi.lexoyo.me/badge/1525963562293-6552)](https://editor.silex.me)
+
+![Silex UI](https://github.com/silexlabs/www.silex.me/raw/gh-pages/assets/silex-ui.gif)
+
+## About Silex, live web creation.
+
+Silex is a no-code tool for building websites. It also lets you code when needed. It can be used online, offline or in a JAMStack project.
+
+Silex lets you create websites without coding, but it also has built-in editors for HTML, CSS, and JavaScript for when you need more control. It is used by freelancers and web studios to make real websites for real clients. Also Silex can generate templates or be integrated in a nodejs project, it has a plugin system and can integrate with headleass CMS and static site generators, it is part of the JSAMStack ecosystem since the v3.
+
+Brought to you by [Alex Hoyau](https://www.patreon.com/lexoyo) and [Silex contributors](https://github.com/silexlabs/Silex/graphs/contributors).
+
+Useful links
+
+* [Official website](https://www.silex.me/)
+* [Road map (please help defining tasks and prioritising)](https://github.com/orgs/silexlabs/projects/1/views/7)
+* [Bug report in Github issues](https://github.com/silexlabs/Silex/issues)
+* [Forums in Github discussions](https://github.com/silexlabs/Silex/discussions)
+* [Silex meta package with more source code](https://github.com/silexlabs/silex-meta)
+
+Here are the main features of Silex website builder:
+
+* Free and Open Source, open to contributions
+* Visual Editor: Silex offers a visual editor that allows users to create websites without needing to write code. It supports drag-and-drop functionality for easy website creation.
+* Online CSS Editor: Alongside the visual editor, Silex also provides an online CSS editor for more advanced customization.
+* Static HTML Websites: Silex is designed to create static HTML websites, which are fast, secure, and easy to host.
+* SEO Features: Silex includes SEO features to help improve the visibility of websites on search engines.
+* Editor UI: Silex offers features like fonts, visual CSS editor, publication...
+* Self-hosting Option: Users can choose to host their Silex website builder on their own server.
+* Community Support: Being an open-source project, Silex has a community of developers who contribute to its development and provide support.
+* Silex v3 > Silex is based on [GrapesJs](https://grapesjs.com/)
+* Silex v2 > Sync with Dropbox and FTP: Users can sync their Silex projects with Dropbox and FTP, allowing for easy access and management of files.
+* Silex v2 > Templates: Silex comes with a growing number of templates (both free and paid) that users can use as a starting point for their websites.
+
+## Getting Started
+
+### Online Version
+
+The easiest way to start using Silex is by using the online version provided by [Silex Labs foundation](https://www.silexlabs.org). Simply visit [editor.silex.me](https://editor.silex.me) and start building your website right away.
+
+### Desktop App (beta)
+
+There is a desktop application that you can install on your computer which may be faster since it uses your local files and it works offline. You can download the desktop app from the [Silex desktop  repository](https://github.com/silexlabs/silex-desktop/releases/latest).
+
+### Local or Server Installation
+
+You can also run Silex locally or on your server using `npx`, `npm`, or `Docker`.
+
+#### Using npx
+
+```bash
+npx @silexlabs/silex
+```
+
+This command will run Silex with the entry point being `src/ts/server/cli.ts`.
+
+#### Using Docker
+
+```bash
+docker run -p 6805:6805 silexlabs/silex
+```
+
+This command will run Silex in a Docker container with the entry point being `src/ts/server/index.ts`.
+
+#### Using npm
+
+First, install Silex as a dev dependency in your project:
+
+```bash
+npm install --save-dev @silexlabs/silex
+```
+
+Then, you can run Silex with the `silex` command. The entry point is `src/ts/server/cli.ts`.
+
+## Configuration
+
+You can configure Silex using environment variables and command-line options. All available options can be found in `src/ts/server/cli.ts`.
+
+## Contributing
+
+Contributions are welcome! Please read our [contributing guidelines](CONTRIBUTING.md) for details on how to contribute to Silex.
+
+## License
+
+Silex is free and open-source software licensed under the [GPL-3.0](LICENSE.md).
+
+## Dependencies
+
+The upstream projects we use in Silex are all listed in [Silex meta package](https://github.com/silexlabs/silex-meta)
+
+## Github stars history
+
+[![Star History Chart](https://api.star-history.com/svg?repos=silexlabs/Silex&type=Timeline)](https://star-history.com/#silexlabs/Silex&Timeline)
+

package/dist/client/css/admin.css

@@ -1477,13 +1477,6 @@ See http://bgrins.github.io/spectrum/themes/ for instructions.
 /* Commands */
 /* Fonts */
 /* Tools */
-@font-face {
-  font-family: "font3336";
-  src: url("../fonts/main-fonts.eot?v=20");
-  src: url("../fonts/main-fonts.woff?v=20") format("woff"), url("../fonts/main-fonts.ttf?v=20") format("truetype"), url("../fonts/main-fonts.svg?v=20") format("svg"), url("../fonts/main-fonts.eot?v=20") format("embedded-opentype");
-  font-weight: normal;
-  font-style: normal;
-}
 .gjs-is__grab, .gjs-is__grab * {
   cursor: grab !important;
 }
@@ -1564,63 +1557,6 @@ See http://bgrins.github.io/spectrum/themes/ for instructions.
   fill: #71b7f1;
 }
 
-.gjs-fonts::before {
-  display: block;
-  font: normal normal normal 14px font3336;
-  text-rendering: auto;
-  -webkit-font-smoothing: antialiased;
-  -moz-osx-font-smoothing: grayscale;
-  font-size: 5em;
-}
-
-.gjs-f-b1::before {
-  content: "Q";
-}
-
-.gjs-f-b2::before {
-  content: "W";
-}
-
-.gjs-f-b3::before {
-  content: "E";
-}
-
-.gjs-f-b37::before {
-  content: "R";
-}
-
-.gjs-f-hero::before {
-  content: "T";
-}
-
-.gjs-f-h1p::before {
-  content: "y";
-}
-
-.gjs-f-3ba::before {
-  content: "u";
-}
-
-.gjs-f-image::before {
-  content: "I";
-}
-
-.gjs-f-text::before {
-  content: "o";
-}
-
-.gjs-f-quo::before {
-  content: "p";
-}
-
-.gjs-f-button::before {
-  content: "B";
-}
-
-.gjs-f-divider::before {
-  content: "D";
-}
-
 .gjs-invis-invis, .gjs-clm-tags #gjs-clm-new,
 .gjs-no-app {
   background-color: transparent;
@@ -3729,11 +3665,13 @@ See http://bgrins.github.io/spectrum/themes/ for instructions.
 
 /*************RTE****************/
 .gjs-rte-toolbar {
-  border: 1px solid rgba(0, 0, 0, 0.2);
   position: absolute;
-  border-radius: 3px;
   z-index: 10;
 }
+.gjs-rte-toolbar-ui {
+  border: 1px solid rgba(0, 0, 0, 0.2);
+  border-radius: 3px;
+}
 .gjs-rte-actionbar {
   display: flex;
 }