Skip to content

FAQ

A few questions that come up often. For everything else, ask in the community forum or the chat.

Which browsers does Silex support?

Silex is regularly tested on the latest two versions of Chrome and Firefox on desktop. These are the only officially supported browsers.

  • Other Chromium-based browsers (Edge, Brave, Opera, Vivaldi) usually work but are not part of our test matrix. If you hit a bug, please reproduce it in Chrome before reporting it.
  • Safari has known compatibility issues with parts of the editor. Use Chrome or Firefox if you're on macOS.
  • Mobile browsers are not supported for editing — Silex is a desktop tool. (Sites built with Silex work fine on mobile, of course.)

If you're stuck on an unsupported browser, open an issue and we'll consider expanding support based on demand.

Why don't margin-left and margin-right do anything on my button?

You probably want to center the button. Margins behave according to the CSS box model, not according to "this should center it." For block-level elements, margin: 0 auto centers horizontally; for inline elements, margins on the left/right only push siblings. Buttons can be either, depending on their display property.

If margins seem to do nothing, the element's display and parent layout are the culprits — not Silex. Silex follows web standards strictly, with no shortcuts.

Read the canonical reference: The box model on MDN.

Can I integrate Silex into my own software (Symfony, PHP, custom app)?

Yes. Silex is designed to be embedded. Four integration paths:

  1. Hosting providers — write a custom hosting connector so users publish to your infrastructure. See Hosting connectors.
  2. Cloud services — write a custom storage connector so users' files live in your cloud. See Storage connectors.
  3. Components and HTML Box — embed any HTML/JS/CSS via components or the built-in HTML box.
  4. APIs — extend both client and server via the plugin API.

The AGPL license allows commercial integration. If you sell websites built with Silex, you're fine — just don't strip the license from the code.

Can I use Silex as a white-label drag-and-drop builder in my SaaS product?

Yes, the AGPL license permits it. Silex is closer to Webflow than to Wix: it expects users willing to learn web concepts (HTML structure, CSS classes). It's a fit for makers, agencies, and technical end-users.

If you need an easier, more beginner-friendly builder, you might prefer one of these alternatives:

What license can I use for my Silex plugin?

Any license, including proprietary.

Plugins are not bundled with Silex and use the documented plugin APIs (client and server), so they're not derivative works of Silex. You can publish your plugin under MIT, Apache, GPL, or a commercial license — your choice.

See Creating plugins for the plugin API.

How do I share my GitLab project with the Silex maintainers for debugging?

When you report a bug on the community forum, sometimes a maintainer asks to look at your site. In this case you will want to share your site with them - the editor URL (https://v3.silex.me/?id=...) is not enough, it only works for you, since it relies on your own login. They will need a read only access to the GitLab project where your site is stored.

To share access, invite the maintainer as a project member on gitlab.com:

  1. Open your project on gitlab.com.
  2. Go to Settings → Members → Invite members.
  3. Enter the GitLab username of the maintainer (for example, lexoyo).
  4. Pick the Reporter role (read-only access, enough for debugging).
  5. Click Invite.

Then post the gitlab.com URL of your project (e.g. https://gitlab.com/your-username/your-project) in the forum thread, it is safe, only them can access it read only. They will be able to suggest changes on gitlab.com and you can review them and accept or reject them then.

More

Edit this page on GitLab