Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

eleven0's avatar

Showcase Site for Your Application, Laravel or Wordpress?

Now that I am making some progress with my application, I have been looking into how I would run my web site (already looking into forge). I need a company front website which will describe my application's features, pricing etc... This has no connection to the application at all, other than providing a log-in link to the application.

My question, I figure wordpress site would be more beneficial as I can benefit from their plugins, themes etc. Also, I dont also have to spend time developing the showcase website. Is this common? Or should I just develop it on Laravel? How do you guys do it? Again, I dont need any connection between them. Can I get some opinions?

So my site configuration would be;

mysite.com --> wordpress installation (Solutions, Features, Pricing, About pages)

app.mysite.com--> laravel app directory

From a maintenance side, What are the advantages or disadvantages of this configuration?

Edit: Is it possible to deploy WP sites with Forge?

Thanks in advance.

0 likes
5 replies
Nash's avatar

AFAIK, it is quite common to do it like that. If your showcase website is no more than a few static pages with content that rarely changes, it could be easier to just make them with Laravel. But if you need multiple pages with easily modifiable content and perhaps a blog, Wordpress or some other CMS might also be a good solution; it's up to you (could also be just a separate blog). I would suggest keeping them on separate servers so they don't affect each other in case of problems, e.g. if someone takes down/gains access to the server through a vulnerable WP plugin or vice versa.

douglasakula's avatar

@eleven0

I would only use wordpress if I needed a blog for the website. For things like pricing, features, about us - seem like static content - which I would get a nice html theme on themeforest and use it on laravels blade templates. In my opinion - if the content on the company website will change weekly - then you are better of with a content management system that has plugins thought through like wordpress. But if the content is static - maybe change once in 6 months or a year - you can do your SEO and other things on site using laravel

RyanPurcella's avatar

If you want something built on top of Laravel, Statamic (https://statamic.com/) might be a good choice instead of Wordpress. Wordpress code isn't as clean, elegant, and flexible as Laravel code. Custom configuration of Wordpress can be time consuming and tedious. Additionally, the plugin ecosystem of Wordpress isn't always secure because good testing practices are not commonly used. However, if you plan to just use a generic wordpress theme or a paid theme with minimal customization, Wordpress isn't a bad choice. Here is a quick overview of the main differences: https://statamic.com/why . Statamic costs $199, but well worth it when it comes to user experience and the ability to quickly customize, extend, and integrate with your existing application.

ohffs's avatar

I've been playing around with gridsome a bit - just deploying a little test site to netlify. It seems to work quite nicely - if you update your site and push to github, it's rebuilt and deployed by netlify without you having to do anything, And no server/hosting to think about :-)

Nash's avatar

Wink by Laravel core developer Mohamed Said also looks really promising, though it is still in its early stages.

Please or to participate in this conversation.