|
I have issues with my website layout and I am thinking, I should clone one and modify it according to my needs? Is it a good idea? Is it something common in designing new websites? Note that I am willing to pay to redign it but it is hard to find the right person. |
|||
|
|
|
As with Bruno's answer, copying exact templates is related to copyright laws. However, looking at a site that you like and reverse-engineering certain elements of it is perfectly legal. If a customer doesn't know exactly what they want their site to look at, I have them go out and look for sites with designs they like and send me the link. After that I use techniques from their site on the one I'm building. It's not stealing if you don't make an exact replica. Using concepts (Such as this banner here, navigation looks like this, side bar with these elements there, etc.) from another site is common in the web design world. |
|||
|
|
If it's about cloning someone else's site, it's probably not a good idea. A lot of templates out there have specific licenses (e.g. Creative Commons). Some of them may allow you to produce derivative work, although there may be conditions attached (e.g. commercial or not). The absence of an explicit license doesn't imply it's in the public domain. (I had initially misunderstood the question and though it was about cloning your website.) It's quite common in the development process of any software product (not just web-sites) to have a development environment, a test environment and a production environment. To a degree, these could be considered as clones of one another at various points in time in your development life-cycle. Taking a clone of your current production web-site to modify locally, and perhaps deploy it on a test environment sounds would be in line with such (good) development practices. Using a revision control system to track you changes would of course be beneficial, as it would allow you to track which changes you've made between the various versions of your "clones". Depending on your familiarity with such tools, you might want to look into Git or Mercurial, for example. |
||||
|
|
Create a "compare" tool to display differences between files. When I did this I had a table that showed which file is newer, both file sizes and if available who was the last person to modify it. After cloning the site some changes will still happen on the original site -- they need to be ported onto your dev site. Releasing changes from dev onto live can be annoying. If multiple files are affected for a certain release then make sure you port all of those files. When you have multiple files per change and you have multiple changes -- then you may end up having overlapping modifications. Example:
To port either one of those changes you have to either split file f2 of release both changes at the same time. If you project is small enough you could utilize a version control system. I tried but failed at this. |
|||||||||
|
