issues
search
halfpintutopia
/
whack-a-marmot
No marmots were hurt in the making of this JavaScript game
2
stars
2
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Bugfixes for re-submission
#66
halfpintutopia
closed
1 year ago
0
No feedback on input field for username
#65
halfpintutopia
closed
1 year ago
0
Waking the marmots
#64
halfpintutopia
closed
1 year ago
0
Marmot goes down fast
#63
halfpintutopia
closed
1 year ago
1
Marmot stays up
#62
halfpintutopia
closed
1 year ago
1
Marmot hits
#61
halfpintutopia
closed
1 year ago
1
Multiple hits
#60
halfpintutopia
closed
1 year ago
0
Game start
#59
halfpintutopia
closed
1 year ago
0
Marmots overlay
#58
halfpintutopia
closed
1 year ago
0
Buttons
#57
halfpintutopia
closed
1 year ago
0
How many marmots can you whack
#56
halfpintutopia
closed
1 year ago
0
Whack the marmot
#55
halfpintutopia
closed
1 year ago
0
See the marmot
#54
halfpintutopia
closed
1 year ago
0
Difficulty
#53
halfpintutopia
closed
1 year ago
0
Dark Mode
#52
halfpintutopia
closed
1 year ago
0
Refreshing page
#51
halfpintutopia
closed
1 year ago
0
Top left marmot
#50
halfpintutopia
closed
1 year ago
0
Hitting the marmot
#49
halfpintutopia
closed
1 year ago
1
Left clicking on first instruction page
#48
halfpintutopia
closed
1 year ago
1
Show hills
#47
halfpintutopia
opened
1 year ago
1
Test a front-end web application through the development, implementation and deployment stages
#46
halfpintutopia
closed
1 year ago
0
Design a web application that lets the user initiate and control actions and gives feedback
#45
halfpintutopia
closed
1 year ago
0
Document the deployment procedure in a section in a README file, written using consistent and effective markdown formatting that is well-structured, easy to follow, and has few grammatical errors
#44
halfpintutopia
closed
1 year ago
0
Present a clear rationale for the development of the project, in the README, - Key project goals, target audience
#43
halfpintutopia
closed
1 year ago
0
Commit often for each feature/fix, ensuring that commits are small, well-defined and have clear, descriptive messages
#42
halfpintutopia
closed
1 year ago
0
Document any bugs found and their fixes and explanation of any bugs that are left unfixed.
#41
halfpintutopia
closed
1 year ago
0
Implement a website that provides an excellent solution to the key project goals, demands and expectations.
#40
halfpintutopia
closed
1 year ago
0
Implement a web application whose purpose is immediately evident to a new user
#39
halfpintutopia
closed
1 year ago
0
Design a website with a flow of information layout and interaction feedback that is clear and unambiguous
#38
halfpintutopia
closed
1 year ago
0
Organise code and assets files in directories by file type.
#37
halfpintutopia
closed
1 year ago
0
Write code that does not generate internal errors on the page or in the console due to user actions.
#36
halfpintutopia
closed
1 year ago
0
Implement appropriate working functionality for all project requirements.
#35
halfpintutopia
closed
1 year ago
0
Write code that intelligently handles empty or invalid input data.
#34
halfpintutopia
closed
1 year ago
0
Write JavaScript functions that correctly implement compound statements, such as if conditions and loops.
#33
halfpintutopia
closed
1 year ago
0
Use consistent and effective markdown formatting that is well-structured, easy to follow, and has few grammatical errors, when writing a README file.
#32
halfpintutopia
closed
1 year ago
0
Group files in directories by file type (e.g. an assets directory will contain all static files and may be organised into sub-directories such as CSS, images, etc.)
#31
halfpintutopia
closed
1 year ago
0
Name files consistently and descriptively, without spaces or capitalisation to allow for cross-platform compatibility.
#30
halfpintutopia
closed
1 year ago
0
Write code that meets at least minimum standards for readability (consistent indentation, blank lines only appear individually or, at most, in pairs)
#29
halfpintutopia
closed
1 year ago
0
Place JavaScript code in external files linked to the HTML page just above the closing body tag.
#28
halfpintutopia
closed
1 year ago
0
Place CSS code in external files linked to the HTML page in the HEAD element.
#27
halfpintutopia
closed
1 year ago
0
Organise HTML, CSS and JavaScript code into well-defined and commented sections
#26
halfpintutopia
closed
1 year ago
0
Clearly separate and identify code written for the website and code from external sources (e.g. libraries or tutorials)
#25
halfpintutopia
closed
1 year ago
0
Attribute all code from external sources to its original source via comments above the code and (for larger dependencies) in the README.
#24
halfpintutopia
closed
1 year ago
0
Insert screenshots of the project features, give a brief description of what each feature does and explain its value to the user.
#23
halfpintutopia
closed
1 year ago
0
Write a README.md file for the web application that explains its purpose, the value that it provides to its users, and the deployment procedure.
#22
halfpintutopia
closed
1 year ago
0
Ensure that there are no broken internal links
#21
halfpintutopia
closed
1 year ago
0
Remove commented-out code before pushing final changes to version control and deploying.
#20
halfpintutopia
closed
1 year ago
0
Use Git & GitHub for version control of an interactive web application up to deployment.
#19
halfpintutopia
closed
1 year ago
0
Deploy a final version of the code to a cloud-based hosting platform (e.g. GitHub Pages) and test to ensure it matches the development version
#18
halfpintutopia
closed
1 year ago
0
If used, implement clear navigation to allow users to find resources on the site intuitively.
#17
halfpintutopia
closed
1 year ago
0
Next