Just reload PG and it should be there!

We will if we get enough user requests for it. In our tests Gemini Pro 1.5 was not that great at tasks in Pinegrow. Do you use it successfully for web development?

Gemini is trash! , it's one of the worst models at least for coding so no use to add that yet. How did mini compare to sonnet? Have not had time to test out mini yet and compare it to sonnet but sonnet is by far the king of coding at this point.

@@wizard-of-ai in a quick "merge the content into template" test that is shown in the video, gpt-4o-mini did better than gtp-4o... Quite a surprise. Yes, Claude Sonnet 3.5 is the best overall model at this time, at least when it comes to using AI in Pinegrow.

@@wizard-of-ai wow, harsh statement. Do you have a recent comparison article or other reference for me please? I really would like to know if I should switch to another vendor. But as I’m on #Google #Workspace and #GCP, too, it makes more sense to use #Gemini.

@@maikvanrossum Sorry i do not have any references since i did the testing myself. However there are a lot of content creators and AI specialists who has detailed test cases. I am a developer myself and what i did was to test Gemini, Sonnet and 4.o to test and see how far i would get building various of web apps and WordPress plugins just using the various of models. For both stand alone React and html web apps sonnet was a clear winner and with using sonnets artifacts it was very nice to be able to test what it built in the browser without having to add the code to a code editor. For WordPress plugins sonnet was also a clear winner with following the instructions and making a better Ui and code. Second place was 4.o and Gemini was far behind on everything. I would advice you to maybe do a test month of sonnet and see what it can do because it is very good and maybe within a month Gemini has improved so you can stay in the Google ecosystem if that is what you want. This AI space is moving so fast so maybe next week the roles are turned around :)

Thanks @andreasgerlach4963, it is a good point. Will include the code quality in future tests. These tests were done with Bootstrap and Tailwind templates. In my experience, AI works best with those because there is no need for the model to consider any CSS styling / stylesheets outside of what is given in HTML itself.

Yes, we will add more providers now that we have the multiple-providers architecture in place.

@@pinegrow good tor hear! 😊 Updated to version 8 👍🏻

exactly - it's actually more difficult in some cases than just learning CSS.

The Inline SVG image works everywhere. Floating tools are only available for Bootstrap and Tailwind. But you can use any CSS framework / custom styles to color SVGs with the CSS color property.

@@pinegrow yes I meant the ‘included’ frameworks, so also Tailwind 👍🏻 Great, thanks!

For now it only works with inline CSS. For this reason, the AI assistant is most useful with Bootstrap and Tailwind CSS.

At the moment the Founders Club offer stands as it is. Sorry, that FAQ items was out of date. I have updated it. Once we develop more fine-grained subscription plans we might bring in bundle pricing.

No worries, the desktop Pinegrow is not going anywhere and will remain our most powerful editor.

Not at the moment. The static CMS from desktop Pinegrow app could be ported to the online version, but not sure how suitable the UI is for end-clients. Wouldn't it be too complex, compared to WordPress and similar?

@pinegrow personally. I think it could be a great way to pair simple static websites to some semblance of editing. While the ability to tailor the actual CMS appearence of Pinegrow would be welcome, I think it could currently work already, as long as the developer keeps it simple enough. A client could just simply edit the site inline, an ability that many CMS's don't have out of the box and if they do, require a fair amount of technical expertise to make it happen. In Pinegrow CMS this is native and can be opened up to clients with the simple click of a button. I'm sure I'm not alone in thinking this is pretty convenient when all a client requires is to be able to update some text. As I understand it, Pinegrow CMS even supports blocks. So a similar editing experience to Gutenberg blocks (up to a point, as it would only be able to serve static content, not dynamic ones) could be achieved fairly easily. Sure, the way it is implemented now may make the interface look a little overwhelming to non-technical users but I'm sure most would easily find their way with about an hour of hand holding by the developer (though indeed, the ability to tailor the CMS appearence a bit more to client expectations would always be welcome as I said earlier). I believe (and have long believed) there is a broader untapped market here. With the rise and entering into the mainstream of the so-called jamstack approach to websites, it seems to me there is a great lack of reliable and/or affordable CMS solutions for these projects. Sure there are things like netlifyCMS (which seems like it is actually nothing more than a glorified markdown editor) and Cloudcannon (which is good but also too expensive if you ask me), I think Pinegrow online could leap into that open space that still exists here. Especially since it wouldn't require the use of a static site generator at all and could work with any static HTML project while still retaining much of the same features. This would certainly be helped by good integration with third party hosting providers like Vercel, Netlify, Github pages (especially that last one as it allows hosting for free up to a point). It seems to me like Pinegrow could be a great CMS solution for the often relatively simple and static websites for businesses who benefit from the jamstack approach in technical terms when they don't require a beefy server capable of handling dynamic content (but are in my opinion still a bit hamstrung by the high costs of existing CMS editors for it). Anyway, that is my perspective on the matter.

@@roelvaneyken211 thank you for the detailed feedback. Will keep this option open and observe the level of interest for this feature.