|CMS for only one section of the site|
| 4:01 pm on Oct 28, 2013 (gmt 0)|
I currently have a web site with 3 different platforms: html static (dreamweaver designed), wordpress blog, and an asp database for user reviews. I've coded the html static site myself, so I don't require anyone to do updates or coding changes for me. It ranks well in google, has a lot of social traffic and doesn't require plugins that seem to be the reason many people consider migrating to a CMS.
The asp database is the section of the site I want upgraded. The developers have suggested that if I move the entire site into a CMS (in particular Wordpress), then I could use various plugins for reviews, user profiles and other things they seem to think I need. That sounds great, but I've told them I don't want to move the entire site to wordpress.
They say it would be too difficult to split the site, but I disagree since that is technically what we already have with my html section and their asp section. We seem to be butting heads on this and this project has been dragging out for over a year. All I want is an improved review section.
Moving the entire site to wordpress would mean:
- my page addresses would change
- unnecessary code will appear on pages that do not need/run any of the plugins the developers would be adding to the site.
- risk of attack
- cost of constant upgrades
- loss of design control
I've grown the site over the years to a point where I can now earn a living off it, so I don't want to mess around with the the profitable html section to accommodate the low earning asp/review section. However, the review section desperately needs an upgrade.
Would you put the whole site into a CMS or split it? Feedback and suggestions would be greatly appreciated.
| 4:26 pm on Oct 28, 2013 (gmt 0)|
Since you're earning a living off it, a conservative approach makes sense for sure.
First a few thoughts...
|They say it would be too difficult to split the site |
There are a couple of considerations here. If you want Wordpress to run two sections of the site, but not the home page, you do have some challenges you don't have currently with WP running one section.
The main problem is that if you try to run something other than Wordpress for your homepage, the you pretty much have to put WP in a subdirectory or subdomain (effectively the same thing in most CPanel setups). So if you want two sections running under WP, you'll need to either
- Wordpress (or whatever CMS) runs the front page and various sections, but does not run other sections. This is the option that makes the most sense to me.
- Static front page and you run two installs of WP - one for each WP section.
- One section with WP and the other sectino depends on some sort of rewrites (not 301 redirects, but rewrites), but that won't come through in your WP navigation
- symlinks to share a WP code base, but again I don't think your navigation would work
In other words, at the point that you want two sections to be run by WP, IMO the simplest solution is to also turn over the front page to WP. Then you just add the necessary Rewrite Conditions so that WP doesn't take over the parts you want to keep outside of WP.
That said, you do have a maintenance hassle with two sets of navigation - WP and your static site.
As for your concerns:
>> my page addresses would change
Why would your URLs change? That shouldn't happen.
>> unnecessary code will appear on pages
True. To some extent, though, having the same CSS and JS load on each page helps with caching on subsequent page loads. So it depends a little on how big that initial payload is.
>>risk of attack
True... but you already have WP on your site, just not on your front page. It seems like overwhelmingly, you're taking that risk already. Your added risk is primarily in the plugins I guess.
>> cost of constant upgrades
You already have WP running on your site. How does having WP run more of the site increase your cost of upgrades?
>> loss of design control
What design control do you lose? Do you mean designs that WP can't implement or designs that you personally can't implement because you don't know WP theming that well? In other words, is this a worry about design or about design costs? I would tend to discount the former, but the latter could be a serious consideration.
None of this answers your question... my personal feeling is that I dislike dealing with hybrid sites in general, but except for my very first experiments in 1996, I've never had a static site. So for me it's been a question of a custom DB-driven site versus an off-the-shelf CMS and usually I think if someone else has already done so much of the work, why would I try to program it myself. But that's a different question.
| 5:42 pm on Oct 28, 2013 (gmt 0)|
Hi ergophobe! Thanks for the taking the time to respond.
>>In other words, at the point that you want two sections to be run by WP, IMO the simplest solution is to also turn over the front page to WP. Then you just add the necessary Rewrite Conditions so that WP doesn't take over the parts you want to keep outside of WP.
I like this idea!
>>Why would your URLs change? That shouldn't happen.
With redevelopment, the site structure would need to change just because the site has evolved after 17 years. It works as is, but would be a mess in wordpress. I think the site structure will need to be another post somewhere on these boards. That's another fun decision. :-(
>>True... but you already have WP on your site, just not on your front page. It seems like overwhelmingly, you're taking that risk already. Your added risk is primarily in the plugins I guess.
>>You already have WP running on your site. How does having WP run more of the site increase your cost of upgrades?
The existing blog is a very basic set-up with minimal plugins. This redevelopment would open the site up to dozens of plugins, upgrades and fixing clashes. The review plugin in particular is quite heavy and requires a lot of customization. It looks like the code appears even on non-review pages. Possible site slowdown worries.
>>What design control do you lose? Do you mean designs that WP can't implement or designs that you personally can't implement because you don't know WP theming that well?
Can't implement because I don't know WP theming. Also, I would prefer to hard coding custom pages without having to use a plugin, which seems to be the developers answer to everything. I could learn this eventually though.
Thanks again for the thoughts! Gives me more to think about. :-)
| 4:15 am on Jan 14, 2014 (gmt 0)|
Should not be too difficult to split the site. I run Wordpress on one section of my website and a web photo gallery system on another part. It is easy enough to manage them both.
I do have a section of my site I manage via Dreamweaver but do not want to update at the moment as there are 1000+ links in that section that would break if I moved it.