Meta Issue: Roadmap - Q2 2018

[nshahan]

Current Projects

We schedule our work a quarter at a time. Here is what we are working on right now.

Improve the documentation generated in the component gallery generator.

• Improve documentation consistency between components.
• Add documentation for the Angular API of the components; inputs, outputs etc.
• Add documentation for Sass mixins used for customizing the appearance of components.

Add new components.

• Material Slider
• Material Stepper

Evaluate mono repo layout for angular_components, examples, gallery etc.

• Simplify syncing process when all code is in one repo?
• Are there additional packages to bring into this repo?

Improve gallery and example usability.

• Build and serve individual examples locally.
• Gallery generators usable for other packages.

[nni123]

anything on data table component. I think it is pretty important one to have for enterprise development.

[nshahan]

@nni123 Work to open source is still progressing but we still can't say exactly when it will be ready.

[pcariel]

@nshahan ping Q3? I am starting a project, I would like to know what the next news will be.

[TedSander]

@pcariel things are going really well. We have MANY people working on it, even some interns. We hope to have something this quarter, but we can't commit to it yet.

[nshahan]

Q2 2018 - Work Summary

Improve the documentation generated in the component gallery generator.

• ✔️ Improve documentation consistency between components.

  Documentation fixit cleaned up many inconsistencies in the presentation.

• ✔️ Add documentation for the Angular API of the components; inputs, outputs etc.

  Now generating docs for @Inputs and @Outputs from the dartdoc comments.

• 🔴 Add documentation for Sass mixins used for customizing the appearance of components.

  Will look at this more in Q3.

Add new components.

• ✔️ Material Slider

  15adee4

• ✔️ Material Stepper

  dd14485

Evaluate mono repo layout for angular_components, examples, gallery etc.

• Simplify syncing process when all code is in one repo?

  Yes would make syncing considerably easier.

• Are there additional packages to bring into this repo?

  Table components when they get released, possibly the shared code between the packages.

Improve gallery and example usability.

• 🔴 Build and serve individual examples locally.

  Still would like this to work, but getting build_runner and bazel working at the same time has been difficult.

• 🔴 Gallery generators usable for other packages.

  Not a priority at this time.

[nshahan]

Roadmap for Q3 2018 (finally) posted #312.