Jump to content
quickjeff

Design, Development and Search Website

Recommended Posts

Hi Guys, 

So we have been working with ProcessWire for sometime now.  We absolutely love ProcessWire so much that we have changed our site from a custom build on a custom CMS to WordPress and now ProcessWire and will never go back to anything else.  We launched a small version of our site to test the migration from WordPress a couple months ago and now have finalized a new look and feel.  We are a small team based out of the Chicagoland area that is eager to grow.

Our go to CMS is ProcessWire for our clients.  

Please take a peak at:

QuickToImpress.com

We are currently running the latest version of ProcessWire with Template Editor Module.

We are looking to start building some of our own modules in the near future.

Ryan Cramer, thank you for such an incredible CMS.  ProcessWire community, thank you for such an amazing group of fellow developers, designers and SEOS.  You guys are all great and have helped us grow so much with answers to API questions, suggestions and advice.

  • Like 9

Share this post


Link to post
Share on other sites

I am, uh, impressed :D. Very nice and clean site (love the fonts and colours!). Loads quickly too. Nice showcase sites as well. Thanks for sharing Jeff :-)

Edited by kongondo
  • Like 2

Share this post


Link to post
Share on other sites

Very glad to hear you've made the switch - its really awesome to hear great feedback!

Site looks very impressive (kongondo, you've started something here...) indeed. One thing to point out: under the "Stop trying to build your own website." block, there's a closing HTML comment tag. This is being shown because of the following:

<!-- One -->
<!--<section id="one" class="wrapper style1">
    <div class="container">
        <header class="major">
            <h2>We design and develop websites that drive results.</h2>
            <p>Increase your customer base, build your business and remain competitive with our website design and development expertise.</p>
        </header>
        <!--<div class="slider">
            <span class="nav-previous"></span>
            <div class="viewer">
                <div class="reel">
                                                    
                </div>
            </div>
            <span class="nav-next"></span>
        </div>
    </div>-->
</section>-->

That last comment closer...

Thanks for sharing your work :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi Mike, we must have missed this last piece, since that was the last element added to replace a previous message. We simply commented out the previous message temporarily as we have something sweet cooking up to release soon!

Thanks for the catch, it is now fixed! 

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By iipa
      Hi everybody!
      I have been reading about Multisite, but it kinda bugs me that every topic talks about having both admin and database same for multiple sites.
      I have a project where customer tests it by adding content to the site, while I still need to do some changes here and there in code, maybe some in database. If something crashes for a while, customer can't keep testing, which is a bit problematic.
      Is there any way that I could have two separate versions of one site ("production" and development) that share the same database, but are otherwise independent? Just the thought of having to migrate database every time I want to show client something new gives me anxiety 😁
    • By quickjeff
      Hi Guys, 
      I wanted to post this thread to get some insight as to how others are migrating from a staging directory inside a live server to the actual root directory.
      I typically develop a project locally using Mamp and then move into a staging environment on a staging server . There are some cases the project requires to move the site into a directory inside a live site to make deployment of the new project move faster.
      When I move a project into a directory on the live server of domain.com/test/ I run into an issue of content links.
      What I mean is that I look at the source code in the CKEDITOR for a field and the link will display:
       domain.com/test/whatever-the-link-is/ 
      or 
      domain.com/test/assets/file.pdf
      or
      domain.com/test/assets/image.jpg 
       
      The issue is, when I move to a live site, I have to go back and change tons of links from:
      domain.com/test/whatever-the-link-is/
      to 
      domain.com/whatever-the-link-is/  
       
      How are you guys making the link changes across the entire site at once?
      Are you using SQL Commands? Something in ProcessWire?  Any suggestions will help eliminate the manual process.
    • By formmailer
      Hi!
      I am redesigning my site and set up a development version of the site (plain copy) using the same database. 
      During the redesign process I became interested in the CroppableImage module, which requires the dev version of PW.
      I upgraded the files in my development sites, but want to check with you before I start installing the new modules in the test version:
      Can this cause problems with the production site as long as it isn't using any of the new fields/modules?
      //Jasper 
×
×
  • Create New...