docs: add a soft navigations integration page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- devtools
- Domain
- documentation
Research direction
The payload names no file path, so start by finding where the project keeps its existing docs pages and how they are linked in navigation, then compare with any integration page already there. Write a new page covering installation, the flow file, project and flow settings, recordings, reports and dry runs, and link out to the lighthouse-soft-navigation docs for step details. Done when the page is reachable from the docs navigation and each listed section is present.
Written by the indexing model from the issue text.
Description
Add an Integrations page that shows how to measure soft navigations in user flows with @push-based/lighthouse-soft-navigation: installation, the flow file, project and flow settings, recordings, reports and dry runs. The details of soft navigation steps stay in the lighthouse-soft-navigation docs, which the page links to.
- Dominant language
- HTML
- Stars
- 131
- Forks
- 7
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 42
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from push-based/user-flow
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
push-based/user-flow#355 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 24/100
push-based/user-flow#285 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
push-based/user-flow#272 · 1 comment ·
Maintainers usually reply within 1 day
-
nx-plugin - init command adds `"PLUGIN_NAME": "^0.0.0"` to `package.json`May be free again @ChristopherPHolder claimed this 1212 days ago, and no pull request is open. Openbug DX
push-based/user-flow#248 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
push-based/user-flow#247 · 1 comment ·
Maintainers usually reply within 1 day
All issues in push-based/user-flow
Similar issues
-
Versioning docs: say that no output from the 0.46 warning check means nothing is affectedPossibly taken @grelinfo claimed this today. Opendocumentation priority:low size:S
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
alphacrack/readme2demo#293 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
tmux-python/libtmux#856 ·
Maintainers usually reply within 1 day
-
area: docs complexity: trivial documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
accensa/x402-facilitator-stellar#775 ·
Maintainers usually reply within 1 day
-
→ Strings bug documentation easy
Difficulty 1/5 Under an hour Newbie friendliness 92/100
arturo-lang/arturo#2309 ·
Maintainers usually reply within 1 day