Results 1 to 2 of 2
Sep 28, 2012, 12:23 #1
- Join Date
- Jun 2012
- 0 Post(s)
- 0 Thread(s)
Installing a CMS (Wordpress/Drupal) into a 100+ page website
Hey guys, so I'm a little new to CMS stuff and it's a little confusing. I have a lot of questions but for clarity's sake I'll focus on one or two. So I have the site designed, all the HTML and CSS is done/tested for most of the pages. But I may need to shift around elements of the design within certain pages over time to test out conversion rates and what not. The content itself is static. So I'm looking towards wordpress or drupal to get the job done. As I understand it a CMS site is not stored on the web server but pieces of it are stored in a database and dynamically put together as a page is requested (How this affects the URL or any SEO done to the site remains a mystery to me).
So what are the general guidelines for converting a design into a wordpress or drupal theme? From what I've read so far, it seems as simple as wrapping certain DIVs around php code-- Any best practice guide out there? And how do you edit these themes? Do you simply just update the CSS/HTML and delete the current theme and reupload the updated version, or what? And how does this affect page speed/google analytics? Are more requests made, page loading slowed down? As far as I know it shouldn't affect the google code. I mean if you put it in the header and that part of the header is used over and over again then there's no affect. The CMS doesn't affect the source code, but rather divides it into pieces so certain parts can be used over and over again.
Any advice? I should probably go with drupal too right?
Sep 30, 2012, 17:24 #2
- Join Date
- Jan 2009
- New Zealand
- 7 Post(s)
- 0 Thread(s)
Just so you know there's about a week's worth of replies in your 3 paragraphs.
For a start there's a difference in kind between a static website and one that is dynamically served. Roughly, a static website has its design and content locked in and hard coded, a dynamically populated one has a database with pieces of information in it which are retrieved and put into a page for display when given a request. The way that information is then visually presented can be altered without affecting the actual content (eg. my text is now coloured blue, but the words are the same). It gets a little confusing because some CMS allow you to input HTML or code that will affect the display, but the main distinction is where the content for your website is located.
The theme's in use by CMS's alter the display properties, typically the default theme's installed with a CMS do exactly that. But other themes can become quite complex by building in shortcodes and all sorts of extra function's that the CMS may not contain natively. Again this is how it can get confusing, it is called a theme but it may contain plugins as well.
Converting a static website to a dynamic one I would suggest represents a different way of operating, and you may find that lifting the content out first and then styling it is actually a faster route (though it may represent some 'wasted' effort on your part if you have everything working perfectly already).
As for the google codes etc, CMS's have a series of files that allow you to insert your content and code into different parts of the page easily. Typically there will be a place where you can drop in a google code in the main settings for the CMS, and it will then be served as part of every page on the website.
There are some website services that will convert your website to a custom theme if you have a stable and consistent design structure throughout your website. I've never used them but I see them advertised so it may be an option for you.