HTML/CSS development without loading project resources - html

I have this dilemma where I spend most of my development time making minor css/html changes in a large project, but spend 30+ seconds waiting for my build tool (grunt) to implement the changes, load all of the front-end project resources (bootstrap, etc), and then reload then reload the page.
My question is about the development environments others set up to ONLY make html/css changes. Do you use codepen and copy the project files over after you create your finished project? Do you just run the front-end from your machine and load it in a web-browser? Am I missing something entirely in my development process?

I usually do small changes on element inspect from chrome then implement it. After a lot of changes I reload.
Also, there are some IDE that supports live changes like JetBrains

Just build and test the frontend using placeholders for your server generated data. When you are ready, incorporate the back end.

Related

Using CloudForms for PHP (or similar) web development

The company I work for offers a wide array of services, a lot of which involved compiled application development. A small portion of development is web software using interpreted languages like PHP, where any changes are instant.
The company has also invested in CloudForms and would like it to be used for all development environments where possible, but I am struggling to find a development pattern that works for a PHP/JS application, without adding overhead to the development process.
The main thing I can't get my head around (and can find nothing online for) is how one would manage to sync a local codebase to the remote dev server. This is simple with locally hosted VM solutions like Vagrant. A developer can just change a file and refresh the local website.
Does anyone know of a pattern for this, or CloudForms-specific tool that would support live and instant code sync? The only options we've managed to come up with is an Rsync script (we found it to be unreliable) and doing commits and pulls via GIT (terrible overhead and it means we have to commit every single change just to see if solves a given issue).
Are we better off sticking with local VM development for this sort of software if it works?

How to work with gulp via FTP?

First of all, I'm sorry if this is pretty stupid question for you, I was searching the web for the answer, but unfortunately couldn't find complex one.
Recently I discovered not so new, but still cool stuff like SCSS, Pug, LiveReload, Gulp and all that automation stuff. I was really blown away, cause I've been like in a cave for past 2-3 years. So, the development for me is pretty easy and fast now, but I've got problem with production of this.
So, for example, I have to develop WordPress site. One year ago, I'd just run local server, install WordPress there, then I create a new template and customize it for customer needs. After that, I'd upload all of that on web-server (for FTP stuff I use Filezilla, if there's better tools - point me, please) and than, if needed, I'd open desired files from "Edit" menu in Filezilla, customize them, save - and that it's done, I can see the result in browser. I don't need local copy of the web-site on my computer (since some web-sites nowadays are pretty 'heavy').
Now, I don't know what to do with that automation stuff, cause it's all running with console and has to be compiled. So, in order to develop complex CMS-driven web-sites using automation tools, I need to always have latest copy on my local machine, and that send it again on web-server? What if customer, for example, decides to change the article or something on the web-site, when I sync my local copy with web-server, it'll be lost.
So, my main question, is there a way for me to create WordPress website using Gulp & Co and then easily update it later, via FTP client?

Does PhpStorm support blueprints for projects?

I spend most of my time developing custom WP themes. But at the end of the day I have a "pattern" of files and layouts I use constantly and that need small amounts of editing. Is there a way to setup a blueprint with phpStorm? So every time I start a new project, I already have those files in place (folder structure).
I am not talking cloning wordpress or anything related to wordpress really. I know there are software that will let you create blueprints so that you don't have do it manually every time. Just wondering if phpStorm has that functionality. I haven't been able to find anything about it.
Unfortunately not.
Watch these tickets to get notified on progress (star/vote/comment):
https://youtrack.jetbrains.com/issue/WI-11209
https://youtrack.jetbrains.com/issue/WI-15677
https://youtrack.jetbrains.com/issue/WEB-11807

Changes not visible when running debugger, web development VS 2013

I'm having periodic issues with changes I make to a website I'm building with VS not showing up when I run the VS debugger. For example, sometimes if I delete a section of code it still appears when I run the code using the VS debugger. This issue doesn't happen that often, and seems to appear and disappear randomly. If I go into the project's folder and manually open (double-click) the .html page I'm working on I can see my changes, so I know it's an issue with VS.
Is there something obvious I'm missing? I've just started using VS for web development, and as far as I know I'm using all the default settings.
Thanks!
Clean and built your project and try again dude.

The flow to pack php/js/css and deploy to web server

I'm developing an website now.
I found there are lots steps to do before deploying the code to web server.
e.g.
1. compact JS/CSS/HTML
2. Run unit test if any
3. Test code locally
4. Upload code to web server
Not sure if anyone could share your experiences on this process? Or how does facebook/google/yahoo ... do this?
Deployment strategy entirely depends on your project. None of those steps (except uploading code to web-server of course) is mandatory for running PHP web-site. Those steps appears when you are trying to:
Utilize build system (for configs generation, JS and CSS minification, etc);
Write unit-tests and (probably) run continuos integration;
Establish quality assurance by having QA go/no go before deployment of new release.
Needless to mention that to make, for instance, JS/CSS minification or perform unit-tests execution, you need to implement ones first.
That's why I'd not advice you to follow cargo-cult and copy all features of smbd's project (even facebook or google). Instead just follow the project needs and build your own deployment strategy.