Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Improve Styling and Responsiveness of Vocabulary Documentation" #139

Open
1 task done
wendy640 opened this issue Oct 8, 2024 · 1 comment
Open
1 task done
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟨 priority: medium Not blocking but should be fixed soon 🚧 status: blocked Blocked & therefore, not ready for work

Comments

@wendy640
Copy link

wendy640 commented Oct 8, 2024

Description

The documentation for the Vocabulary project is not fully styled and lacks responsiveness. It has issues with padding, margins, and overall layout, which affects the readability and usability of the docs across different devices and screen sizes.

Reproduction

  • Open the Vocabulary documentation on different screen sizes (e.g., mobile, tablet, desktop).

  • Observe inconsistent styling, including lack of proper padding, margins, and elements not scaling well.

  • Resize the browser window to different widths.

  • See how elements overlap or are not responsive.

Expectation

The documentation should be well-styled, responsive, and have consistent padding and margins to improve readability and user experience across all device sizes.

Screenshots

Screen Shot 2024-10-08 at 11 33 30 AM

Environment

  • Device: (eg. iPhone Xs; laptop)
  • OS: (eg. iOS 13.5; Fedora 32)
  • Browser: (eg. Safari; Firefox)
  • Version: (eg. 13; 73)
  • Other info: (eg. display resolution, ease-of-access settings)

Additional context

It appears that the current styles in the documentation do not properly account for mobile-first design, which impacts the overall usability of the documentation.

Resolution

  • I would be interested in resolving this bug.
@wendy640 wendy640 added 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix 🟧 priority: high Stalls work on the project or its dependents labels Oct 8, 2024
@possumbilities possumbilities added 🟨 priority: medium Not blocking but should be fixed soon 🚧 status: blocked Blocked & therefore, not ready for work and removed 🟧 priority: high Stalls work on the project or its dependents 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Oct 8, 2024
@possumbilities
Copy link
Contributor

This is a valid Issue, but one that needs to occur once a CMS/SSG direction is chosen. It was kept intentionally barebones at the beginning to make it easier to migrate.

Moving to 🚧 status: blocked Blocked & therefore, not ready for work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository 🛠 goal: fix Bug fix 🟨 priority: medium Not blocking but should be fixed soon 🚧 status: blocked Blocked & therefore, not ready for work
Projects
Status: Backlog
Development

No branches or pull requests

2 participants