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

Audit and reorg HfLA website wiki #2676

Open
5 of 6 tasks
Tracked by #2188 ...
SAUMILDHANKAR opened this issue Jan 9, 2022 · 135 comments
Open
5 of 6 tasks
Tracked by #2188 ...

Audit and reorg HfLA website wiki #2676

SAUMILDHANKAR opened this issue Jan 9, 2022 · 135 comments
Assignees
Labels
2 weeks inactive Complexity: Large Feature: Wiki role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 8pt Can be done in 31-48 hours

Comments

@SAUMILDHANKAR
Copy link
Member

SAUMILDHANKAR commented Jan 9, 2022

Depreciated

Overview

We need to audit and reorganize the HfLA website wiki pages so they can be moved to MkDocs

Action Items

Resources/Instructions

Changes that will need to be made

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions github-actions bot added 2 weeks inactive and removed To Update ! No update has been provided labels Jan 28, 2022
@github-actions

This comment has been minimized.

@SAUMILDHANKAR

This comment was marked as outdated.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot

This comment has been minimized.

@HackforLABot
Copy link
Contributor

@ExperimentsInHonesty, @vraer

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 13, 2025 at 11:04 PM PST.

@HackforLABot
Copy link
Contributor

@ExperimentsInHonesty, @vraer

Please add update using the below template (even if you have a pull request). Afterwards, remove the '2 weeks inactive' label and add the 'Status: Updated' label.

  1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
  2. Blockers: "Difficulties or errors encountered."
  3. Availability: "How much time will you have this week to work on this issue?"
  4. ETA: "When do you expect this issue to be completed?"
  5. Pictures (optional): "Add any pictures of the visual changes made to the site so far."

If you need help, be sure to either: 1) place your issue in the Questions/In Review column of the Project Board and ask for help at your next meeting, 2) put a "Status: Help Wanted" label on your issue and pull request, or 3) put up a request for assistance on the #hfla-site channel. Please note that including your questions in the issue comments- along with screenshots, if applicable- will help us to help you. Here and here are examples of well-formed questions.

You are receiving this comment because your last comment was before Monday, January 20, 2025 at 11:04 PM PST.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 weeks inactive Complexity: Large Feature: Wiki role: back end/devOps Tasks for back-end developers role: front end Tasks for front end developers size: 8pt Can be done in 31-48 hours
Projects
Status: In progress (actively working)
Development

No branches or pull requests

8 participants