popcodeorg / popcodeorg/popcode
Page Title Update on New Project
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 191
- Forks
- 143
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 5
Description
Every time we create a new project the project name is Page Title. This gets a bit unruly when trying to look back through old projects if you forget to rename them. This requires you, in most cases, to either rely on the timestamp to approximate when the last time you update the project or to open the project to see its contents. This is not pressing but I do think a lot of time is wasted trying to find the desired project and discourages folks from looking back on past work.
This can be addressed via structuring curriculum in such a way to provide unique starter code with explicit and descriptive naming. However, I do think there are times where students will create new projects outside the scope of curriculum and would benefit from a system which provides a more unique naming to projects and facilitates navigating the project drop down.
Two proposals-
-
Update the page title when new project is created. Along the lines of
Page Title 1or maybe even something more unique? -
Prompt the user to change the title of the project after a certain amount of progress is made.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files, tests, or implementation entry points are identified in the issue. Start by locating project creation and project-list title handling, then resolve whether the intended behavior is automatic unique naming or a progress-based rename prompt; done means newly created projects are easier to distinguish in the project dropdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100