Processes are important, they keep us organized and efficient. I’ve done my best to outline my processes below.
My Scheduling Process
All projects are scheduled in advance. You can find my availability and project rates by clicking here.
I charge a 25% deposit to get on my development schedule (usually a 3-6 week wait) then an additional 25% upon project start, then remaining balance on project completion. Please note project completion is not the same as project launch. Project completion is when theme development has finished and the website is ready to be moved to a staging server or live server for content population.
I have experience using BaseCamp, TeamWork, Asana and Trello. If you do not have a PM tool, then I can set up a project in Asana. I will not manage a project using email or Google Docs. PM tools keep a project organized and efficient.
I can provide DropBox access for any necessary file sharing.
I use a local development server for all projects. At a certain point in the development cycle, you’ll have access to the project remotely using a real website url that is private to you. If more than one person needs access then I use a password protected splash page.
Version control software allows you to have “versions” of a project, which show the changes that were made to the code over time, and allows you to backtrack if necessary and undo those changes. This also allows me to development new features and test them.
I use Sublime Text, CodeKit, Git Tower, Transmit, and Adobe Creative Cloud.
I’ve become a huge fan of the Genesis Theme Framework from StudioPress (having built at least 200+ themes using Genesis). So all client themes are built as Genesis Child themes. If needed I can also work with BootStrap or Foundation based themes. Alot of my code in my custom starter theme is actually based off of the Foundation Framework.
I use a lot of great plugin’s with every website:
Advanced Custom Fields/ CMB2
Soliloquy Slider/ Royal Slider
WP DB Migrate Pro
I test my work in current versions of major desktop browsers including those made by Apple (Safari), Google (Chrome), Microsoft (Internet Explorer), Mozilla Firefox and Opera. I’ll also test to ensure Microsoft Internet Explorer 9 for Windows users get an appropriate, possibly different, experience.
Testing popular small-screen devices is essential in ensuring that a person’s experience of a design is appropriate to the capabilities of the device they’re using. I test my work in:
iOS: Safari, Google Chrome Android 5.x: Google Chrome and Firefox
I currently don’t test Blackberry, Opera Mini/Mobile, Windows Phone or other mobile browsers. If you need me to test using these, I can provide a separate estimate for that.
Staging Server & Site Migration
Once the site is developed to the point where it needs to be seen by the client, I push it to a staging server. Most often this is a subdomain on the designers server, but sometimes not. It just needs to be somewhere semi-public where the client can get to it.
Final Revisions and Changes
I try my best to allow for minor edits or changes within the scope of the original project. If I feel anything falls outside of the original scope then we can have a conversation and I can provide an estimate.