Move ON / OFFBOARDING LOG link to top of Onboarding/Offboarding Forms section

Open Beginner friendly
#2,105 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
frontend

Research direction

Start by locating the Project page's "Onboarding/Offboarding Forms" section and the existing ON / OFFBOARDING LOG link in the VRMS repository. Move the existing link above the form buttons, remove the explanatory sentence, and verify the link target, new-tab behavior, styling, and spacing in the rendered page.

Written by the indexing model from the issue text.

Description

complexity: small p-feature: Onboarding role: Front End size: 0.25pt
Overview

Improve discoverability of the ON / OFFBOARDING LOG by moving its link to the top of the Onboarding/Offboarding Forms section on the Project page. This will make it easier for users to access the log immediately after opening or submitting the embedded onboarding or offboarding Google Forms.

Action Items
  • Move the ON / OFFBOARDING LOG link so it appears at the top of the "Onboarding/Offboarding Forms" section, above the "Onboarding Form" and "Offboarding Form" buttons.
  • Remove the sentence "These actions are logged in the:" since the log link will now be self-explanatory when positioned at the top of the section.
  • Ensure the link styling remains consistent with the current design system (same link color and behavior).
  • Verify that the link opens the correct Google Sheet/log in a new tab.
  • Confirm that the layout spacing still appears clean and readable after repositioning the link.
Resources/Instructions
  • VRMS repository: https://github.com/hackforla/vrms
  • The ON / OFFBOARDING LOG should remain the same link currently used in the UI; only its placement within the section should change.
screenshot for the current layout of the **Onboarding/Offboarding Forms** section

Image

Dominant language
JavaScript
Stars
61
Forks
101
No merged PRs in 30d

Contributor guide

Open the contributing guide

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.

More from hackforla/VRMS

All issues in hackforla/VRMS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.