I need to put a blog in a Wappler website.
I only know about WordPress. Is this what I should use?
Bonus if it can send new blog posts as a newsletter via e-mail (but the list of e-mails will probably stored in the website's database, not the blog's)
Sure with WP you would have some pre-made templates you could use, but curious as to why with someone of your vast Wappler knowledge would not build it properly to do what you want it to do with Wappler?
Your Wappler expertise could probably pound that out in less time than it would take to try and fiddle with a pre-made to do what you want.
Was thinking the same Brad!
Is this an opportunity to leverage a headless CMS? Especially if the Wappler site already exists (ie less foundational build)?
I think @Hyperbytes was putting together a video tutorial on how to do this with Wappler, you might check in with him.
Yes, do you have any suggestions?
I'll answer to the others tomorrow 
What's the 'catch' buddy?
The site is already up & running with its database setup?
You want to avoid modiyng its structure and database and just create a new independent solution (database, CMS...) that will drive a blog for it?
The blog obviously will have to share the original database (users), right?
*too many questions but we really don't understand what makes you "ask" of it...
None from the above is a problem for you, but I suppose you ask to get some feedback on how would anyone aproach this, right?
Unfortunately I don’t have first hand experience implementing one. But if I were facing a similar requirement I think that’s where I would start.
That was superseded by the community portal series which is basically based on blog structures
@Apple any particular aspect you are unsure of?
At basic level it is just a table (title, content etc) with subtables for comments/reactions etc. You can set up the blog content to be populated with summernote
Not sure if this is any good for you but may help.
I’ve just created a booking system, it runs from a wappler website that is created in the fly for each of my customers.
Some of them already have very basic websites and wanted to include the booking system on them.
I created a bare bones booking page with no menus, headers or footers. I then included that url in an iFrame which they can include in any page they wish. It all works perfectly.
I'd be fine developing the front-end page for the blog to fit inside the existing website, but I was looking to avoid building an interface for admins to write blog posts. I have some aversion to writing admin panels 
True, I'd lose time trying to make the pre-made template to match the existing website. In Wappler, I'd just avoid making a admin panel to write blog posts, feels like a waste of time to me when I guess other softwares do it better. Maybe I need to look into some of these "headless CMS". I haven't really dabbled in this "Summernote" stuff, kind of don't have too much patience these days 
Yes, I want to know how others would do this
Almost, still in development.
Correct, but I'm open to all ideas.
Not sure. I mean, there are some newsletter softwares where you can add and remove e-mail addresses through an API Action (to add or remove users). It's not a requirement the blog to share the database in that sense. I'm not planning to have comments, at least not yet.
@ TMR thanks, an iframe wouldn't work here. Trying to make it SEO-friendly
I would stick to Wappler for everything. Making the admin area to manage the blog should be pretty straightforward and quick.
I've built a blog on a couple of sites and it's been fine.
I have set up a couple blogs with Wappler. One going back to early contributor release days. Although it is my personal site and I don't update the blog very often it still works perfectly to this day. And was seriously easy to set up. Even I could do it. 
Very nice idea! A blog site type of module ("plug-in") that could be enhanced on all of the sites you have or will do in the future...
I don't think so if it could be just installed in all of your sites with easy
So, I think we are talking about an independent blog with its own user table.
I would have to think of 2 alternatives:
And if all of the sites that I'm building has already a users/roles/permissions tables management then I would go with the first option (a "mirror" to the original site's with just a reference/primary key the user_id)
Concerning the commenting/reactions, I would strongly recomment that the blog will have the structure/ability (database and operating modules on front and back-side) to handle them.
So, you can add a switch to enable them or not for each installation of the blog site/module
So, some of the basic parameneters I would have to define in the blog's database settings would be something like:
These are my first thoughts brother... Nothing special, nothing in depth!
As you just said: