I’m fairly new to Wappler and trying to build a basic CMS with PHP (just simple create/read/update/delete content). I’ve been watching tutorials and reading existing posts but most of the material seems quite complicated or aimed at more advanced workflows, and I’m struggling to find something suitable.
I have watched the Boutique one and Wappler QuickStart videos. They are great but I am finding it very difficult to pick out the methods I need.
I’d really appreciate pointers to a straightforward tutorial (video or written) that walks through building a basic CMS in Wappler using PHP and a database. (Even if not PHP NodeJs would be fine as I can adapt).
I’ve seen that there are full video series on the YouTube channel which cover dynamic sites but I haven’t found one that is for a simple CMS use-case.
No offence taken, am actually planning an update with version 7 but on a much smaller scale. To be honest the last one involved a lot of repetitive coding and i got really bored with it towards the end.
Also i have new screen recording software which produces much sharper videos.
Basically just waiting to see how the new docs integration develops in Wappler as I would love to build videos directly linked into that functionality rather than purely stand alone. Is that something in the pipeline @George
Blimey, that would be amazing, I was being tongue in cheek!
I am redesigning my website around a simple, CMS built with PHP and MySQL.
The site is driven by a central content table that holds main pages, blog posts and landing pages, with each item published using SEO-friendly URLs generated from slugs (held in database) rather than dynamic URLs.
Each page to have shared elements such as a collapsible navigation bar and a Contact Us form with a honeypot are handled through PHP includes.
If possible an XML sitemap is generated automatically from the content table.
The back end is secured using hashed passwords and provides straightforward CRUD functionality, allowing me to create and update content, review enquiries and mark them as processed, without unnecessary complexity.
I confess, you have basically described the first parts of my original series!
Not going to redo that in a few days.
Every backend database function just resolves to a basic CRUD action.
Can you focus on something more specific not readily available via existing content.
As you work your way through it, I would suggest start building and ask lots of questions here. There is lots of help here. We all created our first project at one time. No such thing as a stupid question. We are here to help. You got this.