00356f96c5
Summary: Previously we used <Link/> everywhere with useBaseUrl to avoid link destinations depending on the current url of the page. This isn't necessary if you instead link to the **file name**, rather than the **url path**. Then the links are resolved at build time, and work across imported markdown files etc. This diff just does the pages under Features, because other ones will get conflicts. I'll do those later. Reviewed By: nikoant Differential Revision: D25589707 fbshipit-source-id: 35ca986e19fc2af1054b81d7253eeb3827947ab8
16 lines
881 B
Plaintext
16 lines
881 B
Plaintext
---
|
|
id: navigation-plugin
|
|
title: Navigation
|
|
---
|
|
import useBaseUrl from '@docusaurus/useBaseUrl';
|
|
|
|
→ [See setup instructions for the Navigation Plugin](../setup/navigation-plugin.mdx)
|
|
|
|
The Navigation Plugin allows users to quickly navigate to deep links within their mobile applications to help speed up the development cycle. The plugin is designed to integrate easily within your existing navigation framework or as a stand alone tool. Users can bookmark deep links and jump to them via the button in the tool bar.
|
|
|
|
<img alt="Navigation Plugin Button" src={useBaseUrl("img/navigation-plugin-1.png")} />
|
|
|
|
Navigation events within the app can also be logged to Flipper. This allows the user to view past navigation events and jump straight to them, or export the navigation events for reporting.
|
|
|
|
<img alt="Navigation Plugin UI" src={useBaseUrl("img/navigation-plugin-2.png")} />
|