Hi, I'm Franky

I’m a designer, programmer, illustrator, and writer. I spend my time experimenting with technology, in critical thought, and solving puzzles.

In 2005, I began my journey into web development building personal portfolio galleries for myself. Since then, I’ve had contract work for front–end web design, back–end web development, competed in a few Hackathons, and explored programming outside of the browser…mostly iOS.

I’m a full–stack hacker type.1 My usual web development arsenal consists of HTML, CSS, JavaScript, PHP, and Python.2

My choice editors are Xcode, iA Writer, and MacVim.


Please, feel free to throw me an email at . If you just want to have a quick dialog, you can always reach me on Twitter — @frankymartz

Yes, I’m interested in new projects and opportunities.


This website was born on notebook paper and coffee napkins. The design was refined in the Sketch 3 — where colors and proportions were identified. Finally, its DNA was sequenced in MacVim.

I’m a firm believer in pushing technology forward. Modern browsers are action packed with cool features that just break down in older browser releases. So, from the beginning this site was built on top of the latest web technologies; only limiting myself to adhere to Google’s two version support.3

Development: Paper → Sketch 3 → MacVim
The Development Process
PaperSketch 3MacVim

Typography & the Right Side of the Brain

The fonts were snatched from Google Fonts. Wordy stuff uses Noticia, a contemporary humanist slab serif. While navigation and headers stick with the classically proportioned sans–serif, Lato. Finally, the GitHub feed rocks the Octicon font.

  1. My full–stack definition is described as a LAMP, or LEMP server configuration; with PHP as the “P” in both instances.

  2. I’ll occasionally use Python for server administration stuff — like Cron jobs or build tools. Sometimes BASH can get messy.

  3. On Google announced that they will limit “Google Apps” support to the current and prior major release of Chrome, Firefox, IE, and Safari.
    Official Enterprise Blog

  4. The gulpfile assembly turned out quite chunky. For a more complete observation, take a look at the source code.

  5. While GitHub stores the repository, the production deployment is pushed to an AWS S3 bucket.