A Battleship inspired text based game created for the third project of Code Institute Fullstack developer program
https://hitmebabyonemoretime-2b638d3ade8e.herokuapp.com/
This game is part as one of the projects I myself am conducting during my time studying to be a Fullstack Developer at Code Insitutte. Therefore I am making a Battleship game in Python code that I'm calling "Hit Me Baby One More Time". The Player writes a suggested move and gets a response.
Since the game changes depending on the users' choices, I wanted to lay out the step-by-step logic needed to reach each ending of the game. Although there are only two outcomes there are multiple ways to get there. Now I did
This project is a Python command-line implementation of the classic Battleship game. The game is played on a 5x5 grid, where a single ship of length 3 is placed randomly either horizontally or vertically. The player has 10 attempts to guess the location of the ship and sink it by hitting all its parts.
Deployment from Heroku, since the build wont work and I can't figure out why it's failing. It wouldf also be nice with some more visual aid
In this section, you need to convince the assessor that you have conducted enough testing to legitimately believe that the site works well. Essentially, in this part you will want to go over all of your project’s features and ensure that they all work as intended, with the project providing an easy and straightforward way for the users to achieve their goals.
In addition, you should mention in this section how your project looks and works on different browsers and screen sizes.
You should also mention in this section any interesting bugs or problems you discovered during your testing, even if you haven't addressed them yet.
If this section grows too long, you may want to split it off into a separate file and link to it from here.
- HTML
- No errors were returned when passing through the official W3C validator
- CSS
- No errors were found when passing through the official (Jigsaw) validator
You will need to mention unfixed bugs and why they were not fixed. This section should include shortcomings of the frameworks or technologies used. Although time can be a big variable to consider, paucity of time and difficulty understanding implementation is not a valid reason to leave bugs unfixed.
This section should describe the process you went through to deploy the project to a hosting platform (e.g. GitHub)
- The site was deployed to GitHub pages. The steps to deploy are as follows:
- In the GitHub repository, navigate to the Settings tab
- From the source section drop-down menu, select the Master Branch
- Once the master branch has been selected, the page will be automatically refreshed with a detailed ribbon display to indicate the successful deployment.
The live link can be found here - https://hitmebabyonemoretime-2b638d3ade8e.herokuapp.com/
I would like to thank my mentor Moritz, my Swedish community member Sara for supporting me throughout the project. Huge kudos! I wouldn't have come this far without you.
I have also found it helpful to use Chat GPT as a personal tutor to explain matters I don't quite grasp just yet.
- The text for the Home page was taken from Wikipedia Article A
- Instructions on how to implement form validation on the Sign Up page was taken from Specific YouTube Tutorial
- The icons in the footer were taken from Font Awesome
- The photos used on the home and sign up page are from This Open Source site
- The images used for the gallery page were taken from this other open source site
Congratulations on completing your Readme, you have made another big stride in the direction of being a developer!
Below you will find a couple of extra tips that may be helpful when completing your project. Remember that each of these projects will become part of your final portfolio so it’s important to allow enough time to showcase your best work!
-
One of the most basic elements of keeping a healthy commit history is with the commit message. When getting started with your project, read through this article by Chris Beams on How to Write a Git Commit Message
- Make sure to keep the messages in the imperative mood
-
When naming the files in your project directory, make sure to consider meaningful naming of files, point to specific names and sections of content.
- For example, instead of naming an image used ‘image1.png’ consider naming it ‘landing_page_img.png’. This will ensure that there are clear file paths kept.
-
Do some extra research on good and bad coding practices, there are a handful of useful articles to read, consider reviewing the following list when getting started:
Getting started with your Portfolio Projects can be daunting, planning your project can make it a lot easier to tackle, take small steps to reach the final outcome and enjoy the process!