-
-
Notifications
You must be signed in to change notification settings - Fork 776
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
ER: Rationalizing the sponsors and partners info in code base #6819
Labels
Complexity: Large
Complexity: Medium
Draft
Issue is still in the process of being created
ER
Emergent Request
good first issue
Good for newcomers
Issue Making: Level 2
Make issue(s) from an ER or Epic
Issue Making: Level 4
Create an Epic Issue, and it's Level 2 or 3 issues
P-Feature: About Us
https://www.hackforla.org/about/
P-Feature: Home page
https://www.hackforla.org/
P-Feature: Project Info and Page
A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
P-Feature: Projects page
https://www.hackforla.org/projects/
role: back end/devOps
Tasks for back-end developers
size: 1pt
Can be done in 4-6 hours
Milestone
Comments
ExperimentsInHonesty
added
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
size: 0.25pt
Can be done in 0.5 to 1.5 hours
ER
Emergent Request
role missing
Complexity: Missing
labels
May 5, 2024
ExperimentsInHonesty
added
the
Draft
Issue is still in the process of being created
label
May 5, 2024
ExperimentsInHonesty
added
good first issue
Good for newcomers
Complexity: Medium
Complexity: Large
labels
May 5, 2024
sponsors-partners.ymlschema
file contents
|
ExperimentsInHonesty
added
role: back end/devOps
Tasks for back-end developers
and removed
Complexity: Missing
role missing
labels
May 5, 2024
4 tasks
9 tasks
ExperimentsInHonesty
changed the title
ER: Rationalizing the sponsors and partners info across the site
ER: Rationalizing the sponsors and partners info in code base
May 5, 2024
|
ExperimentsInHonesty
added
P-Feature: Project Info and Page
A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
P-Feature: About Us
https://www.hackforla.org/about/
P-Feature: Home page
https://www.hackforla.org/
P-Feature: Projects page
https://www.hackforla.org/projects/
Issue Making: Level 2
Make issue(s) from an ER or Epic
Issue Making: Level 4
Create an Epic Issue, and it's Level 2 or 3 issues
size: 1pt
Can be done in 4-6 hours
ready for merge team
needs a senior review either to do some re writing or to approve it for ready for prioritization
and removed
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
Draft
Issue is still in the process of being created
size: 0.25pt
Can be done in 0.5 to 1.5 hours
labels
May 6, 2024
Please, can someone from the @hackforla/website-merge team give me a review on this ER and see if you see any problems with it before I prioritize? |
2 tasks
3 tasks
ExperimentsInHonesty
added
Draft
Issue is still in the process of being created
and removed
ready for merge team
needs a senior review either to do some re writing or to approve it for ready for prioritization
labels
May 7, 2024
hold until I finish talking to People depot. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Complexity: Large
Complexity: Medium
Draft
Issue is still in the process of being created
ER
Emergent Request
good first issue
Good for newcomers
Issue Making: Level 2
Make issue(s) from an ER or Epic
Issue Making: Level 4
Create an Epic Issue, and it's Level 2 or 3 issues
P-Feature: About Us
https://www.hackforla.org/about/
P-Feature: Home page
https://www.hackforla.org/
P-Feature: Project Info and Page
A project's detail page (e.g. https://www.hackforla.org/projects/100-automations)
P-Feature: Projects page
https://www.hackforla.org/projects/
role: back end/devOps
Tasks for back-end developers
size: 1pt
Can be done in 4-6 hours
Emergent Requirement - Problem
We have sponsors and partners in different files and recently we made new files for former partners because we think we might reuse that info in a former partners section if we make a partners/sponsors page. But we are ending with too many files with different information schemas
Issue you discovered this emergent requirement in
Date discovered
Did you have to do something temporarily
Who was involved
@ExperimentsInHonesty @roslynwythe @KwameTaylor
What happens if this is not addressed
more inefficient code, etc.
Resources
Recommended Action Items
Potential solutions [draft]
What if we combined all the information into one file, and it looked something like this
File format/schema
Excerpt of two records from proposed file
New sponsors-partners.yml file
And the pages will all have code that iterates though this file looking for content to display based on whatever logic we are using. And all pages will get the order of the logos from this file (location of all applicable sponsors/partners combined with position values).
Ideally the partners/sponsors would be all in one file for ease of quarterly review, but if it's not feasible to have multiple location variables then break into individual files.
How to handle order anomalies in the file
Issues to create
- 3: Revise HTML file that creates each project page
- https://github.com/hackforla/website/blob/gh-pages/_layouts/project.html
- 4: Revise HTML file that generates the projects page and current homepage content
- https://www.hackforla.org/ & https://www.hackforla.org/projects
- Both the projects page and the homepage HTML pages (a. & b.) use this include to render the project cards, which in turn drives the filter (filter does not need any changes) https://github.com/hackforla/website/blob/gh-pages/_includes/current-projects.html
- a. projects-page https://github.com/hackforla/website/blob/gh-pages/pages/projects-page.html
- b. https://github.com/hackforla/website/blob/gh-pages/pages/index.html
The text was updated successfully, but these errors were encountered: