oss-slu / oss-slu/oss_dev_analytics

Implement and Integrate CI/CD Metrics Page

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

Nobody has claimed this yet.

frontend javascript
Dominant language
JavaScript
Stars
2
Forks
2
Avg merge
1m
Merged PRs (30d)
1

Description

Description

Once the design draft from the previous issue is approved, this task involves the actual frontend implementation of the CI/CD page. The developer will build the page in the React/Vite architecture and ensure it correctly pulls and requested displays data. THIS DESCRIPTION WILL BE UPDATED WITH MORE INFORMATION ONCE #117 IS COMPLETED

Steps to Reproduce
  1. Initialize the new /cicd route within the React application, ensure it follows correct project structure as found in /docs/CodingConventions.md
  2. Develop the UI components (charts, tables, and status flags) as specified in the approved design documentation.
  3. Connect the components to the data source (if needing a data source, will be updated with more specifics), ensuring CI/CD metrics are being pulled from the test_data.json or equivalent backend endpoint.
  4. Conduct a UI audit to ensure the implemented page matches the approved style guidelines perfectly.
Expected Behavior

A fully functional, responsive CI/CD metrics page that provides the CI/CD team with the requested metrics

Environment
  • Tech Stack: React, Vite, Tailwind CSS.
  • Data Source: Backend/test_data.json.

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 by reviewing the design dependency in #117 and the project structure in /docs/CodingConventions.md. Then inspect the existing React/Vite routes and Backend/test_data.json before defining the /cicd page. Done means a responsive page with the approved charts, tables, status flags, data connection, and completed UI audit.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react, tailwindcss, vite
Domain
ci-cd, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.