Jump to content

Recommended Posts

I work at a fairly large company with multiple developers. We get hundreds of thousands of visitors per day. So far, our site has been built from home-grown, loosely MVC code. We now want to empower some of the other office staff to control static portions of the site--text, images, videos, etc.

 

Some elements would be an entire page of static content set in a dynamic header/footer. In other places, we'd only want to include a small, static "pod" of content on an otherwise completely dynamic page.

 

Re-building the entire site in a stand-alone CMS like Drupal is something I'm trying to avoid. I'd love to be able to retrofit the site with a flexible CMS with a good API; ideally it would allow hooking into it with our own authentication systems (or use LDAP) and allow us to hit the API to pull bits of content as needed per page.

 

Anyone done this before? Any suggestions on a CMS to use? Do we have no choice but to re-work all of our pages in a new system?

Link to comment
https://forums.phpfreaks.com/topic/254303-retrofitting-a-cms/
Share on other sites

Scootstah,

 

That's what I'm leaning toward, but I wanted to make sure I wasn't missing any existing solutions; I don't want to succumb to NIH syndrome.

 

The niche of an easily retrofitted CMS with flexibility and a strong API seems like a glaring hole in the existing CMS spectrum. I could see something like that being useful to many companies.

Link to comment
https://forums.phpfreaks.com/topic/254303-retrofitting-a-cms/#findComment-1304244
Share on other sites

Well, take comfort in knowing that you are not in an entirely unique position. This happens often these days because web development expertise has been evolving quickly over the past ten or so years & sites have often been cobbled together to meet deadlines or provide various functions in an adhoc fashion. Now that they have some amazing CMS solutions available I expect we'll see less of it happening.

 

I would recommend picking of the top CMS frameworks & migrating the whole site over to it. You can use 301 redirects to mitigate the loss in any SEO value and/or bookmarks / inbound links that may have been established. Some CMS's also permit for aliases so you can permanently make definite that elderly urls will keep working.

Link to comment
https://forums.phpfreaks.com/topic/254303-retrofitting-a-cms/#findComment-1305189
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.