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

homepage launch #2481

Open
8 of 23 tasks
ExperimentsInHonesty opened this issue Nov 14, 2021 · 94 comments
Open
8 of 23 tasks

homepage launch #2481

ExperimentsInHonesty opened this issue Nov 14, 2021 · 94 comments
Assignees
Labels
Complexity: Large epic P-Feature: Home page https://www.hackforla.org/ role: product Product Management size: 8pt Can be done in 31-48 hours

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Nov 14, 2021

Overview

We need to track and support the final wrap up items for the homepage launch, so that it can be completed.

Details

The homepage launch is overdue by at least a year, because we have not been actively monitoring its final issues.

Action Items

  • List all the areas that will need to be in good shape before the homepage launch
  • Identify what needs to be done to fix the area
  • Link issues that are already made
  • Make new Epic issues for each section (that has outstanding items)
    • Add a link to each epic below
  • Create the new issues and link them in the epics and below

Final tasks once issue is completed

Resources/Instructions

Issues created

Epics that need issues to be made

Epics that have all issues made


Additional links

Homepage image

Group 737

@github-actions github-actions bot added Feature Missing This label means that the issue needs to be linked to a precise feature label. role missing size: missing labels Nov 14, 2021
@ExperimentsInHonesty

This comment was marked as outdated.

@JessicaLucindaCheng

This comment was marked as resolved.

@JessicaLucindaCheng

This comment was marked as resolved.

@zzhoje

This comment was marked as outdated.

@SAUMILDHANKAR

This comment was marked as resolved.

@JessicaLucindaCheng

This comment was marked as resolved.

@ExperimentsInHonesty

This comment has been minimized.

@Rabia2219
Copy link
Member

Rabia2219 commented Feb 12, 2025

Tasks

Go through all the sub issue epics and their child issues and do the following tasks


  • Add the following check boxes under #Action Items
    - [ ] Make the issues specified
    - [ ] Link them as sub issues to this issue
    

- 1.01 Label name: P-Feature: Wins Page
    - 1.01.01 Issue Tab: [P-Feature: Wins Page](https://github.com/hackforla/website/labels/P-Feature%3A%20Wins%20Page)
    - 1.01.02 Project Board: [P-Feature: Wins Page](https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=+label%3A%22P-Feature%3A+Wins+Page%22)

  • update 1.03
    • update the text at 1.03 with the following link text, but replace WINS with the name of the page the issue is about
    - 1.03 URL of link to code search: [repo:hackforla/website NOT language:SVG NOT path:/^_data/internal/credits// WINS]()
    

  • Add WIKI resources to issue
    • Add this text to the resource section
      - 1.04 URL of WIKI page: 
      
    • Go to repo search page with repo:hackforla/website PAGE and wikis
      • Replace the word PAGE with the name of your page
      • hit the enter key
      • copy the URL, and paste it after the : on 1.04
      • hit the save button
    • Add this text under 1.04
        - 1.04.01 URL of future edits to wiki pages: https://github.com/hackforla/website/wiki/How-to-Contribute-to-the-Wiki (check this page to see if there are any other new edits in the queue.)
      

@ExperimentsInHonesty
Copy link
Member Author

  • Add this template to the bottom of the top portion of issue

Template to use

---
## Issues to write
### Must Have

### Should Have

### Could Have

---
## Relevance of the issues to the Homepage launch
### Must Have
- #[ADD ISSUE NUMBER]
   - why: 
   - status: 
      - draft
      - responsible: 
   - role: 
### Should Have
- #[ADD ISSUE NUMBER]
   - why: 
   - status: 
      - draft
      - responsible: 
   - role: 
### Could Have
- #[ADD ISSUE NUMBER]
   - why: 
   - status: 
      - draft
      - responsible: 
   - role: 

### Won't have this time
<details><summary>List of all won't have issues</summary>

- #
- #
- #
- #
- #
- #
</details> 


#### Template
```
   - why: 
   - status: 
      - draft
      - responsible: 
   - role: 
```
<details><summary>List of all issue by number</summary>

- [ ] #
- [ ] #
</details> 

Example from

@ExperimentsInHonesty
Copy link
Member Author

once the tasks in these issue comments are done

@Rabia2219
Copy link
Member

@priyanka02art
Hi Priyanka,
I confirmed with Bonnie that these task steps should be followed as is. There is not change to the instructions for 1.04, which you had asked clarification for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Complexity: Large epic P-Feature: Home page https://www.hackforla.org/ role: product Product Management size: 8pt Can be done in 31-48 hours
Projects
Status: In progress (actively working)
Development

No branches or pull requests