I've worked on projects where OutSystems was used for public-facing websites, and my view is that it really depends on the type of content and who will be maintaining it. If your website is closely connected to business processes, approvals, user roles, or other application logic, then building it entirely in OutSystems is a reasonable choice. Everything stays in one platform, which simplifies development and maintenance. However, if the site is mainly content-driven—articles, news, documentation, PDFs, SEO pages, categories, and archives that non-technical users update regularly—a dedicated CMS like WordPress or Drupal is usually the better option. Their editing experience, content management features, and SEO capabilities are much more mature. In my experience, the best approach for many organizations is a hybrid one. Use a CMS to manage public content and let OutSystems handle the application side—workflows, portals, dashboards, authentication, and business processes. If needed, OutSystems can consume the content through APIs. That said, if your organization already has OutSystems and wants to avoid introducing another platform, you can build a CMS-like solution entirely in OutSystems. It's definitely possible, but be prepared to invest extra effort in creating a good content editing experience, versioning, publishing workflows, and SEO features that come out of the box in dedicated CMS platforms. 

So my recommendation would be: 

Business process-driven website: Build it in OutSystems. 

Content-heavy public website: Use a dedicated CMS. 

Need both: Go with a hybrid architecture whenever possible.

Hello.

As someone who still does Wordpress whenever possible, I understand your urge to have a CMS in OS. You get a lot of small wins in an instant. The question is the level of customization that you will need and if all that you need to developed still compensate the time saved reinventing what other platforms already have.

I would use a dedicated CMS for a good SEO and the users to have full autonomy.

I would consider doing it OS if it is a niche site with many custom pages or logic that you can't find in existing plugins, but in the end will always depend on the needs of the project.

I wanted to add to previous comments that, in case you would want a hybrid approach, a CMS like Umbraco Heartcore could work really well. Umbraco is a well established, pretty awesome CMS, and using the Heartcore version will allow you to have your pick of frontend. You could have OutSystems as your frontend and for whatever other usages you might need, and in parallel having Heartcore give you a CMS Backoffice and database structure to create and manage content.

Downside is that you would then have two separate applications to manage.

Hi @Rusyl Narito ,

I agree with the points shared above. OutSystems can definitely be used to build a CMS-style website, but whether it's the best choice depends on the project.

If the website mostly contains articles, news, PDFs, and other content that editors update often, a dedicated CMS is usually easier to manage and gives better SEO and content editing features.

On the other hand, if the website needs custom workflows, user-specific features, approvals, or integration with business processes, then building it in OutSystems makes a lot of sense.

For many projects, a hybrid approach is probably the best balance. Let a CMS handle content management while OutSystems focuses on the application logic and custom functionality. It saves development time and gives content editors a much better experience.

Hope this helps,

regards,

Manish Jawla