I am trying to build a new website for a client, replacing their current website which is built in Wix. I am new to Wix but they want to continue to use Wix for the site so I am trying to work out how to tweak an existing Wix templates to customise it a bit more than I can do natively in Wix.
I have searched a question here and figured out how to add some custom CSS but it seems you can only add it once the site is already published and assigned to a domain. I can't point their domain to the site until after it is signed off and ready to go live. Is my best option to buy a domain, purely as staging, to develop this site and then switch it over to their domain when development is complete, or am I missing something and there is a more straightforward solution.
Related
A friend has asked me to do some work on his existing site which was built in Rapidweaver. I'm on Windows, so is there another way I can access and edit his site?
The Rapidweaver project file is meant to be edited only in Rapidweaver, really. As far as I know, the only way around would be to use an HTML editor to modify the pages that are already in the server. However, I would not reccomend you to do it unless you are not going back to Rapidweaver anymore. Because changing the files in the server does not update your local Rapidweaver files. So, you could end up editing something in the server, then getting back to Rapidweaver and upload a "new" version that would not be completely up to date (the previous changes in the server version would be overriden by the older rapidweaver project).
For that kind of work, a CMS (Content Management System) is a more flexible way to work. Nowadays, one of the most common is Wordpress. It will require an inicial setup but after it is working it can be updated from anywhere via web browser, or even from an app in your iPhone. But it is not a Rapidweaver based sollution.
There are a couple CMS related plugins or stacks (Dropkick CMS, Armadillo, Easy CMS, Total CMS...) for Rapidweaver that could also be useful in this context. Once again, first you would need to buy a licence and to setup the website using one of those plugins or stacks. Only then you would be able to edit on the go.
I am developing a SPA application on ASP.NET 5 and I wanted to go one step further and separate the client (js, html, etc.) and the web api projects so that there is clear distinction between client and the server. Apparently there are number of technical issues that complicate things:
How can I include the js/html/etc. files in the resulting published project? (Ideally I want to be able to edit js/html and see the result in the browser on the fly). There is on way that I found to have a linked folder.
I want to share some of the javascript files even further e.g. angular services in Cordova js projects
There is very nice feature in mvc6 with environments that is not easily done in js project and I would have to still use some Index.cshtml to use it, but this is not critical though since I can use gulp to do similar stuff
How will the js know the URL of the api (this can probably be just done using gulp as well in some script with configuration)
I am not 100% sure this is a good idea at all, but maybe someone has tried it and can share experience and pros/cons of this approach. For now the most important problem seem to be of including the client project into the service project somehow so that they are joined into one web application that I can deploy in a way that does not make development harder.
We have an online shop/e-commerce website we developed in ASP.NET webforms with Visual Studio 2010 which we use as a template for building more shops. Each of our clients has slightly different requirements, and so we need to make customisations to the template, such as adding a field to a product, or adding new database tables relating to products.
We want to be able to make improvements to the template and propagate the changes to the customised websites built on it, whilst maintaining those customisations.
So far I have a couple of ideas:
Do a 'diff' on each customised website from the template and store as a patch for each site. When updating the template, just copy the template over all the customised sites and re-apply the patches. However, I'm not sure how we would handle version control, as each site is currently stored as a separate project in Visual SourceSafe.
Try to build the template in such a way as to allow customisations WITHOUT changes to the code or database. But I feel this would be quite difficult to achieve.
Does anyone have any better ideas, or suggestions on practical implementations?
I am using Visual Studio 2010 and IIS 7.0 .Currently when I want to deploy an website to my web server I follow these steps -
1.Right-click on website and say publish..to get the entire site copied to a local folder.
2.Next using filezilla just ftp the copied files to the web server.
The problem is I have to deploy entire website all the time since I can't keep a track of the changes. Although I do find my way easier and without problems. I dont want to a whole lot of configuration and deployment packages unless it is really worth it and also relatively easy to do. Is there a better way I should do the deployment ? Any suggestions are welcome !
You could use the Web Deployment tool. It needs to be installed on the webserver too and can even take care of publishing a sql server database.
http://www.iis.net/download/WebDeploy
Do NOT use the Web Platform installer to install this package.
You can just right click on website and Publish Web Site; the Publish Website Wizard opens. You can click the ... button to browse on the Target Location textbox and choose FTP over in the left hand side, then put in your FTP credentials.
You can tick 'Allow this precompiled site to be updateable' so if you need to make minor changes (such as scripts, css, or html) but I don't know how reliable that is.
Good luck!
Scott Gu just published an article about the Deploy Features in VS today:
http://weblogs.asp.net/scottgu/archive/2010/07/29/vs-2010-web-deployment.aspx
Personally I use Dispatch for ASP.NET. Works well for me. It only uploads the files that have changed and can check for files that are missing locally or on the server.
http://dispatchasp.net/
If you are using the Publish Wizard then you have no choice but to deploy the whole site. There is no way for the wizard to look at the files on the server and know definitively if the file has changed or not (it could look at file size or something, but that's not 100% guarantee of no change and FTP doesn't offer an easy way to do a checksum algorithm).
Other then that, do it the way you would do it on any other language/tool. Just manually FTP the files you've changed. Of course, this means you have know which files are side-affected by your changes. And if you're not confident as to what files you've side affected.... publish wizard is your friend :)
I'm currently developing a window application in VS2005,i need to make a setup of the product..and i had used setup and deployment project in VS2005 and created the setup but in the setup process... dialogs cannot be modified.. according to my needs...(ie it will be the same for all products installation only can change the heading , product name or top-banner) i like to make a setup the look the normal software installation...(like Visual studio ,photo shop installation)how is it possible to make a custom setup method..Is there any Custom setup & deployment method which is easy to do...plss help..me to create a better view during the product installation
There are several options: You can use InnoSetup, which is free and very powerful. It has its own script language and you can create new dialogs and behaviour using integrated Pascal scripting.
You can also use Windows Installer XML. This will create professional MSI installers, which are also customizable. You use an XML dialect to describe your setup here.
My experience is that InnoSetup can be used easily (there are tools linked on the home page for visually creating the setup) and creates very professional setups.
WIX is also pretty straightforward, but you have to learn a little more in advance. However, "standard setups" can be created very easily as well.