r/cms

Howdy all I've decided after many years of using WordPress for my own personal websites as well as client sites that I want to shift away from it entirely if possible. I don't want to do that in the form of an alternative CMS platform like Drupal for example. Instead what I'm exploring is building my own custom one of one contact management system that's entire build process so far has been directly attacking the things that as a developer I have had problems with when dealing with WordPress. Whether that's the security vulnerabilities, the plug-in nightmare market, things breaking with a simple PHP version update, etc I've been slowly building something that's starting to take shape into a pretty capable content management system that's not quite ready to replace any legacy content management platform like WordPress. But it's getting pretty darn close to being something that I'm comfortable with utilizing at least at this point for personal projects, hopefully client projects in the future.

I want to make sure that I'm hitting the mark here and would just be interested in hearing from other individuals familiar with WordPress and it's at this point legacy problems whether that's focused on its vulnerabilities, it's capabilities, it's ease of use... Etc. I would love to hear from developers who've used WordPress at the deepest level and just to get a list of ideas or features or improvements I can make upon in my system that I haven't thought about yet. I look forward to hearing from everybody about your ideas.

I know a bit of programming from long ago and understand the concept, but know nothing about ExpressionEngine. I'd like to volunteer to streamline or edit some changes behind the scenes for my work place. For example, on the backend of a form, staff currently has to edit a new email address in three similar places - as an idea of a change I'd like to learn to do.

What can you tell me about EE and is it easy to learn? Best way to learn? Worth it? It's not in my job description, but I love to learn and figure that it doesn't hurt to learn a transferable skill - unless EE is becoming outdated?

I'm investigating CMSs for a new website and one of them claims 100% pagespeed index for all pages created using the CMS, is this an important aspect nowadays ?

it's easy to use but I'm not sure if the PageSpeed index score should have a high or low priority in my decision.

Would WordPress or another popular CMS do the same easily ?

Thanks!

Nous vous présentons Deltacms, un CMS sans base  de données, open source sous license GNU GPL V3 :

–      responsive, il s'adapte automatiquement à tout type d'écran,

–      administration en français, espagnol  ou anglais,

–      les données sont conservées dans des fichiers json, faciles à sauvegarder,

–      Deltacms possède de nombreux modules : blog, news, agenda, statistiques, formulaire, diaporama, agenda, galeries d’images et de vidéos, livre d’or, sondage, galerie de photos géolocalisées avec cartes,…

–      Il possède également des plugins simple à installer : calendrier, transfert d’images, chat, blocs éditables, fond d’écran vidéo,…

–      édition des pages avec Tinymce, gestion des fichiers avec Filemanager,

–      Installation sur votre serveur par un simple glissé déposé avec FTP,

–      administration complète dans le site, sans passer par FTP,

–      développé en France.

Plus d'informations sur son site principal => https://deltacms.fr/

Démonstration en ligne => https://demo.deltacms.fr/

Forum => https://forum.deltacms.fr/

Merci de votre lecture, cordialement

Choosing a CMS is one of those decisions that seems simple at first, but can have a long-term impact on how a business manages its website.

Many companies start by asking, “Which CMS is the best?”

A better question might be:

“Which CMS fits the way our team actually works?”

For a business website, a good CMS should support more than just publishing pages. It should make content updates easier, support SEO, allow room for growth, and keep the website manageable over time.

A few things worth considering before choosing a CMS:

Does your internal team need to update content regularly?

Is SEO important for your website strategy?

Will the website need ecommerce, booking, memberships, or multilingual pages later?

How important are speed, security, and scalability?

Do you want a simple visual editor, or do you need more technical flexibility?

Platforms like WordPress, Webflow, Shopify, Drupal, and headless CMS solutions all have their place. The right choice depends on the business model, content needs, technical requirements, and long-term goals.

From a business perspective, the CMS should not only help launch the website. It should also make it easier to maintain, improve, and grow after launch.

Curious to hear from other business owners, marketers, and developers:

What CMS has worked best for your business or clients, and what made it the right choice?

A question we hear often: Should my business website be built in WordPress, or should it be coded from scratch with HTML, CSS and JavaScript?

The honest answer: it depends on what your website needs to do.

WordPress is a strong choice when you want flexibility, easy content updates, blog posts, landing pages, SEO tools, and a system your team can manage without calling a developer every time you want to change a sentence. It is like having a well-organized office: many tools, many options, and yes, occasionally one plugin that behaves like it had too much coffee.

Core HTML/CSS/JS is better when the website needs to be very lightweight, fast, secure, and custom-built without extra systems running in the background. It is cleaner, more controlled, and often perfect for smaller business websites, landing pages, or highly tailored front-end experiences.

So which is better?

For most businesses, WordPress is better when content management matters.
Core HTML is better when speed, simplicity, and full control matter most.

The real mistake is not choosing WordPress or HTML. The real mistake is choosing a platform before understanding the business goal.

A good website should not just “exist online.” It should load quickly, explain clearly, build trust, and convert visitors into customers.

In short: WordPress is not magic, and HTML is not ancient history. Both are excellent tools when used for the right job.

What would you choose for a business website: WordPress or custom HTML?

[résolu]

Bonjour à tous,

Je sollicite vos lumières pour un projet d'auto-hébergement local.

Je souhaite mettre en place un site communautaire pour les habitants de mon lieu-dit (nous sommes une cinquantaine de voisins).

L'objectif est de garder le contact, de s'entraider et d'échanger sur divers sujets du quotidien :

Jardinage (conseils, troc de graines/plants)

Entraide (dépannage, gardiennage d'animaux, prêt d'outils)

Organisation d'événements (fête des voisins, repas partagés)

Infos locales

Le profil des utilisateurs :

La grande majorité de mes voisins est assez âgée et très peu à l'aise avec l'outil informatique.

L'ergonomie, l'esthétique et la simplicité d'utilisation sont donc mes critères absolus. Il faut que ce soit aussi intuitif qu'un tableau d'affichage de mairie, mais en version numérique.

Mes contraintes et besoins techniques :

Auto-hébergement : Je vais héberger et administrer la solution moi-même à la maison.

Sécurité / Vie privée : L'accès doit impérativement être restreint par un mot de passe global ou une inscription validée. Pas de référencement public.

Fonctionnalités : Chaque voisin doit pouvoir créer son espace, publier des messages, ouvrir de nouveaux sujets et répondre aux autres simplement (idéalement avec un fil de discussion clair).

J'ai pensé à un CMS classique (type WordPress avec un plugin de forum/communauté).

Selon vous, quelle est la solution la plus user-friendly pour des seniors, tout en restant légère et stable à auto-héberger ?

Merci d'avance pour vos retours et vos partages d'expérience !

Christian

Who hates the WP ACF setup process?

I’ve been messing with this Live CMS plugin and i gotta say the versioning thing is the part that actually doesn’t suck

it’s this wordpress plugin, basically lets you edit shit inline on the frontend instead of dying inside gutenberg.

You simply mark fields with html comments like <!-- lcms:text hero_title --> and it makes them clickable in orange fields.

but the versioning? that’s where it gets interesting.

Every time you hit publish it writes your json draft to the db and dumps a timestamped snapshot to your WP site files, yes, double secured your contents, and made portable!

There’s a little clock icon in the toolbar, click it, you see all the old versions, preview them, restore one. it

Inline edit with versioning

Actually works. reset button is clutch too — screwed up your draft? reset throws away the json and pulls the last published db state back. Saved my ass twice this week the whole thing is stored as json files instead of acf.

You can version control it. not perfect, the code is kinda messy in places, but after years of watching clients butcher pages in elementor i’ll take it.

Appreciate anyone could comment this feature.

My WordPress website was hacked, and I’m seeking a more secure and reliable platform for my website.

A new version of Grav for a new era

Grav 2.0 is a modern update to the venerable Grav 1.7 release that was launched in 2021 and has received over 50 point releases since then. Grav 2.0 is a whole new take on Grav, it's still a PHP-based flat-file CMS that focuses on speed, extensibility and flexibility, but now it has a first-party API that makes it a full-featured "headless" CMS, as well as a new SvelteKit5-powered SPA-based Admin2 plugin. Still fully customizable via 3rd party plugins, just like you would expect of Grav, but faster, and more secure.

Grav 2.0 also has an MCP server that works in conjunction with the API, to make it super easy for AI agents to work with. AI already has a great understanding of Grav as it's been around for over a decade, but we now have dedicated Agent "Skills" that enable the easy porting of 1.7 plugins and themes to 2.0, as well as useful skills that help review plugins for correctness and functionality.

The getgrav.org site also got a major redesign as it had not been updated in years. As part of this I migrated our Discourse based forum back to a Grav-native "forum-pro" (will be released publically soon) solution. Another service we have brought in-house, is our translations.getgrav.org which replaces our Crowdin solution we have used in the past.

Grav has always been a great platform for documentation, and now our Docs are powered by Grav 2.0 and our latest Helios documentation theme as well as our own YetiSearch search engine to make them even more readable and functional. I've been blogging about the process and here's a few posts that will give you a good idea:

• https://getgrav.org/blog/state-of-grav-2026
• https://getgrav.org/blog/grav-2-admin-next
• https://getgrav.org/blog/grav-2-twig-content-security
• https://getgrav.org/blog/migrating-to-grav-2
• https://getgrav.org/blog/new-getgrav-org
• https://getgrav.org/blog/grav-2-forum-pro

And of course, the Grav 2.0 release article: https://getgrav.org/blog/grav-2-stable-released

Find out everything you need to know about Grav and the 2.0 release on the official site: https://getgrav.org

Thanks!

-- Andy

Does anyone give me idea what should be salary for 7-8 years of experience in Guidewire developer? Any suggestion which company can give good compensation