Something New Every Day

In terminal:

type 'git status' [enter]

your changed files should show up

type 'git reset HEAD --hard' [enter]

Git should rewind to last commit and discarded tracked file changes (if you had created a new file it wouldn't have deleted that)

THESE THINGS HAVE TO HAPPEN in order for your custom domain GitHub pages site to work:

1) Repo containing your files must be named 'name.github.io'

2) A file named 'CNAME' must contain your custom domain name (i.e. examplename.com). This file would is placed in the repo.

3) Instead of master, a branch named 'gh-pages' must be the default branch. You can change the default branch in your repo/settings/Default Branch dropdown under 'Settings'

If you're trying to connect to the local server and 'foreman start' doesn't work, because you get an error that contains (Bundler :: Gem Not Found).

try typing

bundle install [enter]

then letting all the ruby gems install that you may be missing

then try again:

foreman start [enter]

IRB is a read-evaluate print loop for Ruby.

get on master branch ('git branch' [enter])

if there is an * beside another branch besides master, type: 'git checkout master [enter]'

then: 'git pull' [enter]//pulls down all the commits you're behind

(if there are conflicts go and find and resolve them in your files then add the file by typing 'git status [enter]' and then according to what result you get when it says "both modified:" type 'git add filename' [enter])

then: 'git rebase --continue' [enter]

then: 'git push' [enter]

if there are still errors, even though you've resolved, type: 'git push -f' [enter]

** If you're trying to rebase your branch against master, at this point you would need to: **

git checkout your_branch_name [enter]

git rebase master [enter]

(There could be conflicts at this stage too, as your files are compared against master. If so - address the issues that come up, save changes to the file, and add that file back in: 'git add file/path/name.erb' [enter])

then git rebase master [enter]

type pwd [enter]     //(pwd stands for 'present working directory')

//terminal will display the path of where you are currently

type cd .. [enter] //(this will send you up a level in the file path)

type ls [enter]

//terminal should bring up a list of repositories on the new level, if this is the level where you want to do your switching, continue...

type cd NewRepoName [enter]

try typing this into terminal: ls tmp/pids [enter]

if nothing, try typing any of the following commands: 

ps ax | grep puma [enter]

ps ax | grep foreman [enter]

ps ax | grep solr [enter]

ps ax | grep thin [enter]

ps ax | grep redis [enter]

If any of those return a result that does NOT include 'grep', not the number at the beginning of the line.

Then go to your terminal and type: kill ##### [enter]

then: ps ax | grep 'whatever you used' [enter]

then: foreman start [enter]

type: cd path/to/where/your/repository/is [enter]

type: git status [enter]

How had I never made a GIF before? I just hadn't. Because I get intimidated by stuff and if no one ever asks me, then I tend to be too shy to try. 

Well that's no way to improve as a designer! I recently read Allison Grayce's New Year's Resolution: Become a Better Designer article and was inspired to both try things I've been meaning to try and share my learning experiences.

So. Today my supersmart amazing gif expert coworker held my hand through making a GIF in Photoshop CS6 and that's the new thing I learned today!

Here's how:

1) Set up your layers.

GIFs (obviously) are a series of still images. So set up your layers with this in mind. You can have as little as two and as many as you want. Each of your layers should represent a different stage in the GIF animation. If all you're doing is changing the color of one thing (as in my case- see below) then each layer should be exactly on top of one another. If you're showing a position change, then this should be reflected as you turn on and off that particular layer.

2) Open up the timeline feature.

In the bottom left of your Photoshop CS6 window, beneath where it says 'Doc 16k....etc' you should see a Timeline button. Click until it opens. Go ahead and pull this area up to give yourself room to work.

3) Arrange your layers in the timeline

If you have any experience with video editing programs, the rest will come as second nature. Once you open the timeline, your layers will automatically load up, except they will all be stacked on top of one another and as the GIF is concerned- all happening at once.

So what you have to do is set the duration that you want each frame to play and arrange them as you would like them to play.

I set mine to where each frame lasts a second and they sequence through the colors of the rainbow.

4) Save with correct settings

Once they're arranged to your satisfaction, go to File > Save for Web and choose any of the GIF options. (I don't at this point know what the difference is. Feel free to enlighten me, this is all in the name of learning!)

The crucial thing about this save is to choose 'Forever' under Looping Options in the Animation section of the save window. This will ensure that your GIF will keep on going!

5) Go forth and give the world your GIFs!

Upload to blogs, Dribbble, wherever you feel your GIFs are most valued. 

Today I learned how to install an alternate color scheme into Coda 2. Through an inquiry thread on news.layervault.com, I found the Github files to an awesome color scheme by Chris Kempson. Prior to this, I had no idea you could upload premade themes into your text editor of choice.

So here's how I did it. (Although I have a feeling there's an easier way and please do, if you're reading this and know it- comment and tell me!):

1) Copied the Github source files into a blank document in my own text editor.

2) Saved file as 'My_File_Name.sss*' 

3) Opened Coda 2 Preferences Window

4) Go to the colors tab

5) Click settings gear wheel and choose 'import'

6) Find where I saved 'TomorrowNightEighties.sss' and import that baby!

Ready to go. Color makeover in action.