Create the initial resource inventory for the student website
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- content
Research direction
Create resource-inventory.md in the final project's repository. Identify official resources for Academic Support, Transportation, Housing, and Student Services; verify each URL opens the intended page and record the resource name, category, URL, a short description, and the date checked. Done when the inventory includes all four categories and explains the student need each resource addresses.
Written by the indexing model from the issue text.
Description
For my final project, I plan to build a website that helps new UIUC students find campus resources. A useful first task is to create a small resource inventory before adding content to the website.
Problem:
The website needs a consistent set of verified resources. Without an inventory, links could be duplicated, descriptions could be inconsistent, and important categories could be overlooked.
Proposed solution:
Create a resource-inventory.md file containing at least four official resources, with one each for Academic Support, Transportation, Housing, and Student Services. Each entry should include the resource name, category, official URL, a short description, and the date the link was checked.
Completion criteria:
Include one resource for each of the four categories.
Check that each link opens the intended official webpage.
Explain what student need each resource addresses.
Save the inventory in the final project's repository.
Why this is a good first issue:
This is a small, clearly defined task that does not require completed website code. It creates content that can support later design, implementation, and testing.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OREL-group/Project-Management
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
OREL-group/Project-Management#133 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
OREL-group/Project-Management#122 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OREL-group/Project-Management#114 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
OREL-group/Project-Management#113 · 1 comment ·
-
UI WireframingOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OREL-group/Project-Management#109 ·
All issues in OREL-group/Project-Management
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Mintplex-Labs/anything-llm#7133 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libnoname/noname#4626 · 1 comment ·
Maintainers usually reply within 1 day
-
chat
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 9 days
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day