r/cms

Good day folks, hope all's well.

I will be getting real web hosting in the soon future, for now, I'd like to test the viability of an amateur pet project.

Do any of you good folks, know of a web host(s). I will trialing some plug-ins so these are essential too. This WordPress site is to be shared with a select group internationally. I looked into LocalWP, an option, but, limited.

If I can, I'd prefer not to go down the iFastNet route, they own, managed or sponsor nearly all at times feature rich, slow running WordPress, limited options free web hosts - InfinityFree, Byethost, AeonFree, HyperPHP, ProFreeHost. The subdomain names are blah (sorry), I guess as this isn't launched yet it doesn't matter the name I use I guess 😅

Before I play the waiting, beggars can't be choosers game, and take a punt again with InfinityFree 🥱

...are there any other web hosts besides, AwardSpace that run WordPress and if so, this will also serve as an addition to the toolkit?

I think I may need to stick hints above, but, I thought I'd ask you pros, in case there are any other potentials.

Many thanks and salute to your endeavours.

Running an agency. And need a reliable white label agency plan.

Hey everyone,

I’ve been working on content systems for a while, and one thing kept coming up with Next.js setups.

Getting a blog live is not that hard. But managing it properly as it grows is where things start to break.

Content lives in markdown or custom structures.
Metadata, formatting, and consistency need constant attention.
And things like SEO structure, readability, and engagement are handled manually for every post.

It works, but it doesn’t feel like a system built for ongoing content.

What’s interesting is that most setups also miss what happens after publishing.

Things like:

• built-in SEO structure (not just meta tags)
• visual elements like banners or infographics inside posts
• lead capture directly within the blog

These are usually added later with custom work, and they are not easy to standardize across posts.

So we started building something specifically for this use case.

The idea was simple:
Keep your Next.js frontend as it is, but manage your blog with a system that handles structure, SEO readiness, visual layers, and lead capture by default.

We recently got it working with Next.js setups, including subdomain and subfolder integration.

I wrote a detailed breakdown here: Nextjs Blog CMS

We’re opening it up in the next couple of days.

Curious how others here are handling blogs in Next.js:

• Are you sticking with markdown?
• Using a headless CMS?
• Or building custom workflows?

Would love to hear what’s working (and what’s painful) for you.

Hi everyone,

I just released a new version of Nodify, a Headless CMS built with Angular + Spring Boot.

🔐 What's new?

· OpenID Connect for Google, GitHub and LinkedIn

· Automatic user creation from external providers (zero‑touch onboarding)

· Role‑based access control (EDITOR / ADMIN)

· Profile editing (first name / last name)

· Dedicated "unauthorized access" page

🧠 Why Nodify?

· API‑first, decoupled architecture

· Micro‑frontend ready

· Content federation + real‑time WebSocket

· Multi‑language (i18n) already integrated

📦 Quick start

```bash

git clone https://github.com/AZIRARM/nodify.git

cd nodify

docker-compose up -d

```

🌍 Live demo → https://nodify.azirar.ovh

🐙 GitHub repo → https://github.com/AZIRARM/nodify

I’d really appreciate your feedback, issues, or contributions 🙌

Thanks for taking a look 🚀

Most of the content driven sites are meant to be static and i've seen people using markdown or MDX files in the repo. And I've also seen people using headless CMSes with a DB backend, where content lives outside the repo.

i'm curious what you all prefer and why:

• do you keep everything in markdown/MDX in the repo?
• or do you pull content from a DB or external API?

would love to hear the "why" behind your setup.

I just finished up a project with WordPress, and I'm just frustrated with how complicated managing content across websites, apps, emails, and social media is. We were pushing the same content to all of those, but had to end up rewriting or reformatting it every time. It got done, but it's inefficient, especially in today's context. Feels like there should be a better way to reuse content across channels without all the extra steps. Any insights will help!!

I am building a CMS to help people that manage restaurants manage their menu (item price for example). I have worked with many a CMS, but never built or designed one. Any good books/articles/UI Principles/etc. I should read before getting started?

I’m building an open-source CMS on top of Filament, and one challenge was turning the RichEditor into something more structured (block-based, not just WYSIWYG).

This write-up covers how I extended it to support:

• Block hierarchy (outline-style editing)
• Drag/drop reordering
• Slash commands
• Collapsible content

All without touching Filament core.

If you’re building CMS tools or admin panels, this might be useful:

Bludit v3.21.0.

Yo, fresh drop, version three-point-two-one, Bludit spittin' fire, CMS king on the run!

Flat-file beast, no database drama,

Lightning load, zero lag, pure rap armor!

Plugins poppin', themes drippin' sauce,

Markdown mackin', posts stackin' with force!

Doesn't seem to be a lot other than some WordPress themes but wondering what is good these days for a podcast website.

Hey r/opensource r/java r/angular

I've been working on a headless CMS called Nodify for a while. It's self-hosted, MIT licensed, and built on a stack I personally enjoy working with.

🔗 github.com/AZIRARM/nodify

The stack (no old school blocking stuff here):

· Java 21 + Spring Boot WebFlux (reactive, non-blocking)

· MongoDB with reactive driver

· Redis for real-time pub/sub and caching

· Angular 19 standalone components (not the usual templating stuff)

· Docker Compose for running everything locally

What Nodify does:

You spin it up, you get a REST API, a visual Studio for content management, authentication, file uploads, real-time updates. One docker-compose up -d. No backend code to write for the people using it.

Why I'm posting here:

I'm looking for contributors. Not because I need free work, but because I think the project could benefit from more perspectives, especially on the reactive side.

Areas where help would be great:

· Spring WebFlux / reactive MongoDB optimizations

· Redis pub/sub for real-time features

· Angular 19 components for the Studio UI

· Documentation (always needed)

· Testing (reactive streams can be tricky)

Not looking for:

· Generic "add star plz" comments

· Drive-by contributions without context

· People who hate reactive programming (it's fine, but this project uses it)

If you're curious:

Check the repo. Try the Docker setup. Open an issue if something feels off. I'm around to answer questions.

Again: github.com/AZIRARM/nodify

Tech stack in the open. No secrets. Just code.

#Nodify #HeadlessCMS #OpenSource #SelfHosted #MITLicense #Java #SpringBoot #WebFlux #ReactiveProgramming #MongoDB #Redis #Angular19 #DevCommunity #GitHub #ContributorsWanted #HiringContributors #OpenSourceContributions

Hi everyone,

I’m currently working on Nodify, an open-source project aimed at building a modern and efficient CMS. The idea is to provide a flexible, multilingual, and developer-friendly solution for content management.

Tech Stack:

• Backend: Java (Spring Boot, WebFlux, Reactive MongoDB)

• Frontend: Angular 19

• Infrastructure: Docker for deployment

I’m hoping to get feedback, advice, or even contributors interested in improving the project. Whether it’s exploring the code, adding new functionality, or optimizing existing features, your input would be incredibly valuable to push this project forward.

🔗 Here’s the GitHub repo: AZIRARM/nodify

Thank you so much for your time! If you have any thoughts, suggestions, or ideas, I’d love to hear them! 😊

If you ever wonder how to build modern hierarchical content such as documentation, study notes, or knowledge bases ?

Here to share a approach. It is to separate content from structure. Use agent-engineering.dev for content creation, and manage hierarchy in your own system using a self-referencing tree model.

Share solution to build Hierarchical Content on Top of a Headless CMS - Agent-Engineering.dev

Then link both using a slug via API.

This pattern gives you flexibility, scalability, and full control over how content is organized and delivered across platforms.

If you're building anything beyond a simple blog, check out this approach in detail: https://www.agent-engineering.dev/article/how-can-you-build-hierarchical-content-on-top-of-a-headless-cms

SitecoreAI is the AI-native evolution of XM Cloud. It brings AI-native capabilities into the authoring, content modelling, and developer workflow experience. The certification covers 9 competency areas including content modelling, headless architecture, GraphQL APIs, content serialization, and security.

A few things worth knowing before you sit the exam:

• Content modelling is tested deeply. Know your templates, template inheritance, and how content models map to component datasource structures in a headless context
• GraphQL APIs came up regularly. Understand Edge Delivery APIs, the difference between read-only and authoring APIs, and how webhooks trigger on workflow changes
• SSG rendering strategies were explicitly tested in the web development section
• Questions are mostly scenario based. You need to think through the right approach for a given situation, not just recall definitions
• Read every question twice. I nearly got one wrong because I missed a single qualifier word on first pass

If you're already working with a headless CMS and have experience with GraphQL and Next.js, this certification is much more achievable than it sounds.

Happy to answer any questions about the exam or SitecoreAI in general.