nf-core / nf-core/stats

Add parameterized pipeline detail pages for traffic data

Open
#65 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
2
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Follow-up from PR #52, related to parent issue #61

Feature request

Create individual detail pages for pipelines showing their specific traffic patterns and metrics.

Implementation approach

1. Parameterized routing
  • Create a route like /code/pipelines/[pipeline_name]/traffic
  • Use Evidence's parameterized pages feature
  • Link from the main traffic leaderboard and Top 10 list
2. Pipeline-specific visualizations
  • Show traffic trends for individual pipeline
  • Include:
    • Views and clones over time (line/area charts)
    • Daily heatmap of activity
    • Comparison to nf-core averages
    • Release markers on timeline
    • Top referrers (if available)
3. Navigation
  • Add links from leaderboard tables to detail pages
  • Include breadcrumb navigation
  • Add "View detailed traffic" button/link

Acceptance criteria

  • Parameterized pages work for any pipeline name
  • Detail pages show pipeline-specific traffic data
  • Navigation from leaderboard to detail pages works
  • Charts are properly filtered to show only selected pipeline data
  • Page handles non-existent pipelines gracefully

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with PR #52 and parent issue #61, then review the existing traffic leaderboard and Top 10 list. Use Evidence's parameterized pages feature for /code/pipelines/[pipeline_name]/traffic, and treat the acceptance criteria as done: filtered charts, working navigation, and graceful handling of non-existent pipelines.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
analytics, data-visualization, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.