-
Notifications
You must be signed in to change notification settings - Fork 594
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve README #3
Conversation
|
||
[![Build Status](https://travis-ci.org/Microsoft/gulp-core-build.svg?branch=master)](https://travis-ci.org/Microsoft/gulp-core-build) [![Dependencies](https://david-dm.org/Microsoft/gulp-core-build.svg)](https://david-dm.org/Microsoft/gulp-core-build) | ||
|
||
The gulp build system, along with its rich plugin ecosystem, is a very powerful tool for web development projects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say
... is a very powerful tool for NodeJS-based development environments.
|
||
The gulp build system, along with its rich plugin ecosystem, is a very powerful tool for web development projects. | ||
However, project gulp build setups become difficult to manage over time, as gulpfiles grow in complexity. This project | ||
simplifies a number of aspects of getting a build setup going for a majority of scenarios. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"for a majority of scenarios" sounds a little superflous.
@@ -0,0 +1,164 @@ | |||
# gulp-core-build [![npm version](https://badge.fury.io/js/%40microsoft%2Fgulp-core-build.svg)](https://badge.fury.io/js/%40microsoft%2Fgulp-core-build) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the root README lets just have a summary of concept and links to the various projects. I've checked this in as a basic first step, but it could use more of the definitions. Could you merge master?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- remove root readme
# Conflicts: # gulp-core-build-karma/README.md # gulp-core-build-mocha/README.md # gulp-core-build-sass/README.md # gulp-core-build-serve/README.md # gulp-core-build-typescript/README.md # gulp-core-build/README.md
Checked this in after removing the top level README, which was contentious |
externalCss option and changes to the typescript generation code.
Improve logging to handle more scenarios and print more information. …
* Typings updates. * Updating readme. * Fixing repo name.
Add --vscode support for debugging through vscode during gulp serve
Don't publish the shrinkwrap
* Updating utility to reuse themes from global state. * Making the IE workaround more legible.
* Add licence and contributing files * chore: add a Code of Conduct Co-authored-by: Franziska Hinkelmann <franzih@chromium.org> Co-authored-by: google-cloud-policy-bot[bot] <80869356+google-cloud-policy-bot[bot]@users.noreply.github.com>
Update @rushstack/heft-jest-plugin to be compatible with multi-phase Heft
Rename "enabled" -> "subspacesEnabled"
Improve and add README for a couple of projects