talks
/
phantomjs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '6fa1144ed9'
${ noResults }
phantomjs/vendor/prism
History
Buddy Sandidge 13b4225ae0 Add syntax highlighter to view 10 years ago
..
components Add syntax highlighter to view 10 years ago
plugins Add syntax highlighter to view 10 years ago
themes Add syntax highlighter to view 10 years ago
vendor Add syntax highlighter to view 10 years ago
.bower.json Add syntax highlighter to view 10 years ago
LICENSE Add syntax highlighter to view 10 years ago
README.md Add syntax highlighter to view 10 years ago
bower.json Add syntax highlighter to view 10 years ago
components.js Add syntax highlighter to view 10 years ago
examples.js Add syntax highlighter to view 10 years ago
gulpfile.js Add syntax highlighter to view 10 years ago
package.json Add syntax highlighter to view 10 years ago
prism.js Add syntax highlighter to view 10 years ago

README.md
Unescape Escape

Prism

Prism is a lightweight, robust, elegant syntax highlighting library. It's a spin-off project from Dabblet.

You can learn more on http://prismjs.com/.

Why another syntax highlighter?: http://lea.verou.me/2012/07/introducing-prism-an-awesome-new-syntax-highlighter/#more-1841

Contribute to Prism!

Prism depends on community contributions to expand and cover a wider array of use cases. If you like it, considering giving back by sending a pull request. Here are a few tips:

  • Read the documentation. Prism was designed to be extensible.
  • Do not edit prism.js, it’s just the version of Prism used by the Prism website and is built automatically. Limit your changes to the unminified files in the components/ folder. The minified files are also generated automatically.
  • Currently the build system building prism.js and the minified files is just a bunch of local settings in CodeKit. If someone wants to help export them to a config file, please contact me by opening an issue.
  • Please follow the code conventions used in the files already. For example, I use tabs for indentation and spaces for alignment. Opening braces are on the same line, closing braces on their own line regardless of construct. There is a space before the opening brace. etc etc.
  • Please try to err towards more smaller PRs rather than few huge PRs. If a PR includes changes I want to merge and changes I don't, handling it becomes difficult.
  • My time is very limited these days, so it might take a long time to review longer PRs (short ones are usually merged very quickly), especially those modifying the Prism Core. This doesn't mean your PR is rejected.
  • If you contribute a new language definition, you will be responsible for handling bug reports about that language definition. Soon I plan to add usernames of project owners for themes, plugins and language definitions so this becomes more clear to users.
  • If you add a new language definition, theme or plugin, you need to add it to components.js as well, so that it becomes available to the download build page.

Thank you so much for contributing!!