Hotel Eko

Code Institute: Milestone Project 4

Hotel Eko is a fictional retreat located in the north of Sweden. Having previously worked in the hotel industry, my idea for this project was to combine my knowledge of guest experiences with everything that I have learnt from my programming journey so far. The result is a hotel website that allows users to create their own hotel retreat personalized after their wishes for their stay, for them to be able to pay securely to confirm their reservation, to leave reviews when signed in and view blog updates from the hotel owner.

This was the last of four Milestone Projects that made up the Full Stack Web Development Program at The Code Institute. The main requirements were to build a full-stack website with the use of HTML, CSS, JavaScript, Python, Django and a relational database. Accommodating payment services was another requirement for this project and this was achieved through the use of Stripe.

If you would like to test the payment functionality of this project, please create an account and use the card number 4242 4242 4242 4242 with any address details, expiry date and CVC that you choose.

Click here to view the project live.

Table of contents

• UX
  • Main aims
  • User Stories
    • Project Stakeholders
    • New Users
    • Returning Users
    • Tablet User
  • Design Process
  • Documenting the design process
  • Database Structure
    • Designing the database
• Features
  • Existing features
  • Features left to implement
• Technologies used
• Testing
• Deployment
  • Local deployment
  • Deploying this project to Heroku
• Credits
  • Content
  • Code
  • Images
  • Acknowledgements

UX

Main aims

• To create a hotel website with a structure that is intuitive for users to navigate and a design that meets contemporary industry standards.

• To create a full stack website where both the owner of the hotel and its users could satisfy all CRUD functions, allowing them to Create, Read, Update and Delete hotel offers or bookings respectively.

• To implement Stripe payment for users looking to make hotel reservations.

• To make the website interactive, by adding JavaScript to create a positive user experience.

• To make navigation intuitive, by introducing prompts to guide the user in the right direction if lost and alert messages created with Bootstrap Toasts to confirm their actions.

• To create a design that would be fully responsive on all devices and screen sizes.

User Stories

The following User Stories helped me to create a design that would satisfy the needs of several different types of users.

Project stakeholders

• As the hotel owner, I want to create a website that inspires users to make a reservation at the hotel. Ideally, I want to encourage them to book as many features as possible – as well as a hotel room – which will increase our revenue by keeping our guests at the hotel.
• I would like the website design to emphasize our brand aims: to offer peace and calm, by drawing on the natural beauty around the hotel.
• To offer guests a platform to share reviews about their previous stays and view my welcoming thoughts prior to their arrival.

New users

• I am a user who relies on apps for all aspects of my life, from finding recipes, measuring the number of steps that I walk and monitoring the temperature of my home. Although I enjoy everything that technology gives me, I now want to learn more about this hotel in order to make a reservation to escape my apps for a weekend break!
• I have been recommended this hotel by a friend who stayed here last year. I would now like to find out more about what the hotel offers in order to decide whether I should make a reservation.

Returning users

• I have made a reservation and would like to confirm my booking number in order to share it with my friend who is joining me for the hotel stay.
• My partner and I have stayed at the hotel before. We would now like to make another reservation with the same account that I used last time.

Tablet user

• I am a user who primarily uses an iPad Pro to browse websites. I want to have a good experience on this website and view all the features in an equally aesthetic way.

Design Process

Design Process: UX Research

Before beginning the formal design process, I began by exploring other hotel, resort and retreat websites. I found it inspiring and helpful to look at the designs featured on Awwwards. and was particularly inspired by designs that drew on the atmosphere and beauty of the hotel’s local setting.

Viewing other hotel website designs led me to the following conclusions:

• I wanted to create a website that would offer information for new users to entice them to make a reservation, but also wanted to create a separate section that would only be for users who had created an account.
• The design should reflect the beauty of the Swedish mountains, which is where this fictional hotel is located. The aims of the hotel would be to offer guests the chance to unwind in a serene environment, and I wanted the design to begin the process by showing the users what kind of atmosphere they will experience.
• The website would allow users to meet several goals: by finding information about the hotel, creating a personalized retreat, making a reservation, writing a review and reading personalized notes from the owner.

The following websites were particularly useful during the research process:

• Samsara Ubud
• Fäviken Magasinet
• Arctic Bath
• Juvet
• the Arctic Hideaway

Design process: UX Design

1. Strategy plane: Having spent some time looking at websites for hotels and resorts based in Scandinavia, I was beginning to form an idea of the atmosphere that I wanted to create with this project. However, my research also led me to understand that the website would have to meet the needs of the hotel owner and potential guests alike, as all categories of users would need to be met within one well-planned design. The website would therefore have several functions: embody the brand and atmosphere of the hotel, inspire users to make a reservation, encourage them to add as many extra features to their booking as possible, successfully accept card payments to confirm bookings, allow the owner to modify their offers and provide a way for guests and the owner to share their views.

2. Scope plane: With the basic website concept and types of users in place, I began to work on how to put these into practice by considering the features. I firstly knew that the features would need to be divided between three categories: external (anonymous users), users logged in to their accounts and the hotel owner (superuser). For instance, all users should be able to view the hotel reviews, but only users logged in with their account could add, edit or remove a review. Similarly, only the owner would be able to change the services provided by the hotel. With this in mind, I decided on these rough feature ideas: login system, ability to leave reviews, a blog from the owner, the ability to customize a retreat and confirm the stay with a payment through Stripe. In order to keep the user informed throughout their experience on the website, I also decided to add a notification system, confirming a user’s actions (eg. deleting an item from their retreat).Furthermore, the website would have to meet certain content requirements to provide users with information about the hotel, including pricing, contact details and what the hotel offers.

3. Structure plane: Once I had narrowed down what features I wanted to include for the project, I began to consider how they would be presented through the structure of my design. I realized that the website would have to meet the needs of anonymous users browsing through the pages with open access, whilst barring them from viewing others that are only accessible to users logged in with their account or to the hotel owner. To create this distinction, I knew that the backend logic would have to make this possible and that it would be achieved through a changing menu bar. Certain items would be available to all users, while others would only be viewable to users who had been granted access to it. With this decision made, I wanted to make it easy for users to find what they were looking for with an intuitive navigation system so users could immediately get the information they were looking for. However, I also wanted to make the design progressive, so browsing users would enjoy the experience of learning more about the hotel at a leisurely pace. Ultimately, I decided to separate the hotel services into three categories: Stay (hotel rooms), Relax (spa treatments and yoga) and Eat (menu items). Users would be able to browse their individual details and add them to their retreat before paying to confirm their reservation. Their reservations would then be visible in their account page, with their profile details viewable there too. Blog posts from the hotel owner would also be exclusively viewable to users who had logged in to their account, and these users would also be able to navigate to the ‘about’ page to leave their review.

4. Skeleton plane: With the concept and structure in place, I began to plan the navigation route through the design. After opening the website, the users would arrive at the home page to immediately experience the atmosphere of the hotel with the hero image and introductory message welcoming them in. Below, links to the different services would encourage them to browse through the offering. By navigating to ‘About’, they would read more about the hotel, the steps needed to make a reservation and a list of all user reviews. They could then click on the ‘Stay’, ‘Relax’ and ‘Eat’ pages to discover more about the options belonging to each respective category, clicking on an individual item to learn more. From there, a user could click on ‘Reservations’ to open a dropdown menu with the choice to sign up or sign in. Once in session, they could click on the same dropdown menu to view their ‘My Details’ page and be prompted to start adding items to their retreat, or read the messages from the hotel owner. Similarly, they could choose the ‘My Retreat’ option to view what they have added, with the ability to progress to the checkout and payment page from there. They also have the choice to return to the ‘About’ page to leave a review of the hotel. Once satisfied with their time on the website, they could sign out from the menu (with a prompt to confirm) and then return to the home page.

5. Surface plane:

• The first stylistic decision I made was to really focus on the atmosphere and branding of the hotel, as this would be part of the strategy to keep the user inspired to make a reservation. However, as the website would contain so many different elements and aspects, I knew that the visual design could not interfere with a user’s ability to navigate through the each page, but rather add to the experience of doing so.
• With the idea of the type and style of design that I was after, I started a workspace on Figma and began experimenting with my wireframes for desktop, tablet and mobile devices. As with my earlier three Milestone Projects, I found it useful to have my hero image in place, as doing so prompts me to choose the tone and theme for the rest of the design. I selected an image of a woman sitting on a bridge by a mountain lake, as I thought that image would inspire users to long for the change to unwind at the hotel. From this image, I began to extract the colors I would use and created a color palette with coolors, as shown below. I chose this palette as the colors are soothing, represent nature and offer an inviting feeling to users looking for a place to relax.
• I turned to Google Fonts to select the fonts I would use for this project. I wanted to find two compatible fonts that were modern, as although the website was meant to be atmospheric, it should not come across as outdated. I found that Poiret One and Open Sans met this criteria.

Documenting the design process

Selected color palette:

Design for desktop devices (in three parts):

Design for mobile devices:

Design for tablet devices:

The entire workspace can be viewed on Figma with this link.

Database structure

As I built my project with Django, I used the built-in SQLite3 database during all development stages. When I then deployed the project to Heroku towards completion, I changed to a PostgresSQL database as that is provided by Heroku as an add-on for production. I also relied on Django’s default user model for authorization, allowing me to meet one of the project requirements of separating features by anonymous users, users in session and superusers. Further information about this feature can be found here: django.contrib.auth.models. Finally, the structure of the Checkout and Services apps were inspired by my studies with Code Institute, namely the Boutique Ado project found here: Boutique Ado.

Designing the Database

While working on the Scope and Structure planes of the design process, I also began working on the database structure. The first stage included drawing a basic idea of what the database would look like, and how data would relate to each other within it. The result of that process led to the following simplistic sketch of the idea: Handrawn database sketch.

With this complete, I had a better understanding of how I could develop the database and continued with a Microsoft Excel document. This eventually led to the structure modelled below.

Profiles App

UserProfile Model

Name	Database Key	Field Type	Validation
User	user	OneToOneField 'User'	on_delete=models.CASCADE
Phone number	default_phone_number	CharField	max_length=20, null=True, blank=True
Address Line1	default_street_address1	CharField	max_length=80, null=True, blank=True
Address Line2	default_street_address2	CharField	max_length=80, null=True, blank=True
Postcode	default_postcode	CharField	max_length=20, null=True, blank=True
Town/City	default_town_or_city	CharField	max_length=40, null=True, blank=True
County	default_county	CharField	max_length=80, null=True, blank=True
Country	default_country	CountryField	blank_label='Country', null=True, blank=True

Owner Blog App

OwnerBlog Model

Name	Database Key	Field Type	Validation
User Profile	user_profile	ForeignKey 'UserProfile'	on_delete=modals.SET_NULL, null=True, blank=True, related_name="owner_profile"
Title	title	Charfield	max_length=200
Date Added	date_added	DateTimeField	auto_now_add=True
Tought Content	thought_content	TextField	blank=True, null=True, default=""

Services App

Services Model

Name	Database Key	Field Type	Validation
Sku	sku	CharField	max_length=254, null=True, blank=True
Name	name	CharField	max_length=254
Category	category	ForeignKey 'Category'	null=True, blank=True, on_delete=models.SET_NULL
Price	price	DecimalField	max_digits=6, decimal_places=2
Description	description	TextField	max_length=900
Image	image	ImageField	null=True, blank=True
Is Stay	is_stay	BooleanField	default=False
Number of Guests	no_of_guests	IntegerField	null=True, blank=True
Has Breakfast	has_breakfast	BooleanField	null=True, blank=True
Is Relax	is_relax	BooleanField	default=False
Length	length	IntegerField	null=True, blank=True
Scents	scents	CharField	max_length=254, null=True, blank=True
Is Eat	is_eat	BooleanField	default=False
Protein	protein	CharField	max_length=254, null=True, blank=True
Number of Courses	no_of_courses	IntegerField	null=True, blank=True

Category Model

Name	Database Key	Field Type	Validation
Category	category	CharField	max_length=254

Checkout App

Checkout Model

Name	Database Key	Field Type	Validation
Order Number	order_number	CharField	max_length=32, null=False, editable=False
User Profile	user_profile	ForeignKey 'UserProfile'	on_delete=models.SET_NULL, null=True, blank=True, related_name='orders'
Full Name	full_name	CharField	max_length=50, null=False, blank=False
Email	email	EmailField	max_length=254, null=False, blank=False
Country	country	CountryField	blank_label='Country*', null=False, blank=False
Postcode	postcode	CharField	max_length=20, null=True, blank=True
Town/City	town_or_city	CharField	max_length=40, null=False, blank=False
Phone number	phone_number	CharField	max_length=20, null=False, blank=False
Street Address 1	street_address1	CharField	max_length=80, null=False, blank=False
Street Address 2	street_address2	CharField	max_length=80, null=False, blank=True
County	county	CharField	max_length=80, null=True, blank=True
Date	date	DateTimeField	auto_now_add=True
Total Price	total_price	DecimalField	max_digits=10, decimal_places=2, null=False, default=0
Original Retreat	original_retreat	TextField	null=False, blank=False, default=''
Stripe Pid	stripe_pid	CharField	max_length=254, null=False, blank=False, default=''

OrderLineItem Model

Name	Database Key	Field Type	Validation
Order	order	ForeignKey 'Order'	null=False, blank=False, on_delete=models.CASCADE, related_name='orderitems'
Service	service	ForeignKey 'Service'	null=False, blank=False, on_delete=models.PROTECT
Quantity	quantity	IntegerField	null=False, blank=False, default=0
Lineitem Total	lineitem_total	DecimalField	max_digits=8, decimal_places=2, null=False, blank=False, editable=False

User Reviews App

UserReviews Model

Name	Database Key	Field Type	Validation
User Profile	user_profile	ForeignKey 'UserProfile'	on_delete=modals.SET_NULL, null=True, blank=True, related_name="user_profile"
Service	service	ForeignKey 'Service'	on_delete=models.SET_NULL, null=True, blank=True, related_name="user_service"
Review Title	review_title	Charfield	max_length=200
Review Content	review_content	TextField	blank=True, null=True, default=""

Features

Existing Features

Consistent features across all pages

• The menu at the top of the page and footer at the bottom are consistent in design and are responsive throughout the website. However, the contents of the menu changes depending on if a user is logged in or not.
• The menu bar for users logged in features a 'Sign Out' link where the 'Sign Up' link usually is. When a user in session chooses to sign out, a toast message confirms this action and they are redirected back to the home page.
• Users with items added to their Retreat notice an additional 'Checkout' link in their navbar, allowing them direct access to go straight to checkout.
• The authentication pages (Sign In, Sign Up & Sign Out) were built with Django, and therefore include all Django's builtin features (including requesting an email for forgotten passwords.)
• Extra authentication prevents users not authenticated from access certain pages, including the checkout pages and the 'My Details' and 'My Retreat' pages.
• Each page features a 'scroll to top' arrow that becomes visible when the user has scrolled down the page.
• The active page is highlighted in a light blue colour to show the user which page they are on.
• All toast messages appear under the menu bar with the same fonts as used consistently in the theme. Depending on the type of message, the toast colour changes to reflect this message.
• Across all 'Service' pages (Stay, Relax & Eat), toast messages appear to confirm the contents of a user's retreat when they add new service items. This message also includes two buttons: 'View My Retreat' and 'Go To Checkout' to prompt users to continue towards making a reservation.
• An overlay with a spinner gif appears on all pages until the page has fully loaded.

Home

• The user begins by seeing the hero image of a woman sitting by a mountain lake.
• The user then scrolls down to see a textbox that slides upwards with an introduction to the hotel. Here a button prompts the user to 'Learn More', taking them to the About page.
• Below this, the user sees a fullwidth carousel that features buttons to the three services provided by the hotel: namely Stay, Relax and Eat.
• On smaller devices, the buttons on the carousel images are hidden, so the user only sees the images.

About

• A hero image of a couple at the retreat features at the top of this page.
• Below it, a user sees a section with the company ethos. The text slides upwards and the image changes size depending on screen width.
• The next section features user reviews. If a user is not signed in, they can only view the reviews added by other users and a prompt to sign in or register. If they have signed in, a form to add a review appears.
• Users who have signed in and have already added reviews can click on the edit or delete buttons. These open respective modals to either edit or delete the review.
• Below the reviews section, the process of making a reservation is described with three bullet points that also rise up when scrolled. The large number icons also change size and positioning to be responsive on smaller screens.
• The final section features three buttons to the hotel service pages: Stay, Relax and Eat.

Stay - Eat - Relax

• Although different pages, these three pages follow the same structure and are built with a generic 'services' template to avoid repetitive code.
• Each page is formatted to feature a hero image representing it's category with the category title at the top.
• As the user scrolls down, cards slide upwards, with one card for each service belonging to that category.
• Each card contains the service title, image and a button to learn more about it.
• Users who are signed in can add the service to their retreat directly. Anonymous users are instead faced with a prompt to sign in or sign up.
• Users are limited to adding 10 items of each service per order.

Stay - Eat - Relax: detail pages

• Users access these pages by clicking on the 'Learn More' button of the respective card.
• This page features the service image, title, all details about it and the price.
• If signed in, users can add the service to their retreat directly. Otherwise, they are prompted to sign in or sign up.
• Users are limited to adding 10 items of each service per order.

Sign In/ Sign Up

• These pages feature the same hero image as a background, reflecting the hero image on the home page.
• Ontop of the hero image, they feature the respective Sign In or Sign Up forms, prompting a user to access the parts of the website that require authentication.
• These pages can only be accessed when signed out / signed in respectively, so authorised users cannot sign in again.
• Once signed in, users are redirected to their 'My Account' overview page.

My Details

• The message at the top of the page changes depending on if the user is new to the site, if they have items already in their retreat and if they have previous orders. Users who have items in their retreat see an overview of what they have selected and see a link to prompt them to go to the My Retreat page to make changes.
• Below this setion, users can view and update their billing details. If users have made reservations in the past, a table with their booking history appears with a button to direct them to the initial 'booking success' page for that booking.
• The final section is the 'Thoughts from the Owner' blog. Here the hotel owner sees a form to submit new blog posts to the page, along with an edit and delete button that trigger their respective modals. Regular users can view the posts but cannot add, edit or delete posts from the page.

My Retreat

• This page is similar to a shopping cart on e-commerce sites: here the user can see each item in their retreat.
• All necessary information about the service item that a user has selected is included on this page, including price, quantity, subtotal and a thumbnail image that links them back to that page.
• A 'checkout' button prompts the user to confirm the reservation through payment.
• The page ends with three buttons linking users back to the services available: Stay, Relax & Eat.

Checkout

• If a user has signed in and added items to their retreat, the 'Checkout' link appears in the dropdown navigation menu.
• Otherwise, users can navigate to this page from the 'My Retreat' page through the button prompt.
• Here the user adds their details to an input form and can select whether to save the information to their profile for future reservations.
• An order summary also includes the name, price, quantity and thumbail link of each item in their retreat.
• Below these features, a user can either select the 'Return to My Retreat' link or confirm the reservation with the 'Complete Order' button.

Checkout Success

• This page is accessed by completing the checkout process. However, it can also be accessed through the 'My Details' page when clicking on more information about a previous booking. In this case, an alert message confirms that the user is viewing a previous booking and that the confirmation email was sent at the time of payment.
• The title is personalized with the user's name above the same hero image as the one featured on the authorization pages.
• Below a box contains a message from the hotel team explaining that they will be in touch to confirm a future arrival date. The order number and order details are also included below this message.

Sign Out

• This page features the same hero image as the Sign In/ Sign Up pages and can only be accessed by users that are not authenticated.
• Ontop of the hero image, a box includes a prompt that confirms that a user really does want to leave the site, with a 'Sign Out' button to do so.
• Once signed out, users are redirected back to the Home page.

Error pages: 404 and 500 pages

• Built with the same structure as the auth pages, these two pages have a large hero image with a textbox notifying the user of the issue they have come across.
• As well as the error message, they also feature buttons to take users back to the home page and include the hotel's email address if users want to get in touch.

Features Left to Implement

• As most hotel websites offer, a future feature I would like to add is the ability to select a date of stay. I decided not to include this feature at this point, as building the logic required to caclulate the number of available rooms, for instance, was beyond the scope of this project. However, this would be the first feature that I would consider working on to develop the idea further.
• Another feature would be to include a chat app to allow users to get in touch with the reception team before their arrival. This would allow them to ask any questions or make specific requests that they may have.
• Creating a members club would be a nice feature, giving points to users depending on how much they spend on each reservation. These points could be used at the hotel and would be a good way to encourage regular users to return to earn more points, as it would provide another incentive for them to do so.
• I would also consider adding different levels of authentication, so the hotel owner and the reception team would have different levels of access to the features of the site.

Technologies Used

Languages, libraries, databases, frameworks, editors, version control and deployment

• HTML5
  • The language used to create add structure and content to the website.
• CSS3
  • The language used to style the HTML5 elements according to the design wireframes and colour scheme.
• JavaScript
  • The languge used to make the app interactive.
• jQuery
  • I used the jQuery library to help write the JavaScript code used in this project.
• Python
  • The programming languaged used to create the back-end function of the site.
• Django
  • The Python web framework used to quickly take my design "from concept to completion".
• Django Crispy Forms
  • Django Crispy Forms allowed me to efficiently style the Django forms used throughout the site.
• SQLite
  • I used Django's built-in SQLite3 database during production and added data through Django's admin panel when authorised as a superuser.
• PostgresSQL
  • For deployment, I used a Postgres database offered through Heroku. I then added the same data again through Django's admin panel, with the same process that I had followed during production.
• Gunicorn
  • The Python WSGI (Web Server Gateway Interface) HTTP Server used in deployment to Heroku.
• Psycopg2
  • Psycopg2 was used to adapt Python to the PostgreSQL database.
• Bootstrap framework
  • I used Bootstrap's grid container system as I wanted to design my project with a 'mobile first' approach. I also used Bootstrap's modal, toast, navbar, carousel and accordion features to add structure to my content.
• Gitpod
  • I relied on Gitpod's dev environment to write the code for my project.
• Git Version Control
  • I used Git for Version Control to track and record changes to my code and refer back when needed.
• GitHub
  • I used GitHub as my remote repository, to push to and store the commited changes to my app from Git.
• Heroku
  • I used Heroku as a hosting platform to deploy the live version of my app.

Additional tools used

• Stripe
  • Stripe was used to add the secure payment feature to the site.
• AWS S3 Bucket
  • I used Amazon's S3 Bucket to store my static files, including local CSS & JavaScript code, favicon, gifs and image files.
• Gmail
  • Google's free email service used to send confirmation emails to users who have made reservations.
• Figma
  • Figma helped me design my project, by creating wireframes for desktop, tablet and mobile devices.
• FontAwesome
  • I relied on free FontAwesome icons for the 'back to top' and bullet point arrows used throughout the design.
• TinyPNG
  • I used TinyPNG to compress my image files to try to reduce the loading time for each page.
• Google Fonts
  • I used two complementary fonts from Google for my project: Poiret One and Open Sans.
• Gauger Fonticon Generator
  • This free Fonticon Generator allowed me to create a favicon with the font and colors used in my design.
• Animate On Scroll
  • The AOS feature was possible thanks to Michał Sajnóg's work, with his GitHub repository linked above
• W3C Markup Validation Service
  • This was a great tool throughout the project to check whether there were any errors in my HTML and CSS code (as discussed in more detail in the Testing section).
• JSHint
  • This tool helped me test my JavaScript and jQuery code (explained in more detail in the Testing section).
• PEP8 online
  • I used PEP8 to check that my Python code complied with formatting standards.

Testing

Please view the complete testing process in this separate document here.

Deployment

This project was developed using Gitpod as the chosen IDE and GitHub as a remote repository.

The deployed project can be viewed on the following link: Hotel Eko: Live Website

The project's GitHub repository can be viewed with the following link: Hotel Eko: GitHub Repository

Local deployment

If you would like to work on this project further you can clone it to your local machine using the following steps:

1. • Install the following in your IDE of choice:
     • Git (for version control)
     • pip (package installer for Python; pip3 was used at the time of production: September 2020)
     • Python3 (the programming language used to produce the backend logic of this project)
   • Make sure that you have created an account with Stripe, as this is necessary to use the payment feature of the project.
   • Either use an existing Gmail account or create a new one, then sign in and navigate to the Google Account Security page. From here, create two-step authentication by creating an App password for a Django app. Use these values when setting up your email username and password in the steps below.
2. Scroll to the top of this repository and click on the "clone or download button".
3. Decide whether you want to clone the project using HTTPS or an SSH key and do the following:
   • HTTPS: click on the checklist icon to the right of the URL to copy it
   • SSH key: first click on 'Use SSH' then click on the same icon as above
4. Return to your IDE and open a new Terminal window.
5. Change the current working directory to the location where you want the cloned directory.
6. Enter the following command and press 'Enter' to create your local clone:

git clone https://github.com/mkthewlis/hotel-eko.git

7. Install the required dependencies with the following command:

pip3 install -r requirements.txt

8. Create an env.py file and add the following, complete with your own values:

import os  
os.environ["DEVELOPMENT"] = "True"    
os.environ["SECRET_KEY"] = "<your value>"    
os.environ["STRIPE_PUBLIC_KEY"] = "<your value>"    
os.environ["STRIPE_SECRET_KEY"] = "<your value>"    
os.environ["STRIPE_WH_SECRET"] = "<your value>" 
os.environ["EMAIL_USER"] = "<your value>"
os.environ["EMAIL_PASS"] = "<your value>"

(Note: Django Secret Keys can be generated with websites such as miniwebtool.)

9. Add your env.py file to .gitignore to make sure your database information is not viewable to others and to keep your values safe.
10. To set up the Django SQLite3 tables required for this project, use the following commands:

python3 manage.py makemigrations
python3 manage.py migrate

11. With this complete, create a superuser for your project with the following command and follow the instructions in the Terminal (note: this will be necessary to add data to the hotel site once deployed locally):

python3 manage.py createsuperuser

12. Your cloned version is now ready to run locally with the following command:

python3 manage.py runserver

13. Once you run your project locally, add '/admin' to the locally deployed project's URL. From here, you can add the service categories and service items to the database. This information can be copied from each individual service's page of the deployed version of the project found on here: Hotel Eko

You can find both the source of this information and learn more about the process with the following link: Cloning a Repository

Deploying this project to Heroku

To deploy the project to Heroku, use the following steps as a continuitation from local deployment outlined above:

1. Begin by making sure that you meet the requirements outlined in Step 1 of Local Deployment as above. In addition, create a AWS S3 Bucket, as this will be necessary to store static files for deployment.
2. Create an account and sign in to Heroku. From here, created a new app with a unique name that had not already been taken (this project uses 'hotel-eko'). Set the region to the closest to you, eg. 'Europe'.
3. To use the Postgres database for deployment, select 'Heroku Postgres' as a free add-on.
4. With the app created, go to the 'Settings' tab and click on the 'Reveal Config Variables' button. From here, input the following values:

Key	Value
AWS_ACCESS_KEY_ID	your AWS bucket ID
AWS_SECRET_ACCESS_KEY	your AWS secret key
DATABASE_URL	your Heroku Postgres database url
EMAIL_HOST_PASS	your password to use your gmail account for emails
EMAIL_HOST_USER	your email address
SECRET_KEY	secret key used for your Django project
STRIPE_PUBLIC_KEY	obtained through your Stripe account
STRIPE_SECRET_KEY	obtained through your Stripe account
STRIPE_WH_SECRET	obtained through your Stripe account
USE_AWS	True

5. In Gitpod, create a requirements.txt file with the following command:

pip3 freeze --local > requirements.txt

6. Create a Procfile with the following content within (making sure that 'Procfile' was written with a capitalized 'P'):

echo web: gunicorn hotel_eko.wsgi:application > Procfile

7. As with local deployment, set up the Postgres database with the following commands:

python3 manage.py makemigrations
python3 manage.py migrate

8. Follow steps 11 to 13 from local deployment outlined above.

9. Commit these changes with the following:

git add .

git commit -m "<your commit message here>"

10. With these files committed, log in to Heroku using this command and entered your details at the prompt:

heroku login -i

11. Once logged in, link your Heroku app created above as the remote repository with this command:

heroku git:remote -a <your app name here>

12. Complete the deployment by pushing the projekt to Heroku:

git push heroku master

13. This completes the process of deploying the project to Heroku. Once deployed, continue to push all changes made to the project to Heroku with the final command listed above.

Credits

Content

The content of this website is entirely fictional and written by myself.

Code

• This project was possible thanks to following the mini-project Boutique Ado, which was part of the course material while studying with Code Institute. Although changes have been made to suit this project's aim and scope, the 'checkout', 'retreat', 'services' and 'profiles' apps were inspired by and draws upon the course material.
• The loading spinner overlay was possible by combining this tutorial https://smallenvelop.com/display-loading-icon-page-loads-completely/ with the JavaScript onload function: https://www.w3schools.com/jsref/event_onload.asp.
• Responsive thumbnail images were possible thanks to Hussain Akram's answer on this Stack Overflow post: https://stackoverflow.com/questions/27460065/how-to-make-same-sized-thumbnails/27460341
• The owner blog functionality was inspired by this Django tutorial: https://djangocentral.com/building-a-blog-application-with-django/

Images

• The images are all from Pexels, which is an open source library of photos, images and videos.
• The spinner gif was found on Preloaders.net and 'Black Hole' was selected for this project.

Acknowledgements

Thank you to the following people who helped with support and inspiration:

• My mentor Seun Owonikoko. As with my earlier three projects, Seun was a great help and support throughout the development process of this project. I've learnt a huge amount working with her and she's now become a great friend!
• The fantastic support from the Code Institute tutors, always willing to drop hints when trying to debug code.
• My classmate James Gregory for his advice when restructuring my database and being great at answering general questions.
• And as always, a big thank you to my family and friends for striking the perfect balance between giving me space and offering their support through long coding sessions.

NOTE: This project was created for educational purposes only as 'Hotel Eko' is a purely fictional hotel.