Skip to content
This repository

An open source code editor for the web, written in JavaScript, HTML and CSS.

branch: rlim/improved-…

This branch is 4 commits ahead and 5266 commits behind master

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 samples
Octocat-spinner-32 src
Octocat-spinner-32 tasks
Octocat-spinner-32 test
Octocat-spinner-32 tools
Octocat-spinner-32 .gitattributes Normalized Line Endings and added .gitattributes February 02, 2013
Octocat-spinner-32 .gitignore
Octocat-spinner-32 .gitmodules
Octocat-spinner-32 .jshintrc Add grunt tasks for jshint and jasmine. Refactor and move package.jso… January 24, 2013
Octocat-spinner-32 .travis.yml
Octocat-spinner-32 CONTRIBUTING.md
Octocat-spinner-32 Gruntfile.js
Octocat-spinner-32 LICENSE Changed license to be MIT September 21, 2012
Octocat-spinner-32 NOTICE
Octocat-spinner-32 README.md
Octocat-spinner-32 package.json
README.md

Welcome to Brackets! Build Status

Installers for the latest build can be downloaded here.

This is an early version of Brackets, a code editor for HTML, CSS and JavaScript that's built in HTML, CSS and JavaScript.

What makes Brackets different from other web code editors?

  • Tools shouldn't get in your way. Instead of cluttering up your coding environment with lots of panels and icons, the Quick Edit UI in Brackets puts context-specific code and tools inline.
  • Brackets is in sync with your browser. With Live Development, Brackets works directly with your browser to push code edits instantly and jump back and forth between your real source code and the browser view.
  • Do it yourself. Because Brackets is open source, and built with HTML, CSS and JavaScript, you can help build the best code editor for the web.

You can see some screenshots of Brackets on the wiki and intro videos on the Brackets YouTube channel.

Brackets is early in development, so many of the features you would expect in a code editor are missing, and some existing features might be incomplete or not as useful as you'd want. But if you like the direction it's going, the CONTRIBUTING.md file contains some useful links to help you get started. Please contribute!

The text editor inside Brackets is based on CodeMirror—thanks to Marijn for taking our pull requests, implementing feature requests and fixing bugs! See Notes on CodeMirror for info on how we're using CodeMirror.

How to run Brackets

Brackets isn't ready for general use yet. It's still early in development, is missing a lot of basic editor features, and probably has bugs. That said, we've actually been using Brackets to develop Brackets for awhile now, so what's there is reasonably stable.

Although Brackets is built in HTML/CSS/JS, it currently runs as a desktop application in a thin native shell, so that it can access your local files. (If you just try to open the index.html file in a browser, it won't work yet.) The native shell for Brackets lives in a separate repo, adobe/brackets-shell.

The Brackets native shell currently runs on Mac and Windows. The community has started working on a Linux port, and is making great progress; if you're interested, check out the Linux Version wiki page.

You can download stable builds of Brackets from download.brackets.io. If you want to pull the repo directly via git, see How to Hack on Brackets for instructions on how to get everything.

By default, Brackets opens a folder containing some simple "Getting Started" content. You can choose a different folder to edit from File > Open Folder. (Might we suggest editing the Brackets source code and submitting some pull requests?)

Most of Brackets should be pretty self-explanatory, but for information on how to use its unique features, like Quick Edit and Live Development, please read How to Use Brackets. The extensions wiki page has a list of extensions that have been contributed. Also, see the release notes for a list of new features and known issues in each build.

I found a bug/missing feature!

Issues starting Brackets the first time? Please review Troubleshooting.

Brackets bugs are tracked in the Brackets github issue tracker. When filing a new bug, please remember to include:

  • Brackets version/sprint number (or commit SHA if you're pulling directly from the repo)
  • Platform/OS version
  • Steps to reproduce problem with actual and expected results
  • Link to test files (you can create a gist on gist.github.com if that's convenient)

More details on how to file an issue can be found here.
For feature requests, go ahead and file them in the issue tracker; they'll be converted to user stories on the public Brackets backlog*.

* Please excuse the mess in the "Icebox (To Be Reviewed)" list. We're still importing data from our internal system.

I want to help!

Awesome! Please read How to Hack on Brackets.

I want to keep track of how Brackets is doing!

Not sure you needed the exclamation point there, but I like your enthusiasm.

Something went wrong with that request. Please try again.