Open
Description
Flutter documentation is currently split between docs.flutter.dev and api.flutter.dev. However, pages on docs.flutter.dev frequently link to pages on api.flutter.dev. Users in a recent study were disoriented when they were taken to the API references site after clicking a link on the general documentation site. The navigation is completely different and the only way to get back to the previous page is to use the web browser's back button. The experience is disjoint.
Idea from team discussion: allow another website to embed content generated by DartDoc, without the navigation elements, and display that content in place.
Open question: when the user clicks links in the embedded API reference, what should happen?