You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Although the UI looks identical, the header nav is not being shared between the main page and the docs page. For instance, a retina logo was added to the docs in #2874, but http://angularjs.org still has the old logo.
Browsing through the repo on GitHub, it isn't clear where the home page source is being rendered from, but it clearly isn't using the same template as the docs. To prevent bugs like the above where a change on one page doesn't propagate to the other (creating an inconsistent experience), the nav code should be shared among both.
The text was updated successfully, but these errors were encountered:
keeping the two in sync is not that easy because the code lives in two different repos. I suppose we could just create a bower module (a component directive) that would contain just the header and then import it into both apps, but that would then impact the rendering time, since the template expansion would happen only after angular bootstraps, which I fear is not going to be a good user experience.
The long term aim would be probably to merge the home page app and docs app into a single app. This should be possible with bike-shed eventually, meaning that the homepage would just become a generated page.
Moving to bike-shed
Although the UI looks identical, the header nav is not being shared between the main page and the docs page. For instance, a retina logo was added to the docs in #2874, but http://angularjs.org still has the old logo.
Browsing through the repo on GitHub, it isn't clear where the home page source is being rendered from, but it clearly isn't using the same template as the docs. To prevent bugs like the above where a change on one page doesn't propagate to the other (creating an inconsistent experience), the nav code should be shared among both.
The text was updated successfully, but these errors were encountered: