# Advanced Project Settings

**Published:** February 6, 2020 | **Authors:** Andy Schneider, Luc Leray, Shu Ding, Christopher Skillicorn, Leo Lamprecht | **Category:** Company News

*Control your projects with improved importing, settings, and Vercel CLI\.*

---

With the launch of [Zero Config Deployments](https://zeit.co/blog/zero-config), we made setting up your projects as easy as [importing a Git repository](https://zeit.co/docs), and having every push and pull request deployed with Vercel. No configuration.

Today, we're extending this process to non-JavaScript projects (like [Hugo](https://gohugo.io/) sites) and giving you full control over your project's automatically configured settings.

## Better Import

If your code is located in a subdirectory, you'll find it useful that connecting one of your Git repositories to Vercel will prompt you for specifying a **Root Directory**.

Additionally, you can now select a different **Framework** or overwrite its default settings:

![Select the right settings for your needs when importing repositories.](//images.ctfassets.net/e5382hct74si/56A5UQQ2NK9Vw3lP8LpLe3/f2b53ca7f75d9a36671f045308190ae3/modals.png)

## Better Project Settings

Once you've deployed your project, you might still want to continue tweaking its configuration until it meets all your needs – no matter how advanced they are.

Because of that, you can now fully customize all of the options mentioned above right from the Project Settings:

![Adjust your project's configuration at any time.](//images.ctfassets.net/e5382hct74si/5EXQ5XCjiwRz9Ku9meuyir/04e8f4ec5f3bb1e66c9538feb6530e62/my-site-settings.png)

All of the fields are automatically optimized for your Framework by default. Overwriting one of them, however, is as easy as turning on the `OVERRIDE` toggle.

## Better Vercel CLI

After [importing your Git repository](https://zeit.co/docs/v2/git-integrations), every push and pull request gets deployed automatically. However, sometimes you might want to create a quick manual deployment from the CLI.

To make this easy, creating new projects through our [command-line interface](https://zeit.co/download) now surfaces the automatically detected configuration and lets you edit it on the fly:

![Setting up a new Vercel project using Vercel CLI.](//images.ctfassets.net/e5382hct74si/1MzLWtlGG4kmchAr0BEW5q/1bb4130fd7c2198bb0b09fefb711797c/now-cli-first.png)

For subsequent deployments, those values naturally don't have to be configured:

![Deploying to an existing Vercel project using Vercel CLI.](//images.ctfassets.net/e5382hct74si/1D1MYanBr4qGvcOB7wgZBe/32a84b48f816dccdc46a95179c2f1c5a/now-cli-second.png)

> **Note:** In order to run `vercel dev,` please make sure to first deploy using `vercel`. Additionally, `vercel --confirm` can be run to auto-confirm the prompts.

Aside from allowing for customizing your Framework settings, as you can see, Vercel CLI now also lets you link your local codebase to any project on Vercel – no matter its name or scope.

## Conclusion

Thanks to the above changes, several new use cases are now possible:

- Projects without a `package.json` file (like [Hugo](https://gohugo.io/) or [Jekyll](https://jekyllrb.com/) sites) can be deployed.
- Your project can be located in a subdirectory of your Git repository.
- The Build Command, Development Command, and Output Directory can be customized.

> **Note:** The `--name` flag is now [deprecated](/docs/now-cli#commands/now/unique-options/name) in Vercel CLI.

With this release, we've also paved the way for several additional fields that will enable an even more extensive range of use cases in the future. [Stay tuned](https://twitter.com/vercel)[!](https://twitter.com/zeithq)

---

**More posts:** [View all blog posts](https://vercel.com/blog/sitemap.md) | [Changelog](https://vercel.com/changelog/sitemap.md)