TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Ask HN: Do you use an in-house CMS?

8 pointsby jessehorneabout 6 years ago
Do you use an in-house CMS? If so, why? What are the pro's and con's of using it? Have you considered a custom solution over something built on top of WordPress or any other popular system? How should a Web Development agency go about providing in-house custom CMS solutions? What difficulties would that company face while marketing such services?

1 comment

markwillis82about 6 years ago
We used to have our own in-house CMS built in .Net (at least 10 years ago) and it was a pain to maintain and provide updates for, however we replaced that with MODX - which was better and we helped in the community alot and pushed changes back. It was nice knowing every line of code was ours - and having all the expertise inhouse was a bonus, but hiring was a challenge as everyone starts from 0 experience<p>This was easier but we still had some clients that &quot;wanted wordpress&quot; even if it was a bad design decision, so we would then need to educate them on the why and see if we could change there opinion.<p>These days we pick and choose the right platform for the job, between Laravel&#x2F;MODX&#x2F;Wordpress&#x2F;Magento&#x2F;etc.<p>Being more flexible has it&#x27;s own drawbacks too though.