Closed jelbourn closed 5 years ago
I think we discussed just having another Github builds repository for that, right? Pushing it to NPM might cause confusion since it's technically just our internal "package".
Is there any reason not to reuse the existing repo?
I was just thinking that we need another repository because one would be for the @angular/material-examples
package and the other one just for the individual API/guide/StackBlitz files.
dependencies: {
"@angular/material-examples": "github:angular/material2-docs-content"
}
After re-reading, I think you've actually meant that we should somehow package the API, guide and StackBlitz files into the same NPM package. That way we would eliminate all scripts, right?
Yep, exactly
We can close this once #14612 and #14634 are merged.
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.
We currently publish the docs content to https://github.com/angular/material2-docs-content in an ad hoc structure. It's not an npm package, meaning we need a bash script to pull in the content to the right place.
Things that are pending:
.html
, needed for source view of examples)