- value:'Why do people still build their own CMSes and frameworks?'
created:
- value:'2024-12-31T00:00:00+00:00'
changed:
- value:'2025-05-11T09:00:03+00:00'
promote:
- value:false
sticky:
- value:false
default_langcode:
- value:true
revision_translation_affected:
- value:true
path:
- alias:/daily/2024/12/31/build
langcode:en
body:
- value:|
<p>A few times in the last couple of years, I've come across companies or agencies writing their own CMSes or frameworks.</p>
<p>Not as a learning exercise, which I think every Developer does at some point as part of their learning, but to host production applications.</p>
<p>With so many free and open source options - there are Drupal, WordPress, Symfony and Laravel just in the PHP ecosystem - why would people use custom or proprietary CMSes or frameworks?</p>
<p>One reason is <a href="/daily/2024/12/30/domain-names">vendor lock-in</a>.</p>
<p>If someone is locked into your CMS, framework or hosting platform, it's difficult for them to move away.</p>
<p>That's one of the main benefits of open source software.</p>
<p>There isn't just one company that provides services for it and customers can choose who they want to work with.</p>
format:full_html
processed:|
<p>A few times in the last couple of years, I've come across companies or agencies writing their own CMSes or frameworks.</p>
<p>Not as a learning exercise, which I think every Developer does at some point as part of their learning, but to host production applications.</p>
<p>With so many free and open source options - there are Drupal, WordPress, Symfony and Laravel just in the PHP ecosystem - why would people use custom or proprietary CMSes or frameworks?</p>