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

Propose new file organization structure #1549

Closed
1 of 4 tasks
edwinjue opened this issue Aug 15, 2023 · 3 comments
Closed
1 of 4 tasks

Propose new file organization structure #1549

edwinjue opened this issue Aug 15, 2023 · 3 comments
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) draft Feature: Code Health Make our code more readable, testable, and modular Needs More Info Request for more info...Issue not clear ready for dev lead ready for developer lead to review the issue Role: Frontend React front end work size: 3pt Can be done in 13-18 hours

Comments

@edwinjue
Copy link
Member

edwinjue commented Aug 15, 2023

Overview

Once we get our site up on github pages, we may need to propose a new file organization structure that makes sense for volunteers, one that is intuitive to follow and makes it easy to find source files and assets.

We just need to be mindful of the way github pages compiles code using the workflow .yml file among other github pages requirements and find something that works for eveyrone

Action Items

  • Get site running on github pages Set up github pages for 311-data #1534
  • Proof of concept of a proposed file organization that does not break the site
  • Solicit feedback from other volunteers
  • Submit PR

Resources/Instructions

@ZekeAranyLucas
Copy link
Member

What are the problems with the existing file structure?

it's not clear what motivates this change.

@ryanfchase
Copy link
Member

I think this issue needs more concise Action Items. The previous comment is a good proposed question that should be answered in the Overview section (we need X because Y)

@ryanfchase ryanfchase added ready for dev lead ready for developer lead to review the issue and removed Tech Stack: New labels Jan 30, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this to New Issue Approval in P: 311: Project Board Jun 7, 2024
@traycn
Copy link
Member

traycn commented Jan 27, 2025

Ticket created from previous dev lead. Propose closing issue.

@traycn traycn closed this as completed Jan 29, 2025
@github-project-automation github-project-automation bot moved this from New Issue Approval to Done (without merge) in P: 311: Project Board Jan 29, 2025
@ryanfchase ryanfchase closed this as not planned Won't fix, can't repro, duplicate, stale Jan 29, 2025
@cottonchristopher cottonchristopher added the Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) label Feb 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Missing This ticket needs a complexity (good first issue, small, medium, or large) draft Feature: Code Health Make our code more readable, testable, and modular Needs More Info Request for more info...Issue not clear ready for dev lead ready for developer lead to review the issue Role: Frontend React front end work size: 3pt Can be done in 13-18 hours
Projects
Status: Done (without merge)
Development

No branches or pull requests

6 participants