Welcome to KicksOnFire, your online destination for comfortable sneakers! Our modern e-commerce platform offers a curated selection of top-quality sneakers, carefully chosen to meet all your style and performance needs.
In addition to our diverse range of sneakers, we provide convenient features like account creation. By creating an account, you can easily add products to your wishlist and write reviews for your favorite items.
This business idea is close to my heart, as it lets me combine my love of fashion sneakers with my passion for using Django, HTML, CSS, JavaScript, and Python.
View live site: KicksOnFire
I used coolors.co to generate my colour palette.
This CSS file is used to define colors as needed:
- --Auburn: #9E2022;
- --White: #FEFCFC;
- --Lemon chiffon: #FFF7C0;
- --Black: #000000;
- --Eerie black #212529;
- Epic: Account Management
| User Story | Priority |
|---|---|
| As a user, I need the ability to create an account to access personalized features and save my preferences. | MUST HAVE |
| As a user, I want to log into my account to view my settings, order history, and complete purchases. | MUST HAVE |
| As a user, I want to log out to keep my account secure when I'm not using it. | MUST HAVE |
| As a user, I want the option to delete my account so I can erase my personal information. | MUST HAVE |
| As a user, I want to view my profile to see my details, manage orders, and adjust settings | MUST HAVE |
- Epic: User Registered Customers
| User Story | Priority |
|---|---|
| As a user, I want to save products to a wishlist to easily access them later. | MUST HAVE |
- Epic: Product Management (Staff)
| User Story | Priority |
|---|---|
| As a staff member, I need the ability to add new products to expand the selection available to customers. | MUST HAVE |
| As a staff member, I want to update product information to ensure accuracy and relevance. | MUST HAVE |
| As a staff member, I need the ability to remove discontinued products to maintain a clean catalog. | MUST HAVE |
- Epic: Cart and Checkout
| User Story | Priority |
|---|---|
| As a customer, I need to add products to my shopping cart to prepare for purchasing them. | MUST HAVE |
| As a customer, I want to remove items from my cart to adjust my selection before checkout. | MUST HAVE |
| As a customer, I need the ability to complete the checkout process to finalize my purchase. | MUST HAVE |
- Epic: Review System
| User Story | Priority |
|---|---|
| As a registered customer, I want to leave reviews to share my feedback and experiences with others. | MUST HAVE |
| As a registered customer, I need to edit my reviews to update or correct my feedback. | MUST HAVE |
| As a registered customer, I want the option to delete my reviews if I no longer want them to be visible. | MUST HAVE |
- Epic: Blog Management (Staff)
| User Story | Priority |
|---|---|
| As a staff member, I need to write blog posts to provide useful and engaging content for users. | MUST HAVE |
- Epic: Comment System (Registered Customers)
| User Story | Priority |
|---|---|
| As a registered customer, I want to post comments on blogs to share my thoughts and engage in discussions. | MUST HAVE |
| As a registered customer, I need to edit my comments to fix errors or revise my input. | MUST HAVE |
| As a registered customer, I want the ability to remove my comments if I change my mind about sharing them. | MUST HAVE |
For the Kicksonfire project, I decided to focus on deepening my understanding of the Stripe API and webhook handlers, which were integral to its functionality. To achieve this, I deliberately scoped the project smaller than my earlier work on FreeFido, ensuring the emphasis was on delivering a polished and functional e-commerce platform. My primary objective was to reach the Minimum Viable Product (MVP) with essential features to ensure completion within the time frame.
As the final project for my Diploma, it was important to balance ambition with practicality. The rigorous year had been both rewarding and demanding, leaving me determined to avoid overburdening myself at this critical stage. However, as I planned, I became excited about extending the eco-conscious theme of the project. This led to incorporating the innovative concept of carbon footprint as currency, aligning with emerging trends like carbon credits that could shape future commerce.
To further enrich the platform, I added features that aligned with the project’s goals:
A dedicated Articles section where the Admin could post valuable content about sustainability, climate change, and eco-conscious manufacturing. A Wishlist feature, allowing users to save premium, eco-friendly items for future purchases, reflecting their durability and value. Using Django’s Model-View-Template (MVT) framework, I was able to efficiently develop these features. The inclusion of an Admin interface made managing products and articles straightforward, resulting in a versatile and fully functional e-commerce system ready for launch.
- User Accounts: Secure account management with Django AllAuth integration.
- Payment Processing: Fully functional payment flow using Stripe.
- Articles Section: Admin-controlled posts with full CRUD capabilities to engage and educate customers.
- Product Management: Robust tools for adding, updating, and removing products with full CRUD support.
- Shopping Experience: A seamless user experience with an intuitive Bag and Checkout process.
- Responsive Design: A site designed to perform effectively across all devices.
- Business Transparency: Clear, accessible information about the business to build customer trust.
- Balsamiq was used to create basic wireframes for KicksOnFire.
he Hero Section spans the entire width of the screen and is positioned at the top of the page, above the fold (the part of the webpage that is visible without scrolling). Because of its prominent placement, I aimed to make it visually striking to capture the visitor’s attention and encourage them to explore more of the website’s content or offerings.
The navigation bar and the free delivery option for desktop orders are clearly visible over the hero image.
In the center of the navigation bar, there are menu links to the store's departments: Men's, Women's, and Accessories. Clicking any of these links will take users to the corresponding product listing page for shoes in that department.
On the right side of the navigation bar, users will see options to log in or register for an account on the website. This section also includes a cart icon that displays the user's current cart total. Additionally, once the user is logged in, they can access a profile section to manage their account details, along with a wishlist section that allows them to save products they may wish to purchase in the future.
The products page displays all available items. Users can sort by price, category.
Clicking on the image or name of a product will direct the user or shopper to the Product Details Page for that specific item. This page will feature a larger image of the product along with more detailed information about it.
The wishlist is an additional feature added to the store that was not included in the basic plan. This feature is only available to registered and logged-in users. From the Product Detail page, a user can click the "Add to Wishlist" button, adding that product to their wishlist.
Users can view a list of the products in their wishlist by clicking the "Add to Wishlist" button. This action will direct them to their wishlist page.
The wishlist page consists of a loop that renders each item in the wishlist. There is also a "Remove from Wishlist" button that users can click to remove an item from their wishlist.
Clicking the product name on the card will take the user to the Product Details page for that specific product.
Customers who are logged in can leave a review on a product. The review section can be found on the Product Details page, located below the product information.
The review form is straightforward and consists of a text area where users can write their reviews, along with a select box that allows users to rate the product on a scale from 1 to 5.
A logged-in user can edit or delete their own comment. Editing a comment will submit the new version.
The shopping bag page shows all products in the cart and their details. Users can update the quantity of products or remove items from the shopping bag.
Users can update the product quantity or remove products from the shopping bag, which will display a success toast.
The total cost, including delivery fees, is displayed. A message will notify the user if the minimum amount for free delivery has not been reached, indicating how much more is needed.
The checkout page displays a form for users to complete their purchase by providing necessary contact, shipping, and payment information.
After successfully checking out and processing payment through Stripe, the Checkout Success Page will be displayed. This page presents the order details and user information, allowing the customer to confirm that the provided information is accurate.
User clicks on my profile in the top navigation to view their order history details, which they can keep for their records.
Administrators can click on Product Management in the top navigation to access additional functionality, allowing them to add a new product to the store or database from the front end. This feature can be accessed by selecting Profile Management.
This makes it easy for store owners to add new products by filling out the required product information and clicking "Add Product."
Admin Django Backend Panel - Admin Only
KicksOnFire’s footer includes the company’s social media connections. The Facebook page for KicksOnFire opens in a new tab, while my LinkedIn and GitHub profiles are also linked and will open in new tabs. The “Contact Us” button opens a modal for any inquiries. Additionally about, there is a section about the KicksOnFire story.
Users can sign up for weekly emails through the newsletter subscription form with all the information they need about KicksOnFire.
Underneath, you'll find the store’s Privacy Policy and Terms and Conditions. The Privacy Policy opens in a new tab, while the Terms and Conditions are displayed on a new KicksOnFire webpage, thanks to Termly's pasteable HTML block, after you provide the relevant business details.
Customers can contact us with any queries they may have. Once they submit their name, email, and message, they will be directed to a thank you page that includes a ‘Return Home’ button. The Admin can view the messages in their connected business email service and respond directly to the customers.
Enable shoppers to create an account on the website.
The sign-out page is designed for security. Would you like to log out of your account securely?
"404 Not Found” is displayed when a user tries to access a page that doesn’t exist. This message suggests that the user may have mistyped the URL or clicked on a broken link. The page includes a button to redirect users back to the homepage.
HTTP error code 500 indicates an internal server error, which means there is a problem with the website's server.
Kicksofire’s e-commerce store is performing well, but the team is committed to enhancing the shopping experience even further. An exciting update will involve revamping the hero images on the homepage to feature a diverse range of products for men, women, and kids. Each hero image will spotlight popular items—such as sleek men's sneakers, trendy women's footwear, and stylish kids' shoes—while also introducing improved sizing options like 6, 7, 8, and 9 for kids' products. These changes aim to create a visually engaging and user-friendly shopping journey for every customer.
These changes are part of our ongoing effort to create a more user-friendly and visually engaging shopping journey. By broadening product representation and offering more precise sizing options, we aim to cater to a wider demographic and provide a tailored experience for all customers, making it easier for them to find products that match their personal style and needs.
In addition to these visual enhancements, the team is also working on improving site navigation and product filtering options to make it even easier for customers to discover the perfect items, quickly and efficiently. The goal is to build a seamless and enjoyable experience from the moment customers land on the homepage to the final stages of checkout.
used to generate README and TESTING templates.
used for version control. (
git add,git commit,git push)used for secure online code storage.
used as a cloud-based IDE for development.
used for the main site content.
used for the main site design and layout.
used for user interaction on the site.
used for user interaction on the site.
used as the back-end programming language.
used for hosting the deployed back-end site.
used as the front-end CSS framework for modern responsiveness and pre-built components.
used as the Python framework for the site.
used as the Postgres database from Code Institute.
used for online static file storage.
used for serving static files with Heroku.
used for online secure payments of ecommerce products/services.
used for sending emails in my application.
used for sending newsletter subscriptions.
used for online static file storage.
used for creating wireframes.
used for creating wireframes.
used for the icons.
used to help debug, troubleshoot, and explain things.
A couple recommendations for building free ERDs:
I have used pygraphviz and django-extensions to auto-generate an ERD.
The steps taken were as follows:
- In the terminal:
sudo apt update - then:
sudo apt-get install python3-dev graphviz libgraphviz-dev pkg-config - then type
Yto proceed - then:
pip3 install django-extensions pygraphviz - in my
settings.pyfile, I added the following to myINSTALLED_APPS:
INSTALLED_APPS = [
...
'django_extensions',
...
]- back in the terminal:
python3 manage.py graph_models -a -o erd.png - dragged the new
erd.pngfile into mydocumentation/folder - removed
'django_extensions',from myINSTALLED_APPS - finally, in the terminal:
pip3 uninstall django-extensions pygraphviz -y
Entity Relationship Diagrams (ERDs) assist in visualizing the structure of a database.
Kicksonfree Agile planning methodologies to effectively manage the project. GitHub Projects provided an ideal platform for organizing tasks, enabling the creation of issues, boards, and milestones to streamline workflow.
GitHub Projects served as an Agile tool for this project. It isn't a specialized tool, but with the right tags and project creation/issue assignments, it can be made to work.
GitHub Issues served as an another Agile tool. There, I used my own User Story Template to manage user stories.
To effectively manage task priorities for the Kicksonfire project, I applied the MoSCoW Prioritization method. This approach categorizes tasks based on their importance and urgency:
Must Have: Essential features that are guaranteed to be delivered. Should Have: Features that add significant value but are not critical for immediate delivery.
This site sells goods to individual customers, and therefore follows a Business to Customer model.
It is of the simplest B2C forms, as it focuses on individual transactions, and doesn't need anything
such as monthly/annual subscriptions.
It is still in its early development stages, although it already has a newsletter, and links for social media marketing.
Social media can potentially build a community of users around the business, and boost site visitor numbers, especially when using larger platforms such a Facebook.
A newsletter list can be used by the business to send regular messages to site users. For example, what items are on special offer, new items in stock, updates to business hours, notifications of events, and much more!
I've identified some appropriate keywords to align with my site, that should help users when searching online to find my page easily from a search engine. This included a series of the following keyword types
- Short-tail (head terms) keywords
- Long-tail keywords
I also played around with Word Tracker a bit to check the frequency of some of my site's primary keywords (only until the free trial expired).
I've used XML-Sitemaps to generate a sitemap.xml file. This was generated using my deployed site URL: https://kicks-on-fire-5b791a86ef14.herokuapp.com
After it finished crawling the entire site, it created a sitemap.xml which I've downloaded and included in the repository.
I've created the robots.txt file at the root-level. Inside, I've included the default settings:
User-agent: *
Disallow:
Sitemap: https://kicks-on-fire-5b791a86ef14.herokuapp.com/sitemap.xml
Further links for future implementation:
- Google search console
- Creating and submitting a sitemap
- Managing your sitemaps and using sitemaps reports
- Testing the robots.txt file
Creating a strong social media presence and linking it to the business website can effectively drive sales. Leveraging popular platforms with a large user base, such as Facebook, can significantly increase site traffic. E-commerce thrives on Facebook through consistent posts, engaging user interactions, polls to gather feedback, and competitions designed to attract both new and returning customers.
I've created a mockup Facebook business account using the Balsamiq template provided by Code Institute.
KicksOnFire Facebook Business Page.
In the footer section of the main page a newsletter sign up section is included. Therefore the MailChimp Newsletter subscription service is used. The sign up is easy and completely optional.
*MailChimp Newsletter.
Sign up message successful
The email has been added to the subscribers contact list in Mailchimp.
Note
For all testing, please refer to the TESTING.md file.
The live deployed application can be found deployed on Heroku.
This project uses a Code Institute PostgreSQL Database.
To obtain my own Postgres Database from Code Institute, I followed these steps:
- Signed-in to the CI LMS using my email address.
- An email was sent to me with my new Postgres Database.
Caution
- PostgreSQL databases by Code Institute are only available to CI Students.
- You must acquire your own PostgreSQL database through some other method if you plan to clone/fork this repository.
- Code Institute students are allowed a maximum of 8 databases.
- Databases are subject to deletion after 18 months.
This project uses AWS to store media and static files online, due to the fact that Heroku doesn't persist this type of data.
Once you've created an AWS account and logged-in, follow these series of steps to get your project connected. Make sure you're on the AWS Management Console page.
-
Search for S3.
-
Create a new bucket, give it a name (matching your Heroku app name), and choose the region closest to you.
-
Uncheck Block all public access, and acknowledge that the bucket will be public (required for it to work on Heroku).
-
From Object Ownership, make sure to have ACLs enabled, and Bucket owner preferred selected.
-
From the Properties tab, turn on static website hosting, and type
index.htmlanderror.htmlin their respective fields, then click Save. -
From the Permissions tab, paste in the following CORS configuration:
[ { "AllowedHeaders": [ "Authorization" ], "AllowedMethods": [ "GET" ], "AllowedOrigins": [ "*" ], "ExposeHeaders": [] } ] -
Copy your ARN string.
-
From the Bucket Policy tab, select the Policy Generator link, and use the following steps:
-
Policy Type: S3 Bucket Policy
-
Effect: Allow
-
Principal:
* -
Actions: GetObject
-
Amazon Resource Name (ARN): paste-your-ARN-here
-
Click Add Statement
-
Click Generate Policy
-
Copy the entire Policy, and paste it into the Bucket Policy Editor
{ "Id": "Policy1234567890", "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1234567890", "Action": [ "s3:GetObject" ], "Effect": "Allow", "Resource": "arn:aws:s3:::your-bucket-name/*" "Principal": "*", } ] } -
Before you click "Save", add
/*to the end of the Resource key in the Bucket Policy Editor (like above). -
Click Save.
-
-
From the Access Control List (ACL) section, click "Edit" and enable List for Everyone (public access), and accept the warning box.
- If the edit button is disabled, you need to change the Object Ownership section above to ACLs enabled (mentioned above).
Back on the AWS Services Menu, search for and open IAM (Identity and Access Management). Once on the IAM page, follow these steps:
- From User Groups, click Create New Group.
- Suggested Name:
group-kicksonfire(group + the project name)
- Suggested Name:
- Tags are optional, but you must click it to get to the review policy page.
- From User Groups, select your newly created group, and go to the Permissions tab.
- Open the Add Permissions dropdown, and click Attach Policies.
- Select the policy, then click Add Permissions at the bottom when finished.
- From the JSON tab, select the Import Managed Policy link.
-
Search for S3, select the
AmazonS3FullAccesspolicy, and then Import. -
You'll need your ARN from the S3 Bucket copied again, which is pasted into "Resources" key on the Policy.
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:*", "Resource": [ "arn:aws:s3:::your-bucket-name", "arn:aws:s3:::your-bucket-name/*" ] } ] } -
Click Review Policy.
-
Suggested Name:
policy-kicksonfire(policy + the project name) -
Provide a description:
- "Access to S3 Bucket for kicksonfire static files."
-
Click Create Policy.
-
- From User Groups, click your "group-kicksonfire".
- Click Attach Policy.
- Search for the policy you've just created ("policy-kicksonfire") and select it, then Attach Policy.
- From User Groups, click Add User.
- Suggested Name:
user-kicksonfire(user + the project name)
- Suggested Name:
- For "Select AWS Access Type", select Programmatic Access.
- Select the group to add your new user to:
group-kicksonfire - Tags are optional, but you must click it to get to the review user page.
- Click Create User once done.
- You should see a button to Download .csv, so click it to save a copy on your system.
- IMPORTANT: once you pass this page, you cannot come back to download it again, so do it immediately!
- This contains the user's Access key ID and Secret access key.
AWS_ACCESS_KEY_ID= Access key IDAWS_SECRET_ACCESS_KEY= Secret access key
- If Heroku Config Vars has
DISABLE_COLLECTSTATICstill, this can be removed now, so that AWS will handle the static files. - Back within S3, create a new folder called:
media. - Select any existing media images for your project to prepare them for being uploaded into the new folder.
- Under Manage Public Permissions, select Grant public read access to this object(s).
- No further settings are required, so click Upload.
Select AWS Region
This project uses Stripe to handle the ecommerce payments.
Once you've created a Stripe account and logged-in, follow these series of steps to get your project connected.
- From your Stripe dashboard, click to expand the "Get your test API keys".
- You'll have two keys here:
STRIPE_PUBLIC_KEY= Publishable Key (starts with pk)STRIPE_SECRET_KEY= Secret Key (starts with sk)
As a backup, in case users prematurely close the purchase-order page during payment, we can include Stripe Webhooks.
- From your Stripe dashboard, click Developers, and select Webhooks.
- From there, click Add Endpoint.
https://kicks-on-fire-5b791a86ef14.herokuapp.com/checkout/wh/
- Click receive all events.
- Click Add Endpoint to complete the process.
- You'll have a new key here:
STRIPE_WH_SECRET= Signing Secret (Wehbook) Key (starts with wh)
Stripe Webhook/Payment Successful
This project uses Gmail to handle sending emails to users for account verification and purchase order confirmations.
Once you've created a Gmail (Google) account and logged-in, follow these series of steps to get your project connected.
- Click on the Account Settings (cog icon) in the top-right corner of Gmail.
- Click on the Accounts and Import tab.
- Within the section called "Change account settings", click on the link for Other Google Account settings.
- From this new page, select Security on the left.
- Select 2-Step Verification to turn it on. (verify your password and account)
- Once verified, select Turn On for 2FA.
- Navigate back to the Security page, and you'll see a new option called App passwords.
- This might prompt you once again to confirm your password and account.
- Select Mail for the app type.
- Select Other (Custom name) for the device type.
- Any custom name, such as "Django" or KicksOnFire
- You'll be provided with a 16-character password (API key).
- Save this somewhere locally, as you cannot access this key again later!
EMAIL_HOST_PASS= user's 16-character API keyEMAIL_HOST_USER= user's own personal Gmail email address
This project uses Heroku, a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud.
Deployment steps are as follows, after account setup:
- Select New in the top-right corner of your Heroku Dashboard, and select Create new app from the dropdown menu.
- Your app name must be unique, and then choose a region closest to you (EU or USA), and finally, select Create App.
- From the new app Settings, click Reveal Config Vars, and set your environment variables.
Important
This is a sample only; you would replace the values with your own if cloning/forking my repository.
| Key | Value |
|---|---|
AWS_ACCESS_KEY_ID |
user's own value |
AWS_SECRET_ACCESS_KEY |
user's own value |
DATABASE_URL |
user's own value |
DISABLE_COLLECTSTATIC |
1 (this is temporary, and can be removed for the final deployment) |
EMAIL_HOST_PASS |
user's own value |
EMAIL_HOST_USER |
user's own value |
SECRET_KEY |
user's own value |
STRIPE_PUBLIC_KEY |
user's own value |
STRIPE_SECRET_KEY |
user's own value |
STRIPE_WH_SECRET |
user's own value |
USE_AWS |
True |
Heroku needs three additional files in order to deploy properly.
- requirements.txt
- Procfile
- runtime.txt
You can install this project's requirements (where applicable) using:
pip3 install -r requirements.txt
If you have your own packages that have been installed, then the requirements file needs updated using:
pip3 freeze --local > requirements.txt
The Procfile can be created with the following command:
echo web: gunicorn app_name.wsgi > Procfile- replace app_name with the name of your primary Django app name; the folder where settings.py is located
The runtime.txt file needs to know which Python version you're using:
- type:
python3 --versionin the terminal. - in the runtime.txt file, add your Python version:
python-3.9.19
For Heroku deployment, follow these steps to connect your own GitHub repository to the newly created app:
Either:
- Select Automatic Deployment from the Heroku app.
Or:
- In the Terminal/CLI, connect to Heroku using this command:
heroku login -i - Set the remote for Heroku:
heroku git:remote -a app_name(replace app_name with your app name) - After performing the standard Git
add,commit, andpushto GitHub, you can now type:git push heroku main
The project should now be connected and deployed to Heroku!
This project can be cloned or forked in order to make a local copy on your own system.
For either method, you will need to install any applicable packages found within the requirements.txt file.
pip3 install -r requirements.txt.
You will need to create a new file called env.py at the root-level,
and include the same environment variables listed above from the Heroku deployment steps.
Important
This is a sample only; you would replace the values with your own if cloning/forking my repository.
Sample env.py file:
import os
os.environ.setdefault("AWS_ACCESS_KEY_ID", "user's own value")
os.environ.setdefault("AWS_SECRET_ACCESS_KEY", "user's own value")
os.environ.setdefault("DATABASE_URL", "user's own value")
os.environ.setdefault("EMAIL_HOST_PASS", "user's own value")
os.environ.setdefault("EMAIL_HOST_USER", "user's own value")
os.environ.setdefault("SECRET_KEY", "user's own value")
os.environ.setdefault("STRIPE_PUBLIC_KEY", "user's own value")
os.environ.setdefault("STRIPE_SECRET_KEY", "user's own value")
os.environ.setdefault("STRIPE_WH_SECRET", "user's own value")
# local environment only (do not include these in production/deployment!)
os.environ.setdefault("DEBUG", "True")Once the project is cloned or forked, in order to run it locally, you'll need to follow these steps:
- Start the Django app:
python3 manage.py runserver - Stop the app once it's loaded:
CTRL+Cor⌘+C(Mac) - Make any necessary migrations:
python3 manage.py makemigrations - Migrate the data to the database:
python3 manage.py migrate - Create a superuser:
python3 manage.py createsuperuser - Load fixtures (if applicable):
python3 manage.py loaddata file-name.json(repeat for each file) - Everything should be ready now, so run the Django app again:
python3 manage.py runserver
If you'd like to backup your database models, use the following command for each model you'd like to create a fixture for:
python3 manage.py dumpdata your-model > your-model.json- repeat this action for each model you wish to backup
You can clone the repository by following these steps:
- Go to the GitHub repository
- Locate the Code button above the list of files and click it
- Select if you prefer to clone using HTTPS, SSH, or GitHub CLI and click the copy button to copy the URL to your clipboard
- Open Git Bash or Terminal
- Change the current working directory to the one where you want the cloned directory
- In your IDE Terminal, type the following command to clone my repository:
git clone https://github.com/ciarangriffin93/KicksOnFire.git
- Press Enter to create your local clone.
Alternatively, if using Gitpod, you can click below to create your own workspace using this repository.
Please note that in order to directly open the project in Gitpod, you need to have the browser extension installed. A tutorial on how to do that can be found here.
By forking the GitHub Repository, we make a copy of the original repository on our GitHub account to view and/or make changes without affecting the original owner's repository. You can fork this repository by using the following steps:
- Log in to GitHub and locate the GitHub Repository
- At the top of the Repository (not top of page) just above the "Settings" Button on the menu, locate the "Fork" Button.
- Once clicked, you should now have a copy of the original repository in your own GitHub account!
| Source | Location | Notes |
|---|---|---|
| strftime | CRUD functionality | helpful tool to format date/time from string |
| WhiteNoise | entire site | hosting static files on Heroku temporarily |
| Code Institute | entire site | This is from code institute to learn how to create the Boutique Ado walkthrough projec |
| Git Commit | entire site | I learn how to writing better commit messages |
| Source | Location | Type | Notes |
|---|---|---|---|
| Pexels | entire site | image | favicon on all pages |
| Pixabay | gallery page | image | group of photos for gallery |
| Chat GPT | Chatgpt page | image | was used to produce create content for the Articles section, prompted by various discussion points regarding climate change and current issues. |
- I would like to thank my Code Institute mentor, Tim Nelson and Rory Sheridan for his support throughout the development of this project.
- I would like to thank the Code Institute tutor team for their assistance with troubleshooting and debugging some project issues.
- I would like to thank the Code Institute Slack community and Deaf group for the moral support; it kept me going during periods of self doubt and impostor syndrome.
- I would like to thank to my family for their patience, support, and understanding.