Skip to content
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

Quest: Ember Engines Guides MVP Tracking issue #55

Open
villander opened this Issue Apr 4, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@villander
Copy link
Contributor

commented Apr 4, 2019

Hello and thanks so much for helping out with the Ember Engines Guides! We need the knowledge you've gained over the years using ember-engines

High level tracking, in progress:

This section is purely for tracking how much work we still have left to do, in a very broad sense.

General

  • Almost all docs from README should be moved to ember-engines.com. Having similar but different info in both places is confusing and unmaintainable. [ issue ember-engines/ember-engines/issues/540 ]

  • Consider using https://github.com/ember-learn/ember-cli-addon-docs to standardize the docs and guides and to make them version-specific. [ issue #50 ]

  • Clarify the philosophy and intended uses for engines. [ issue #57 ]

    Is the "Why Use Engines?" section on http://ember-engines.com/ sufficient?

  • Update the "Engines Roadmap" section [ issue #56 ]

    Link to the 1.0 Roadmap

  • Include a section on using engines with Fastboot. [ issue #58 ]

  • Testing section is completely blank. We need to discuss what's possible today. [ issue #59 ]

  • Make Ember Engines more public for beginners in Ember.js [ issue ember-learn/guides-source/issues/701 ]

Building Engines

  • Clarify that engines should always be built together with their host app and other engines, regardless of whether they are lazy or eager. This is required for hosts to understand and properly bundle engine dependencies and routes. [ issue #56 ]

  • Explain what will happen when there are dependency mismatches between different engines and/or their host app. [ issue #60 ]

  • Explain the dependency deduping that is currently performed. [ issue #16 ]

  • Explain the manual verification of dependencies that is needed right now. [ issue #61 ]

  • Include a few examples that lists a host app and engines, as well a few dependencies (common and shared) to illustrate points. [ issue #62 ]

@villander villander changed the title Quest: Ember Guides MVP Tracking issue Quest: Ember Engines Guides MVP Tracking issue Apr 4, 2019

@amyrlam amyrlam referenced this issue Apr 8, 2019

Merged

The Ember Times No. 93 - April 12th 2019 #60

9 of 17 tasks complete
@lifeart

This comment has been minimized.

Copy link

commented Apr 16, 2019

Engines example repo - https://github.com/catz/eng-test

@villander

This comment has been minimized.

Copy link
Contributor Author

commented Apr 18, 2019

thanks @lifeart I'll do a awesome demo with this work, adding more UI/UX.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.