Revised feature request as per the title.
Could you give a link to the product as there are many ghostjs projects - the one on npm is an UI test runner…
Sorry, here it is: https://ghost.org/
What does it do and is it something that would commonly get set up?
My concern is that already there is so many external setups when setting up a project that Wappler will get so bloated and become unusable to the average user.
Especially adding features that cost users extra to use. I feel it is getting out of hand already.
Hey brad. If you follow the link and you’ll see what it does.
However, yes CMS’s are common in the world of web and web projects. It’s a super lightweight, rapid CMS that would be a nice addition and enable users to not worry about needing to proxy in a wordpress or other onto the main domain or host on a sub domain etc.
I do 100% understand where you are coming from though. It’s just an idea that might be of interest to the team - we’ll likely implement ourselves anyway.
I did, and have no idea what it does. 
Think super fast, lean and lightweight publishing platform - as a very good alternative to the bloated Wordpress (CMS). Host/manage your blog content, newsletters and even distribute newsletters etc.
But what is the use case? How would ghost integrate with Wappler?
1 Like
I’ve already answered to that in the response to brad above.
With Wappler you can build websites, web apps, mobile apps.
Most websites desire content publishing for their blog content etc. hence why Wordpress is so popular, initially as a blogging platform and now that successfully hosts and runs entire websites.
If I want to achieve the same with Wappler say, for our marketing site and have our content published on the main domain then I’d need to reverse proxy this, or alternatively, we just use a different platform (e.g. Wordpress) and host on the sub domain.
Integration into Wappler would remove the need to build out the entire CMS platform, and provide a ready made, tried and tested content publishing platform to compliment Wappler’s website building power. Of course you can build it yourself in Wappler. Just an idea - like I said, we’ll be doing it ourselves - so thought it was worth mentioning in case there was interest from the forum.
It is probably my fault or maybe it’s too late here so please bear with me 
I still fail to see how it would integrate with Wappler.
As far as I know ghost is a full fledged standalone publishing platform that includes templates to be used. You install it, run it, set a template, create content and publish. Then people visit your blog
Or do you mean just using the headless cms feature so you can create content and then call the API from wappler and render the content on a page built in wappler?
Ghost Pro is, but the open source ghost projecct can be integrated directly into projects which is what we plan on exploring.
All good Jon, I’m sure the team will align with your thoughts and expertise - this can be removed if they see no validation in it.
https://strapi.io/ has been mentioned a few times before. Would that cover your needs? I just have the impression from what you are saying that you are looking for a headless CMS to handle content, but want to use Wappler to display that content thus the integration you are asking for.
Another option is that you want Wappler to handle the deployment via docker of a ghostjs instance.
If not any of those I truly need to go to bed and look at this with fresh eyes tomorrow morning 
I think mostly a terminology issue in my side.
Revised the feature request.
1 Like
Can I throw in my thoughts? What I’ve been looking for for some time is a way to allow site owners to edit page content with the most flexibility.
In the old days I would use TinyMCE and attach it to a textarea. That would allow site owners to write their content with WYSIWYG features so it could include images, styling, layout, etc. The whole HTML would be stored in the textarea and then saved in the database. The page would then render that HTML.
What I’m looking for is a similar solution in Wappler. Summernote goes part way but it would be great to expand on that and allow more powerful page-building features. GrapesJS.com looks like the ticket but I’ve not had a chance to properly test it out but am always keen to hear other people’s experiences.
I’ve built dozens of websites with Wordpress including creating my own themes but the end result of a Wappler-built site is way better than a Wordpress one so I’d like to move away from Wordpress completely.
I don't really understand these requests for using external CMS systems with pages built with Wappler. Why not just build a custom CMS with the components available in Wappler?
A CMS is nothing but CRUD pages which allow the users to Insert, Update and Delete records in the database. You just customize these CRUD pages with the options they need for their website.
And yes, that's the idea of the editors like Summernote - you attach it on your Insert/Update record pages so the users can style the text as per their needs 
3 Likes
I’m completely with you here, @Teodor. Maybe someone could write some kind of how-to on this? I’m fine with all the CRUD workings, completely comfortable with Wappler, and would want a solution that’s all within Wappler but I’m just not sure the best way to actually structure it all - the database structure, how to set out the editors giving maximum flexibility and ease of use, etc.
I suspect something along the lines of a table containing elements, and they are then strung together to make up the page? I would do it all using Bootstrap 4 layouts so an element might contain a value for the column width, offset, etc.
And the solution needs to be easy to port across to other projects so I don’t need to keep rebuilding the CMS.
Does that make sense?
For me personally, any version I build would be of lower quality and reliability than say the ghost.org project - and maintaining our existing blog, and expanding upon it is the main focus, whereas the build of a CMS is low priority for us - so imply integrating a third party who focus on, and specialize in such a publishing platform is just a no brainer for me. I get that his can all be built in Wappler, but I’m focusing my Wappler time on the app itself, and would rather just let another service handle the CMS.
I think we would want to say anyway from something like ghost.org as it appears you must use their hosting, I would agree that having a headless cms integration would be great but @Teodor has a good point why not build it in Wappler. To answer that question I think it would speed up the output of a website that needs CMS features using a pre-build system but someone like myself that would be learning curve of yet another product but I may not have the skill set to build my own CMS.
Maybe ghost is too specific and very focused on blogging.
Something like Strapi would make more sense as it would cover more ground. They even have support for ejs templates.