lexoyo
commented
5 years ago Hello @fullofcaffeine !! It's great to see you back with lots of good ideas :)
As a matter of fact I am using silex for my business too so I recently added several features to customize Silex - for freelancers to create optimized versions of silex to fit their production needs and for hosting companies to integrate with their infrastructure. So these questions comes right in time!
I'd like to use Silex to create or edit fully static sites as an alternative to Middleman (the Ruby static site generator), for example. I think it could be great to quickly come up with landing pages to test ideas fast (a mix between unbounce and wix). Most of the time, I don't need the complexity of a site generator or a dynamic backend, and just need to get something (beautiful and functional) out there, fast to show and collect some data (i.e emails).
A mix between unbounce and wix, that is exactly what it is. And it integrates with Jekyll now, more on that bellow
I've read Silex can only edit pages created by it. Is this format documented somewhere? What is the metadata that it needs specifically? I haven't seen any way to edit the HTML source code of the page in Silex, am I missing something or is it not possible?
This is the answer which you will not like: the pages have special markup and a JSON object with params in it. Also in the editable version, the whole webisite pages are included in 1 single page. This is all cleaned up when the user publishes the website to host it online (it is split in multiple pages and json data is removed, as well as useless css classes etc.
But the real problem is that Silex has something special in order to provide the best editing experience, I decided that in the desktop editor, everything would be absolute. This makes it very easy to design like in photoshop or powerpoint, not like in dreamweaver... This is the same with wix. And not the same with the excellent grapejs which is an alternative to Silex (the only one I would consider).
So about that topic
1- it very is complex to write a script to convert any website to a silex ediatble template 2- it is very quick (less than 4h) to "silexsize" a website (clone it starting from scratch)
I'd like to host Silex myself and use it to quickly create and modify static sites. I currently use Ansible to provision new nginx vhosts in a server, so the workflow that I'm looking for would look like: 3.1) I provision the new vhost / domain with ansible; 3.2) I fire up my own hosted Silex and create a new site; 3.3) I deploy (publish it) using Silex. In 3.3, I'd like to push it to GitHub first so that the version is tracked and just after that, I'd like Silex to update it via FTP. I can always use a build server that is triggered by GitHub, but if Silex can do it, it'd be simpler and I could skip setting up a build server. Another possibility is for Silex to push to github, I then pull locally and use something like rsync or Capistrano to deploy, this can work for now. What do you think? I'm open to other ideas, any insights are appreciated.
I didn't know about ansible.. It looks complex to me, I am not a good ops.
It is easy to host an instance of Silex
Also very easy: you could save your website on github so that it is versioned. And setup the publication to push to an sFTP or your local machine (local works only if you use the ofline/desktop version of Silex).
Please feel free to ask, your use case is very interesting and I am willing to make it work for you. A few links to the roadmap which might be interesting to you:
- Silex for marketers
- feature request: standard set of components: #702
- Silex for hosting companies
fullofcaffeine
Hi @lexoyo and team,
I've checked Silex a few years ago and it has come a long way! Thanks for keeping it up and keeping it free and open :)
I'd like to use Silex to create or edit fully static sites as an alternative to Middleman (the Ruby static site generator), for example. I think it could be great to quickly come up with landing pages to test ideas fast (a mix between unbounce and wix). Most of the time, I don't need the complexity of a site generator or a dynamic backend, and just need to get something (beautiful and functional) out there, fast to show and collect some data (i.e emails).
I have a couple of questions regarding that: 1) I've read Silex can only edit pages created by it. Is this format documented somewhere? What is the metadata that it needs specifically? 2) I haven't seen any way to edit the HTML source code of the page in Silex, am I missing something or is it not possible? 2) I'd like to host Silex myself and use it to quickly create and modify static sites. I currently use Ansible to provision new nginx vhosts in a server, so the workflow that I'm looking for would look like: 3.1) I provision the new vhost / domain with ansible; 3.2) I fire up my own hosted Silex and create a new site; 3.3) I deploy (publish it) using Silex.
In 3.3, I'd like to push it to GitHub first so that the version is tracked and just after that, I'd like Silex to update it via FTP. I can always use a build server that is triggered by GitHub, but if Silex can do it, it'd be simpler and I could skip setting up a build server. Another possibility is for Silex to push to github, I then pull locally and use something like rsync or Capistrano to deploy, this can work for now. What do you think? I'm open to other ideas, any insights are appreciated.