Meta tags:

Headings (most frequently used words):

projects, defaults, for, new, initial, values, existing, location, missing, settings, old,

Text of the page (most frequently used words):
the (13), codekit (12), new (11), #settings (11), defaults (10), #project (9), for (9), file (8), projects (8), you (7), your (6), that (6), will (5), are (5), those (4), from (4), values (4), initial (4), this (3), add (3), any (3), options (3), missing (3), set (3), preferences (2), codekit3 (2), but (2), app (2), read (2), old (2), and (2), config (2), can (2), been (2), features (2), only (2), folder (2), yellow (2), bar (2), now (2), first (2), plugins (2), custom (2), languages (2), frameworks (2), minifier (2), tools (2), postcss (2), browsers (2), steps (2), topics (2), privacy, policy, report, bug, email, support, follow, developer, twitter, made, san, diego, delete, lose, default, stored, located, library, com, incident57, location, also, created, files, they, were, named, has, not, one, automatically, carry, over, pull, pulled, happen, hasn, while, meantime, have, added, these, used, already, contains, apply, specified, brand, existing, opens, familiar, area, see, across, top, adjust, then, click, button, done, choose, menubar, edit, when, all, start, off, with, specify, what, should, time, watch, screencast, faq, upgrading, mode, more, coda, sublime, text, atom, nova, editor, scripting, team, workflows, adding, environment, variables, hooks, advanced, eslint, syntax, checkers, jeet, nib, susy, zurb, foundation, bitters, bourbon, bootstrap, tailwind, gif, svg, jpeg, png, webp, image, optimizers, json, markdown, kit, slim, haml, pug, typescript, coffeescript, javascript, stylus, less, sass, bless, lightningcss, html, cache, buster, rollup, bundler, terser, babel, transpiler, npm, other, purgecss, autoprefixer, license, recovery, troubleshooting, git, stuff, know, target, build, second, output, paths, action, language, browser, sync, live, reload, getting, started, close, view, buy, menu, updates, about, help, videos,

Text of the page (random words):
codekit defaults for new projects features videos help about updates menu buy now defaults for new projects view topics close topics first steps getting started live reload browsers browser sync set language options set output paths action second steps defaults for new projects build your project set target browsers stuff to know codekit git troubleshooting license recovery postcss tools autoprefixer purgecss custom postcss plugins other tools npm babel js transpiler terser js minifier rollup js bundler cache buster html minifier lightningcss bless languages sass less stylus javascript coffeescript typescript pug haml slim kit markdown json image optimizers webp png jpeg svg gif frameworks codekit frameworks tailwind bootstrap bourbon bitters zurb foundation susy nib jeet syntax checkers eslint advanced hooks environment variables adding custom languages team workflows scripting codekit editor plugins nova atom sublime text coda 2 more read only mode upgrading from 2 0 faq 2 59 watch the screencast initial values when you add a folder to codekit for the first time all settings start off with initial values you can specify what those initial values should be choose file edit defaults for new projects from the menubar this opens the familiar project settings area but you ll see a yellow bar across the top adjust settings then click the done button in that yellow bar those settings are now the defaults for new projects existing projects these initial defaults are used only for brand new projects if you add a folder that already contains a config codekit3 file codekit will apply the settings specified in that file missing settings if your project settings file is missing any options those values will be pulled from your new project defaults this can happen if a project hasn t been in codekit for a while and in the meantime new features have been added to the app old 2 0 projects codekit 2 0 also created project settings files they were named config codekit if you add a project to codekit 3 that has a 2 0 settings file but not a 3 0 one the app will read the old 2 0 file and automatically carry those settings over for any options that are missing or any that are new to 3 0 codekit will pull from your new project defaults defaults location your default settings are stored in codekit s preferences file it s located at library preferences com incident57 codekit3 if you delete this file you will lose your new project defaults made in san diego ca follow the developer on twitter email support report a bug privacy policy