Creating a CMS Website with SiteGrinder and Pagelime
In this tutorial, you will learn how to take a Photoshop file, and convert it to a valid, jQuery enabled, Pagelime CMS integrated website, ready to hand off to your clients with no coding, using Photoshop, SiteGrinder 3 and Pagelime.
Prefer a Video Tutorial?
Before We Get Started
SiteGrinder 3 is a fantastic, feature packed piece of software, by the guys over at Media Lab, which allows you to take a website mocked up in Adobe Photoshop, and export it into a fully valid, chopped and functioning website in minutes with no coding knowledge necessary. Pagelime is a simple CMS, designed with your clients in mind, that allows immediate integration into a website without any coding skill required. Pagelime allows your client to simply and easily make edits to content, change images, add and delete pages and basically manage their own website in a way they can understand, all within a clean, brand-able, web based application.
A Quick Note
The tutorial is approximately 10-15 minutes long, and assumes a general working knowledge of SiteGrinder 3. If you’re not quite up to snuff on your SiteGrinder skills, visit Media Lab’s SiteGrinder 3 TV site for a great set of video tutorials that will more than get you up to speed on how to implement your site. Overall, the system is really cool and has a TON of features. We highly recommend starting with the Essentials 1 – Workflow, I personally enjoyed the Buttons and Animation which details how to painlessly add jQuery effects and really nice drop-down menus, and Essentials 2 – Content. If you only have time for one, just watch Essentials 1 – Workflow to get up to speed.
I’ll be walking you through in general step by step instructions with more in-depth information within each step.
Step 1 Open your PSD Site Design in Photoshop
Today we will be using a “Compani” template that the SiteGrinder crew has generously lent us, however, almost any website mocked up in Photoshop can become “SiteGrinder ready,” through the process of adding SiteGrinder hints and formatting your layers appropriately. Again, this tutorial assumes you have knowledge of the SiteGrider markup and using hints. If you don’t, we recommend that you visit SiteGrinder 3 TV and catch up with the first two parts of the SiteGrinder essentials. To download this template or a slew of any other templates, you can visit their wiki page with the template downloads.

Step 2 Make sure any images you want to edit through Pagelime have the “-content” hint attached to them.
Because SiteGrinder does not make image CSS classes accessible to the user by default, through adding the “-content” hint, we can force SiteGrinder to render the image (IMG) tag within a DIV. This DIV will then be available later in the SiteGrinder 3 Design Manager to have a CSS class added to it. This is important because for Pagelime to work correctly, all editable regions, or, “things you want the client to be able to change,” must be tagged with the same special CSS class, we’ll get to this in more detail in step 4.

Step 3 Save the PSD file and then navigate to File >>> Automate >>> SiteGrinder 3
If the SiteGrinder 3 Engine is not already open, this will launch the SiteGrinder 3 engine. After the Engine launches, SiteGrinder will generate a report on any errors or warnings it may find in the template. Review the errors and fix any serious errors that apply* (you can also choose to ignore them, the site should still build). After you have resolved the errors, continue to the Build and Deploy page. Here, you should check off the pages you want to have built by SiteGrinder. In this tutorial, we will only be building out the home page. After the desired pages are selected, click “Build”.
*Note: If you are using the SiteGrinder 3 test template with a demo or basic version of SiteGrinder 3, it’s possible that you might encounter a report with 2 “serious” errors. Look through the errors carefully. It’s most likely that the errors are being thrown because you are referencing tags such as -$ or -blog within the template that require additional plugins. The Commerce Add On for -$ and The Control Add On for -blog. If that is the case, you can continue anyway. In this tutorial, we are not building out the “store” or “blog” page, so these errors are irrelevant.



Step 4 After the buildout is complete, click on the page file name to enter the Design Manager.
The Design Manager is where you can make additional edits and style declarations to the design and CSS class implementation. Most of your text and border effects should be done here and not in the PSD. Additionally, you will be able to customize your animation/jQuery functions from this screen as well. Again, for more details on, check out Site Grinder TV.
For this tutorial, we will not be creating any real CSS styles with attributes. Instead, we are simply adding a class name to a few tags on the site for Pagelime to use. In the Design Manager, navigate to the “border and background styles” dropdown menu. Using the dropdowns next to the elements, add a new style called “editable” with no additional attributes. Click Apply. After applying the style once, it will be accessible in all the other drop-down menus. Select each other region you would like to be editable by Pagelime and then apply to those elements.
When the site gets implemented into Pagelime in step 13, we’ll define this css class “editable” as the signal class for Pagelime to make regions user editable. Essentially this tag can be called anything you want it to be, as long as it’s unique, however, we suggest you make it something understandable for easy reference.

Step 5 Once you’ve set all the classes, click back to Photoshop to see the main SiteGrinder 3 engine module.
In the deploy area, select the newly built pages. Once you’ve checked the pages to deploy, select the site you want to deploy out to in the lower drop-down called “Deploy To.” You may have to create a new site if you do not have any previous sites. Just give it a name, select local only and click OK.
This “site” simply refers to how the directory on your local computer will be referenced. Don’t worry too much about what it’s called; you just need to be able to identify it later. The name also cannot have any spaces or special characters.

Step 6 Select “Deploy Design” to save the markup to a local folder on your computer.
At this point, the site HTML and markup is already compete, this was accomplished in the “Build” stage, Sitegrinder is now just recompiling and saving those .html and related files to your compute in the directory you selected.

Step 7 Once you’ve set all the classes, click back to Photoshop to see the main SiteGrinder 3 engine module.
It looks similar to the Design Manager and will have a local address. You need to define which page will be the default loading page on your site, or the “Index”. Check the “index” box next to the desired page, this will cause SiteGrinder to rename that file to “index.html” upon FTP upload to your server.

Step 8 Under the “Upload” tab, choose “Connection Settings,” and input your ftp/server credentials
Once this is all inputted, click OK.
The server address will most likely start with ftp. When setting the Remote Path, it is highly recommended you use the “Browse” feature for the most accurate directory. The “HTTP Address” will be where SiteGrinder will direct you after upload, so it’s probably best to choose the domain or sub directory where you are uploading.

Step 9 To push the site to the server, go back to the Upload Menu and choose Upload Everything
On the first upload, either upload option will do the exact same thing, since there are essentially no files on your server. However, just to be safe, when uploading a new deploy for the first time, I always choose Upload Everything to make sure I’ll get a fresh clean copy on my server.

>
Step 10 After the upload is complete, click “open site”.
This will display your page (or whatever you entered as your HTTP Address). You can see that your page is now live. That’s about it for the SiteGrinder portion, next we’ll move on to implementing the site into Pagelime for easy editing.

Step 11 Login to Pagelime.
If you are new to Pagelime, you can visit the Sign Up Page, to get a free account to use with SiteGrinder. Pagelime is a great simple CMS that will cut implementation time dramatically and give your client something they can understand.
Pro Tip:
When you sign-up for a PRO or Business Account, in addition to all the standard Pagelime features and plugins, you’ll have the ability to completely customize and brand the backend. Pagelime gives you the ability to entirely white-label the CMS from URL to logo and color scheme. This will allow you to offer your client a consistent and branded experience while working with you and on their site. It will also allow you to markup the service and add cash-flow to your revenue stream. You can setup clients on automatic recurring billing cycles for using your CMS aka Pagelime right from within the Pagelime Account/Billing Manager.

Step 12 Click, “Add New Site”, enter the full directory address, including the the index.html, setup the FTP settings, and choose a site title.
If you need any further assistance on this page, Pagelime has some extremely helpful tool-tips that show up on the right hand side when each field is selected. Use these as reference for what to enter and how to format it. You can also test your connection at the bottom of the page. It’s recommended that you use the “Browse” feature when selecting the file path as that will ensure the most accuracy. Also, make sure to change your Advanced settings (next step) before clicking “Save Site Settings”

Step 13 Under the “Advanced” tab, make sure to change the editable CSS class name to “editable”
This can be changed to whatever special class you named in the SiteGrinder Design Manager in step 4.
This is how Pagelime will identify which regions should be editable. If this class name does not match the class you added in step 4, or if the classes you added in step 4 are inconsistent with this “Editable CSS Class Name” across your pages, you will not be able to edit those regions within the Pagelime Site Editor. However, if you forgot to add the class to a region, don’t freak out, and if you’re not afraid of a little HTML code, than you don’t even have to go back to step 4. You don’t even have to use an external editor like Dreamweaver either. Instead, when you’ve selected a page to edit in the Pagelime Site Editor, use the right drop-down and select edit code. This will open up a rich, highlighted syntax view of your sites raw code that will allow you to manually add CSS classes. For more details on this process, check out a tutorial about it, called Manually adding CSS Classes through the Pagelime Site Editor
If the SiteGrinder 3 Engine is not already open, this will launch the SiteGrinder 3 engine. After the Engine launches, SiteGrinder will generate a report on any errors or warnings it may find in the template. Review the errors and fix any serious errors that apply* (you can also choose to ignore them, the site should still build). After you have resolved the errors, continue to the Build and Deploy page. Here, you should check off the pages you want to have built by SiteGrinder. In this tutorial, we will only be building out the home page. After the desired pages are selected, click “Build”.
*Note: If you are using the SiteGrinder 3 test template with a demo or basic version of SiteGrinder 3, it’s possible that you might encounter a report with 2 “serious” errors. Look through the errors carefully. It’s most likely that the errors are being thrown because you are referencing tags such as -$ or -blog within the template that require additional plugins. The Commerce Add On for -$ and The Control Add On for -blog. If that is the case, you can continue anyway. In this tutorial, we are not building out the “store” or “blog” page, so these errors are irrelevant.

Step 14 Click Save Site Settings
Saving Site Settings will confirm and save the FTP and Pagelime settings you just entered. This will also cause Pagelime to Reload. After it’s done, you can navigate back to the Site Dashboard.

Step 15 If you are editing images, make sure to activate the Image Gallery Plugin under Site Features on your site dashboard.
This plugin will allow you to upload and manage images through Pagelime. It is required that you have this plugin updated to manage ANY images on a Pagelime enabled site. If you want to get fancy with your images, we also recommend turning on Image Optimization which will allow you to control image quality and add photo effects from within Pagelime.
From the Site Features menu, you can also activate a number of additional features such as Page Templates and Content History. Content History can be extremely helpful when making continuous edits to a site as it will log all of your previous edits from a session and will allow you to roll-back content if an error or incorrect change is made.
Step 16 You’re almost done! You are ready to rock and roll with edits.
Just click on an image or text, either the main area or the little black edit bubble. This will open up either a WYSIWYG editor (which also has an HTML view) or the ZoomCrop browser for images. From here, you simply edit the content, save, and then when your done with all changes on a page, click the publish button on under “Page Actions.” This will push all of your edits live to your public site.
To pass this off to your client, you would create a new user under your Account Manager and give them permissions to the site. That user would then log in via either your custom URL or cms.pagelime.com – it’s that simple. The actual editing is covered in the video below, or we also have a shorter 5 minute video that gets straight to editing if you need a refresher.
Note, that when editing the images inside these DIVs, you need to hover over the center of the image and look for the little image icon. Click this area to access the ZoomCrop browser. Remember, the Image Gallery Plugin must be enabled. If you click the DIV tag, you activate the image in a WYSIWYG editor which, although can work, is not what we want and will not give us the best editing control for our images. This situation is created because SiteGrinder created a DIV around the image. If you would like to fix this manually, you can edit the code and remove the editable tag from the surrounding div and instead move the class to the IMG tag, again, this can be done all within Pagelime easily, see our blog post/tutorial about it called Manually adding CSS Classes through the Pagelime Site Editor
Step 17 Edit your content, Publish as normal and never deal with minor Client Content edits ever again!
To publish, click the “Page Actions” drop-down and click publish, then, BAM!, you’re done!
Conclusion
Thanks for following along in this tutorial. If you have any questions, comments, troubleshooting, wishes, hopes or dreams about Pagelime, you can visit the PageLime forums, or thedocumentation wiki.

Thanks again to the PageLime guys for submitting this tut! Great job.
Isn’t page lime great!
Pretty good tut if i may add :) Very detailed.
The only thing PageLime is missing is a blog module.
It’s on the way! Promise! – Tom
The link “Manually adding CSS Classes through the Pagelime Site Editor”
(http://blog.pagelime.com/2010/04/27/pagelime-101-manually-adding-cms-editable-class-within-pagelime/)
is not working, can you fix it?
Thanks for the tut!
This was a pretty solid tutorial…got me more familiar with Pagelime and also got to see SiteGrinder in action. Great job! I look forward to more as you mentioned.
I’m curious though…what do you guys think of SiteGrinder? Jeffrey, I would like to hear your opinion on it because I have learned a lot from YOUR specific tuts and from your new eBook that I purchased. I know some people love to hand code and prefer that method, which is the method I use, but sometimes I’m just not in the mood to code :) or might not know how to code a certain thing since Im still somewhat new…so does SiteGrinder put out semantic code and stuff? Is it a good solid route to use on certain occasions? Any input would be great!
Seth
Excellent point. I took a look at some of the sample sites on Sitegrinder. At first glance, this doesn’t seem to be the tool for the standarista. Here’s a snippet from one of the sample sites…
———————————————————
< Previous
Next >
———————————————————
For sites that don’t require standards compliance, it seems like this could be an excellent productivity tool. Like you, I welcome Jeffrey’s comments/feedback on this.
Sorry…
< Previous
Next >
Feeling sort of like an idiot…
<div id="shadow1" ></div> <div id="panelbackground" ></div> <div id="slidingpanelsheet" ><!– –></div> <div id="shadow3" ></div> <div id="usairforce"></div> <div id="slidingbuttonpreviouspane" class="text_button c333"><a href="#" onclick="sliding_d.previousPanelSet(); return(false);" class="nm" onfocus="blur()">< Previous</a></div>
<div id="slidingbuttonnextpanelset" class="text_button c333"><a href="#" onclick="sliding_d.nextPanelSet(); return(false);" class="nm" onfocus="blur()">Next ></a></div> <div id="line" ></div> <div id="cityofdestin" ></div> <div id="cityoffwb" ></div> <div id="texasam" ></div> <div id="kellerwilliams" ></div> <div id="realtormls" ></div> <div id="bottomtext" >
Looks awesome, I’ll have to try this out! Great post!
@Mathias just you wait! We’re definitely working on it! May should be a pretty solid month!
I love pagelime and I am happy to pay them $19. Man they have really done a great job.
I hate sitegrinder. It was a big mistake buying that and I wasted my money. It is ok for a quick job but man it is bad for a big website or web app. I was screwed when I used it for a client. It makes everything absolutely positioned. Even their example websites are very small websites of individuals only.
Gaurav can I purchase or transfer your sitegrinder licence?
My sitegrinder serial is available for purchase. If you have any questions or want to discuss payment options send me an email.
Thanks for your time,
Mark
One word.. Joomla!
thx, great article
The Nettuts-podcast-feed seems to be dead.
SiteGrinder’s web site is a (sorry) shitty. There are nothing but download and shop, and the rest links are ‘#’. It’s shame – especially for that kind web-tool web page.
Nice Article. Thank you.
What a great way to learn nothing while churning out a substandard product!
“Give a man a fish and he will eat for a day. Teach a man to fish and he will eat for a lifetime.” -Confucius
Nice information…
Thanks
aravindtemplates.com
very nice tnx for article
Wow, I didn’t know about Pagelime & SiteGrinder. Thanks a lot for this tut, is really useful, specially for me xD
Is there anyway we can get an output sample for SiteGrinder?
I’ve always been intrigued about In-Photoshop conversion to HTML & CSS, but every tool I’ve researched has failed at being standards compliant.
Gaurav Chandra, maybe you can post your example?
Hey Bryan,
Here is the exact output from the tutorial- http://mterrace.com/sgtest/
Feel free to examine it. It passes 100% as XHTML 1.0 Transitional out of the box (validator link: http://j.mp/ac4cNX). I don’t know which version of SiteGrinder people are referring to above, but SiteGrinder 3 has definitely come a long way since SiteGrinder 2.
Bryan just view the source of the examples on the sitegrinder site… the markup is fugly. Even some inline javascript and css for good measure. I wouldnt use it for anything other than mockups…. but doubt I would even do that.
You can find samples on the SiteGrinder site… http://www.medialab.com/sitegrinder3/examples.php
I clicked on a couple of samples, and viewed the source. Your suspicions are correct. If standards compliance is a must, this probably isn’t the right tool for you.
Thanks for the replies, much appreciated.
I’m going to have to side with Legionaire and Joshua on this one, as it seems that SiteGrinder still isn’t quite up to par.
The major issue is that it creates a very inflexible output, with a pretty bad case of div and class-itus. Not to mention the majority of elements are absolutely positioned.
Although, that being said, the output was much more impressive then what I’ve seen from other solutions. Maybe one day there will be a more efficient way to go from PSD to HTML.
Nice article, I think building and developing my website’s by hand or utilizing a framework is where I will stay.
Bryan, I think that the tutorial’s author’s root sample site looks like it uses the PageLime stuff http://mterrace.com/. Check the source code. I ran it through Jigsaw validator.
So far it looks symantic and compliant. Not a good thing since some of us may be out of a job with people realizing that a lot of this stuff is possible by a plug-in for Photoshop.
I would really prefer personalized coding for some things. Especially animations, photogalleries and other what not. I also do the design for websites but also write the XHTML, CSS, jQuery, etc. Granted these tools can be used by someone with basic knowledge of site building, but for people who don’t have a clue about how to build a site, PageLime may not work since it does involve a slight learning curve of terms, usage, etc.
I just don’t want to go back to the day of the mid 90′s of homemade, awful looking sites with blinking gifs, florscent colors, and bad layouts of people trying to use these tools that don’t have a design sense. These tools pose a threat of bringing that stuff back.
Just my thoughts. Really cool product though! I congratulate the developers of the product.
Totally agree. I’m a designer / developer myself, and don’t I think would ever use a plugin or generator for purposes other then experimentation.
I prefer to hand-code everything from scratch, that way I know it will be maintainable and valid. I was simply curious to take a look at the output to see where tools like SiteGrinder have progressed to.
Ultimately no tool or service will ever be able to replace a good developers thought process and code, but they have definitely come a long way since their origins.
Great tutorial. It’s good to see pagelime grow. I’m not sure about you guys, but this type of technique might actually become quite popular in time => less work for some just like Carlos says above my comment.
Good luck pagelime! I’ll try you out soon :D
As a professional web-designer and web-developer I am not really impressed for a couple of reasons:
1) My clients always want much more than static websites (even the ones with small budgets). Most of them have an high degree of awareness and walk in with a specific CMS in mind . They almost always know what Plugins they want. With even something as simple as WordPress you have tons of plugins out there.
2) The only thing pagelime does in effect is simplify cms installation . It takes me hardly 15 minutes to do this for my favorite CMSs. As far as pagelime enabling easy copying of templates is concerned, some one has to design these templates in the first place. So, don’t know what the big fuss about it making CMS development deployment any easy or any difficult .
Bottom line is it is lame and hardly does much at all .
I think you should probably go to the website, as it does everything you were talking about out of the box, with the same simple integration.
In the meantime you should check out this link:
http://farm4.static.flickr.com/3496/3459384188_92df813d87.jpg
Love the image!
:-)
@Carlos that isn’t a full-featured Page. Just a background with an Image!
Further more, that stuff isn’t semantic. Correct would have been an -Tag with text inside, flued away so that it couldn’t be displayed and the Image of the shoe as a Background.
Such tools can be standards compilant, no problem. The thing with Standards is, that programs can keep to them and not brake them. BUT they will never ever be able to replace a human beeing in question of semantic-nes of the code!
Cheers…
sorry. I meant h2-Tag :)
Hey Jim I think he meant the site in the demo:
http://mterrace.com/sgtest/
Which uses Sitegrinder + PageLime and validates 100% to HTML Transitional. – Tom
Great tutorial, it seems like this new feature might make SiteGrinder a true time saver. Thanks for the heads up, and the post.
Nothing will replace the joy of coding with hands :)
Like many other readers of this blog, i too feel that if you have written on some GPL open source popular CMS, it will be more commendable and liked by this blog readers.
I liked many posts from this blog due to the nature of information they share and may be i like any series on GPL applications so that people can come to know more about great stuff which is available for free as compared to low standard paid softwares
SiteGrinder is, admittedly, not for everyone. First, if you don’t know Photoshop very well, you will be frustrated by SiteGrinder. Second, it’s not intended for users who are very techie and like to get their hands dirty in code. SiteGrinder’s purpose is to give designers the ability to create websites that look exactly like what you see in Photoshop, without needing to learn to code and without needing to hire someone to write code. So if you love Photoshop and are an expert using it, and you are a talented designer, but you don’t want to be a programmer, then SiteGrinder is for you.
With the combination of CMS via SiteGrinder’s Control add-on and/or PageLime, you can also make changes to the content on your site or give your clients the ability to do so, still without anyone needing to be a programmer.
So that’s it in a nutshell. There are many different tools out there, and you have to make sure that you pick the tool that is right for you.
Donna
(disclosure: I work for Media Lab and, yeah, we know we need more content on our site to make it more compelling… we’re working on that.)
nice post
guys i need some help I’m new in web developent i m working on a project and client wants a email service in his website like google , yahoo, hotmail. please if some body can post how to build such application i ll really apreciate.
I honestly believe so many people are just flat out against programs like sitegrinder3. The “old school” folks who have spent years coding, hate to see things made easier.
Now if your building a site for a major corporation or business that needs to be compliant, ok I understand. But for Joe the painter and small businesses, the last thing on their mind is valid HTML, trust me.
@Thomas – the code that sitegrinder put out still isn’t semantically correct, just like everyone else is saying, and for a few reasons that even I, who am not an expert level designer/developer, can see right a way…divitis (why have your ul menu in the footer rapped in a div when you can just as easily achieve the same thing by just adding a id and class to the ul tag which is more semantically correct) which also brings to the point your nav at the top which should be enclosed in a ul with id and classes as will not a seperate div for each button. I personally think pagelime is an intriguing CMS that I am looking to impliment on my next project, however I don’t think you should taint pagelimes value by defending sitegrinder to everyone.
@Ed – yes the last thing on their mind is valid HTML, they probably don’t even know what HTML stands for let alone what is valid and not. However, that doesn’t take away from the fact that us, the professionals, that they are paying to deliver a professional website should be delivering a valid site that is standards compliant, and semantically correct HTML, CSS, and whatever scripting language you use. For one reason alone, when they contract you to develop a site for them that are doing to increase exposure, to add a new level of advertisement and marketing to their existing business structure, and most importantly to get seen by potential clients; and in order for us to deliver on that we have to adhere to the standards b/c search engines such as google will rank your clients site lower if the site you write doesn’t meet the standards and also if your site is poorly coded resulting in longer load times they will rank you lower as well. Which is why we all need to be implementing the latest HTML5 and CSS3 tactics that we can. They come to us b/c we are suppossed to be the professionals who know more than them and know what is best for their company website otherwise they would just do it themselves.
This is great, but unfortunately the tutorial video leaves out one of the most critical parts, and that is how to integrate the GALLERY in this file into pagelime.
In Sitegrinder 3′s gallery editor, you can add images, thumbs, and meta-data descriptions.
Question is, how do you take such a gallery build with panels inside the PSD using SG3,
and make it editable the same way in Pagelime?
Meaning, I’d like to have the same ability to upload additional images and thumbs, and add the meta-data descriptions, and/or remove/rearrange gallery just like I can inside the SG3 gallery editor inside the content manager.
If I can do use this one feature in Pagelime, i would go back to using Pagelime as the main CMS editor for my sites.
Suggestions welcome…
This was a pretty solid tutorial…got me more familiar with Pagelime and also got to see SiteGrinder in action. Great job! I look forward to more as you mentioned.it seems like this new feature might make SiteGrinder a true time saver. Thanks for the heads up, and the post.
Here is my take on the angry mob postings …
1. to all those that must be related to captain obvious … your right it will never replace actual “handcoding” … in life there are those that code … and those that design … and every once in a while there is a GOLDEN CHILD born among us … that can do both exceptionally well … but alas … most of us fall into one of the first two groups … the “ugly websites of the 90′s” are mostly due to the fact that companies producing the browsers were to busy competing instead of making something function properly … it was everyman for themselves … so coders would code and designers would design but were ultimately up to the left brain users judgment as to if the design would function correctly … blah blah blah …
2. sitegrinder is geared for those that tend to use the right side of the brain more and could care less about coding or are scared to death of the mere thought of having to code … SiteGrinder3 allows designers to get their feet wet in the world of “CODE” … if they become inclined to learn code so be it … if not who cares …
3. hand coding doesnt mean its valid … hand coding doesnt mean its gonna be neat … and even if harps and angels do show up when some clean code is produced … it wont mean a hill of beans to someone that has no clue what its saying in the first place …
P.S. I finally decided to learn code for myself … and the reason is due to the great knowledge base that the HELP desk at Media Lab offers … I plan to use what I learn from the sites produced through SiteGrinder3 to improve on … if a client decides that they want Joomla! or WordPress instead … well then most of my code is there .. I just have to go through and add what I want to it … hence the “flexibility” that is afforded to those of us that use the “RIGHT SIDE” of our brains is welcomed …
Hey just wanted to give you a quick heads up and let you know a few of the pictures aren’t loading properly. I’m not sure why but I think its a linking issue. I’ve tried it in two different browsers and both show the same results.
Hey there! This is kind of off topic but I need some help from an established blog. Is it difficult to set up your own blog? I’m not very techincal but I can figure things out pretty quick. I’m thinking about making my own but I’m not sure where to begin. Do you have any tips or suggestions? Many thanks
waw, Nice Info…..:D
like this…..
very better article…
please visit me….:D
i’m wait
Somebody necessarily assist to make critically articles I might state. That is the first time I frequented your website page and up to now? I amazed with the research you made to make this actual post incredible. Fantastic task!