Tasks to Reach 1.0

We should focus on what still needs to be done to call a release a "1.0" release. Here we should compile a list and document the tasks. I'm willing to help, but I don't know exactly what to do.

- [ ] Doc issues (Tracked in projects on docs repo [links here](#issuecomment-570353348))
- [ ] Binding Issues (not sure what this means, but @carlosrovira mentioned this).
- [ ] Critical Missing Components (compose a list of this)
- [ ] Improved CSS Support (what exactly needs improvement?)
- [ ] What else can we do to make Royale compelling? This can be both features and education.
- [ ] Fix Build Server Release Scripts

Start with the checklist and the linked docs-repo project, then review the build server release scripts and the unresolved binding, component, and CSS items. Done means the 1.0 requirements are defined as an actionable, agreed list with ownership or next steps.

Written by the indexing model from the issue text.