Coda Tips and Tricks

  • 5 Comments
  •       618 words

Since I switched to Mac a two weeks ago, I’ve been looking at viable alternatives in how I go about coding my sites. During my time on social networks I have seen alot of people championing Coda and Textedit. However being the sucker I am for something which is aesthetically pleasing I decided to opt for Coda, I think it was their lovely leaf logo which won me over, fickle or what?

With any new program there is a learning curve, if the truth be told I’ve actually struggled to get to grips with Coda but I am determined for it to become my editor of choice. My intention for this post is simple – to tell people about the hints and tips which I have learned in the hope that I will learn a few new things myself.

Validation

If it isn’t already activated turn this option on by pressing the small triangle icon located at the bottom of the Coda window. The purpose of this is that it highlights the coding errors within your document before you put it through the arduous task of putting it through an HTML validator. You’ll notice the errors, if you have any, pop up in icons which resemble small bubbles.

Line Numbers

Line numbers can be enabled within the Coda window, like you will see in other WYSIWYG editors, such as Dreamweaver. This is very handy when, as mentioned above, you’ve just ran your code through an online validator. The validator will then tell you the error which it has found and present you with the line number the error is located on. These line numbers can be a life saver when spending time sorting out your code. To activate the line numbers simply press ‘view’ and select ‘show line numbers.’

Show File Paths

To show the save path of a file press the command button and click on the tab to show the exact save path.

Split A Window Vertically Or Horizontally

Although you can change this in the preferences you can split a window horizontally or vertically by pressing a button in the top right corner of a window. If you press Option you can switch it from vertical to horizontal and back again by clicking once more.

Is Your Font Size Too Small?

Press the Command button and then the plus or minus key depending upon which way you want your text to go.

Show .htaccess and Invisible Files

Go to View > Show Hidden files.

Preview Current File in Browser

If you want to open the file you are using in your own browser press the command button + Option + B.


These are most of the tips I’ve learned and read about since downloading the trial of this app. Below I have a few questions I would like to know the answers to.


A question I have for you

How do you create a connection for your sites in order to upload and download your files? During my first night of getting to grips with the software I found creating a connection to be quite hit or miss. Please enlighten me as to what option you choose to create/connect to your sites and what fields you fill out with what content.

My final question

Transmit. Do you use it and is it worth buying? I know Coda has it’s own built in ftp window but is it easier just from the start to use Transmit? I probably won’t be uploading massive files every day, I think I may just have answered my own question?

If you liked this article then please feel free to Tweet it
  • Who I am

    My name is Jack Osborne and I am a Glasgow–based designer and writer. You should follow me on Twitter.

5 Responses to “Coda Tips and Tricks”

  1. RE: Sites

    Root URL is the root url of the website you’re creating.

    Local URL is for doing local testing and is used for preview if it is available (provided).

    Remote Root is the path to the top level folder on the server. This determines where things get uploaded to.

    Local Root is the path to the top level folder on your local machine.

    The Connecting section is the really important information because it tells Coda how to actually establish a connection with your webserver for (S)FTPing files.

    The Terminal section is similar to the Connecting section except it is for the terminal view, i.e. it is used if you want to ssh into your server from Coda.

    The Source Control section is only relevant if you’re using subversion as it is not (as of yet) compatible with other types of source control

  2. Jack Osborne says:

    Excellent Bryan, that’s helped clear a few things up for me, I felt a bit daft when I couldn’t get anything to make a proper connection.

    Just had a quick look through your site and there’s alot of really interest stuff on it, I’ll be adding it to my bookmarks for future reading. Thanks once again, your help was greatly appreciated.

  3. I’m glad I could help and thanks about the stuff I’ve posted. More and more it seems as though my blog has become a chronicle of mistakes and lessons learned but I do tend to learn things the hard way and I can only hope the lessons I’ve learned help others.

    The biggest thing I want to learn is design, I mean I ‘get’ good design and really appreciate typography but I seem to have a lot of trouble crafting it.

    Anyway, best of luck with Coda and your new Mac.

  4. Jack Osborne says:

    A little update for the people who have read this article or are following the comments.

    Shortly after posting this blog Dave Shea posted two quick tips on exactly the same topic.

    accidental but awesome Coda discovery: Cmd + / comments or uncomments the current line/selection, with the proper langu age-specific syntax.
    http://twitter.com/mezzoblue/status/1143494552

    Cmd + ] and Cmd + [ to increase/decrease indenting. (both work in Textm ate too, apparently)
    http://twitter.com/mezzoblue/status/1143516554

    Enjoy!

  5. Paul says:

    Jack, Bryan excellent tips! Thank you so much for sharing, you’ve made it a little easier for me to get on with some coda-ing tonight :)