Created by Ondrej Valla
View Z-V-Gallery website on Heroku.
The Z-V-Gallery (Zuzu Valla Gallery) website is my fourth ‘Milestone Project’ as part of the Full Stack Development course of The Code Institute. The main focus is on using the Django framework, an authorization and authentication system, same as using The Stripe payment system. I believe this website could be a foundation for the real online store, selling printed portraits of Zuzu Valla's work in the future.
Card number: 4242 4242 4242 4242
Use any expiration date (month/year) in the future and any CVC code.
or
4000 0025 0000 3155 Use any expiration date (month/year) in the future and any CVC code.
Thank You for understanding, Enjoy!
The Z-V-Gallery website is here for all the fans of Zuzu Valla. People have a great opportunity to purchase printed portraits of Zuzu Valla's work. Users can choose to get prints of their choice unframed, or framed in a white or black frame and delivered worldwide, straight to their door.
- The website to be user-friendly.
- The website to be visually appealing to users.
- Easy to navigate website.
- Ability to register / log in
- To be able to save my billing details in my profile for the future.
- To be able to review products.
- Easy to use payment system.
- Have a well-designed / responsive website.
- To be able to create / manage different project categories and be able to upload products for each category.
- Use MySQL and Postgres databases effectively.
- To see users' profiles, reviews, and messages in the database.
I am definitely one of the biggest Zuzu's fan and I always like to find a way to share her amazing photography with others. I came up with this idea of selling Zuzu's prints as soon as I found out, that the last project will be an online store.
Users can browse this website and find out a bit more about Zuzu and her photographs. Users can create an account to save their order history and billing details.
The target audience are people interested in photography. These can be people, who already know Zuzu Valla, same as people who dont know her yet, never seen her work and want to find out more about her and her photography. Target audience are also returning users, for instance, people who have seen Zuzu's images before and want to go a step further and purchase some of them.
The primary goal is to deliver an interactive web app with gallery portfolio style, which provides its users the ability to purchase framed or unframed pieces of printed art.
The project's goal is to show the knowledge I have learned from The Code Institute course.
As a general site user, I would like to:
- see the content of the page.
- see the content, be able to see all Prints and prices.
- view other users' reviews.
- be able to see individual projects.
- see all products added to the shopping bag.
- be able to adjust the shopping bag before checkout.
- be able to purchase prints as a guest, without creating the profile.
- get the confirmation email after the purchase.
- be able to register and create my profile.
- be able to contact the store owner, for further details.
- find out more through social media.
As a registered user, I would like to:
- be able to easily log in and log out.
- save and edit my billing details in my profile.
- see my purchase history details.
- be able to comment / review products.
- be able to edit or delete my review.
- easily change my forgotten password, if needed.
As an Admin user, I would like to:
- be able to create new project categories.
- edit or delete existing project categories.
- be able to add new products with all the details and images.
- be able to edit or delete uploaded products.
- MySQL and Postgres database to store page content effectively and safely.
- have access to all website messages, reviews, and user profiles / email addresses through my Admin login in the database.
Based on the user stories I have applied the following requirements:
- A responsive design.
- A home page with navigation menu, About section, Photography projects section, little gallery section (currently desktop view only).
- An about section on the home page where users can get more information about Zuzu Valla.
- A photography projects section on the home page, where users can see individual projects.
- A shop page where all available prints are displayed.
- An option to search the prints on the shop page.
- An option to sort prints by the individual project.
- Individual pages for each prints / products with the framing preview and the ability to choose the frame and the quantity.
- Reviews section at the bottom of each product details page with the ability to add, edit or delete the review if user is registered.
- An option to register and log in / log out.
- A profile page where registered users can add or edit billing information and see their order history details.
- Contact page with the contact form. Receiving confirmation email with the message and sender details for admin and the user.
- A shopping cart icon with relevant info is displayed at all times.
- A shopping cart page with all the items in the bag. Ability to adjust the bag.
- A checkout page with details on the shopping items.
- Secure checkout via Stripe payment.
- Email confirmation on purchase.
- An admin pages with options to Create or Edit prints / products.
- Defensive programming, e.g. confirmation on deleting, logging out, etc.
The overall look is kept the same on each page as much as possible.
- The header and footer are kept the same on each page.
- Buttons are styled in a similar way.
- The used color style is kept on each page.
The navigation is kept simple and consistent:
- The logo at the top of the page is also the link to the home page.
- Buttons can be used to navigate.
The information provided should be easily visible for the user:
- Messages(toasts) in the right top corner, are used to confirm or inform about current actions.
- Modal delete pop-ups are used as defensive programming, prompting the user if they are sure of their action.
- The user gets feedback when an error has occurred.
The website has 12 main content pages plus account registration / login pages. Each page has a header with the logo linked to the Home page, and a footer. The links in the header are shown depending on whether a user is logged in or not and if the user is the admin or not. When a user is not registered nor logged in, the register and login links are shown in the My Account section. When a user is logged in, the register and login links are hidden and a profile link and logout link are shown in My Account section. When the user is admin, an extra link for the Product Management is shown.
The footer has a section with links to social accounts and a link to the GitHub repository of this page.
- The landing page (Home page): This is the first page a user can see when they visit this website. There is a hero image with the Navigation Menu. The Navigation Menu has four link buttons, taking users to the About section, Art series section, Contact Us page, and Shop page. Below the menu, there is an Art series section.
-Art Series section: Cards of individual projects. Each card has a button (SEE PRINTS) linked to the products.html (shop page) displaying prints of selected project.
-Gallery section: Only visible on medium and larger screen resolutions. This is the section showing nine random images from Zuzu Valla's portfolio. Each image features the function of changing to black and white on hover.
-About section: Information about Zuzu Valla plus the button (CONTACT) linked to the contact.html page.
-
The products page (Shop page): The heading of this page is Prints. On this page, all available prints for sale are displayed. Each print has an image, name, project name, price, rating and for admin use only: edit button.
-
The product details page: The heading of this page is Details. On this page individual/clicked print is displayed with further details. There is the name of the print, description, three images: white-framed image, black-framed image, and un-framed image. Underneath are the edit/delete buttons for Admin use only, the price, rating, followed by the frame option selector, quantity selector and one keep shopping button, and add to bag button.
-
The product details/reviews page: This page is only displayed as a part of the product details page. This page contains heading Reviews with the count of total reviews for selected print and the current average rating. Underneath there are individual reviews. For the user who wrote the review, there is an option to edit, or delete the review.
-
The contact page: This page has a contact form, where the user can ask questions or give remarks. A confirmation email is sent to the user’s email address after submitting. Admin receives the email with the message.
-
The sign-up page:
This page has a signup form where the user can register and create an account. After registration, the user is asked to confirm their email address. After confirmation, the user is redirected to the login page. -
The sign-in page:
This page has a login form where users that have an account can log in. After login, the user will be redirected to the home page. There is a button to the register page, in case the user has no account. -
The profile page:
This is the personal page of the user. Here the user can see and edit their shipping information, see an overview of their orders (with links to each order confirmation page). -
The product management page:
On this page, the admin can add a new print / product by filling in the form. After submitting the admin is redirected to the individual page of the added print / product. -
The edit product page:
On this page, the admin can edit an existing print / product by editing the pre-filled form. After submitting the admin is redirected to the individual page of the added print / product. -
The shopping bag page: If the shopping bag is empty, the user is informed by the text, saying the shopping bag is empty and the Keep shopping button. When there are items in the bag, the user is able to see the table with product information such as Product image, name, price, whether or not framed, quantity with the update/remove option, and subtotal. At the bottom of the page, there is bag total sum, delivery charge, grand total sum, keep shopping button, and secure checkout button.
-
The checkout page:
This page has a form the user has to fill out to complete their order. The user has to provide delivery information and credit card details. After submitting the form, the user gets a confirmation email. There is also an order summary view, showing all items in the bag, subtotals and grand total including delivery charges. -
The checkout success page:
This page is shown when the payment was successful. It has an overview of the order, delivery details, and payment details.
During development, the Sqlite3 database is used. This is the default database used by Django. During production, HerokuPostgres is used in conjunction with deployment on Heroku.
Website's Header and Footer background image is downloaded from: www.teahub.io
All other images used on this website are owned by Zuzana Valla - Zuzu Valla Photography.
The website's color theme is MOSTLY White with the combination of different shades of Grey color and texts are black or "text-dark" Bootstrap class.
- rgba(0, 0, 0,) black is mostly used for text color, a part of text with the Bootstrap class of "text-dark".
- rgba(255, 255, 255,) white is used across the page to create nice, clean gallery-style background.
- rgba(181, 181, 181,) a shade of gray is used for border colors.
- rgba(233, 230, 230,) used for review cards and hovers
- Image from www.teahub.com is used
- The standard colors of Bootstrap for success, info, danger, and warning were also used.
For the headings (h1 to h6) and paragraphs, I've used 'Playfair Display' fonts and sans-serif fonts as a backup.
- To achieve a better appearance and user experience, Font Awesome icons are used in this website.
- The source: Font Awesome
The final appearance of the website varies from original wireframes, however, the main structure / idea has been followed.
- Wireframes for Home Page PC
- Wireframes for Home Page Mobile
- Wireframes for Home Page Tablet
- Wireframes for Art series section home page PC
- Wireframes for Art series section home page Mobile
- Wireframes for Art series section home page Tablet
- Wireframes for Product Details PC
- Wireframes for Product Details Mobile
- Wireframes for Product Details Tablet
-
Responsiveness on all viewports, which allows users to use the website probably on all devices.
-
Burger menu, which allows users to easily navigate the website on devices below 992px. This menu creates a cleaner and more organized look for smaller screen devices.
-
Search bar, which allows users to search prints, by entering a keyword into the search bar.
-
View by project will display only prints of selected projects.
-
Contact form is a great feature for users to get in touch with the owner of the website.
-
Delete modal as a defensive programming tool, which allows users to double confirm to delete their review.
-
Register functionality, which allows users to create an account, by filling in the registration form.
-
Login functionality, which allows users to log in to their account, by filling in the login form.
-
Logout functionality, which allows users to log out of their account, by clicking the logout button.
-
Stripe functionality, which simulates a safe environment for payments by credit card.
-
CRUD functionality (Create, Read, Update, Delete) functionality:
Create:
- Admin can create / add new prints / products.
- Users can create a review for a print / product.Read:
- All users can search and view prints / products and Reviews.Update: - Admin can edit prints / products.
- Users can edit their own review.Delete: - Admin can delete prints / products.
- Users can delete their own review.
- Register and Login by using Social media account.
- Sign up for the newsletter feature.
- Add your favorite prints to the Wishlist displayed on the profile page.
- Set the Stripe, to make the payment gate fully functional.
- HTML5 for markup.
- CSS for styling.
- JavaScript for interactivity.
- Python3 for backend programming.
- Bootstrap v4.4.1 frontend-framework with precoded code-snippets, like navigation bars, modals. Also used to help with the responsiveness of the website.
- jQuery, a javascript library for easier DOM traversing and manipulation, and shortening of the JavaScript.
- Google fonts for the fonts used on the website.
- Font Awesome for the icons used on the website.
- Django is a high-level Python web framework that encourages rapid development and clean, pragmatic design.
- Balsamiq for making the wireframes.
- Chrome Developer Tools to debug and check/test the website.
- Git for version control.
- GitHub for storing the files and version control of the website.
- PostgreSQL is used as an open-source relational cloud database after development to Heroku.
- Amazon AWS used to store static files after deployment.
- Heroku is a cloud platform for deploying the website.
- W3C Markup Validation Service to validate Html files.
- W3C CSS Validation Service to check the CSS code.
- JSHint to check the Javascript code.
- PEP8 checker to check the python code for PEP8 requirements.
- Favicon.io/ to create the favicon for the website.
- Coolors to make the color scheme.
- quickdatabasediagrams.com to create the database diagram.
- autopep8 1.6.0 to make my Python files pep8 compliant.
For testing results, please see TEST.md
Heroku is used to deploy this application, as GitHub can only deploy static websites.
The GitHub repository is linked to the Heroku App via automatic deployment. Every time commits and pushes are sent to GitHub, the Heroku App starts deploying the site.
git add .
git commit -m "commit message"
git push
-
Create a Heroku App
1. Create a new app by clicking the ‘New’ button inHeroku Dashboard. 2. Give it a unique name and set region to your nearest region. 3. Click ‘Create App’ in right top corner. 4. Click on the 'Resources' tab and in Add-ons type: postgress, then select 'Heroku Postgres'. 5. For the subscription plan, choose the free plan and click submit form.
-
Setup the Postgres Database
1. In your workspace install dj_database_url and psycopg2:pip3 install dj_database_urlandpip3 install psycopg2-binary2. Create a requirements file.pip3 freeze > requirements.txt3. Import dj_database_url in **settings.py**.import dj_database_url4. Backup the database if you're using a local database instead of fixtures.python3 manage.py dumpdata --exclude auth.permission --exclude contenttypes > db.jsonPLEASE make sure you're connected to your mysql database at this stage. 5. In Settings.py scroll down to DATABASES, comment out the default configuration and add the database url from HerokuDATABASES = { 'default': dj_database_url.parse('DATABASE_URL') }You can add the database url from Heroku's Config Vars in the Settings tab. PLEASE MAKE SURE THAT you dont commit and push The DATABASE_URL from Heroku.6. Run migrations. python3 manage.py migrate7. If you are using a local database type:python3 manage.py loaddata db.json to import the data from the mySQL database to Postgres.8. If You Are using fixtures do as following: First import the categories:python3 manage.py loaddata categoriesAnd then the products:python3 manage.py loaddata products9. If not, you can upload your files to the database later on. -
Create a superuser
- Use command: `python3 manage.py createsuperuser` - Create a username and password. -
Set up a local and remote database in settings.py
In settings.py :if 'DATABASE_URL' in os.environ: DATABASES = { 'default': dj_database_url.parse(os.environ.get('DATABASE_URL')) } else: DATABASES = { 'default': { 'ENGINE': 'django.db.backends.sqlite3', 'NAME': BASE_DIR / 'db.sqlite3', } }Therefore, when the app is running on Heroku it connects to Postgres(remote database). Otherwise, when running locally on GitPod it will connects to MYSQL(local database).
-
Install Gunicorn
Once the app is deployed to Heroku, Gunicorn will replace the development server and will act as the web server. - Use command: `pip3 install gunicorn` -
Create a Heroku 'Procfile'
The Procfile is the file that let Heroku know which file runs the app and how to run the app. 1. In the terminal type: `touch Procfile` to create 'Procfile'. 2. Inside the Procfile type:web: gunicorn <Github yourappname>.wsgi:application -
Connect to Heroku in the terminal
1. Login to your account on the Heroku website. 2. Go to account settings (click on your avatar). 3. Scroll down to the API Key section. 4. Click 'Reveal' and copy your API Key. 5. Login to Heroku via the Command lineheroku login -i6. Login with your email but use the API Key as the password. 7. Temporarily disable the collection of static files until AWS has been setup.heroku config:set DISABLE_COLLECTSTATIC=1 --app <Heroku appname>8. Add the hostnames to allowed hosts in `settings.py`.ALLOWED_HOSTS = ['<heroku appname>.herokuapp.com', 'localhost']9. Commit to GitHub.git add . git commit -m "commit message" git push10. Commit to Heroku. Make sure you have git remote initialized.heroku git:remote -a <Heroku appname>Push to Heroku.
git push heroku -
Setup automatic deployment from GitHub to Heroku.
1. In Heroku, click the Deploy tab. 2. Under 'Deployment method', Click on 'Connect to GitHub'. 3. Under 'Connect to GitHub', enter the GitHub repository name and click ‘Search’. Find Your Repository and click 'Connect'. 4. Next click the ‘Enable Automatic Deploys’ button further down.
I highly recommend to check the official documentation of AWS to get more understanding.
[Create bucket overview](https://docs.aws.amazon.com/AmazonS3/latest/userguide/create-bucket-overview.html)
1. Create an account, and login to Amazon web services.
2. Search for S3 and select it.
3. Click Create a new bucket button.
4. Give the bucket a unique name.
5. Select the region closest to you.
6. Uncheck block all public access box and acknowledge that the bucket will be public.
7. Click 'Create bucket'.
8. Set basic settings
- Click on the bucket name.
- Click the 'Properties' tab.
- Scroll down to 'Static website hosting' and click 'Edit'
- Click 'Enable', Keep 'Host a static website' selected.
Enter the default values for index and error document as shown in the example:
index.html and error.html
- Click 'Save changes'.
9. Set permissions
- Click on the 'Permissions' tab.
- Scroll down to 'CORS' and click 'Edit'.
- Past the following configuration:
[
{
"AllowedHeaders": [
"Authorization"
],
"AllowedMethods": [
"GET"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": []
}
]
- MAKE SURE YOU ARE FOLOWING JSON FORMAT!
- Click 'Save changes'
- In the Permissions tab scroll to Bucket Policy and click 'Edit'.
- NOTICE THE Bucket ARN, **You will need it in next steps**
- Click on 'Policy generator'
- In the new window that opens select 'S3 bucket policy' as the 'Type of Policy'.
- Add * to 'Principal'.
- Select 'GetObject' in 'Actions'.
- Copy your ARN from the other tab and paste it in the ARN field.
- Click 'Add Statement'.
- Click 'Generate policy'.
- Copy the policy and paste it in the Bucket Policy of the first tab.
- Add '/*' to the end of the resource key.
- Click 'Save changes'.
- Scroll down to Access control list (ACL) and click 'Edit'.
- Select 'List' for Everyone (public access) and select 'I understand...' at the bottom.
- Click 'Save changes'.
- Search term "Iam" via the main search bar and open it.
- To create a group:
- Click on 'Users groups' on the left.
- Click 'Create group' and enter a group name. E.G. manage-z-v-gallery
- Scroll down and click 'Create group'.
- To create the policy to access the bucket:
- Click on 'Policies' on the left.
- Click 'Create policy'.
- Click the JSON tab and then on 'Import managed policy'.
- Search for 'S3' in the pop up window and select 'AmazonS3FullAccess' and click 'Import'.
- Copy your ARN from previous steps (Open S3 in a new tab, click the bucket name, Permission, Bucket policy - copy the ARN)
- Paste it in the 'Resource' field in the JSON tab.
- Click 'Next: Tags', then 'Next: Review'.
- Give the policy a name and description.
- Click 'Create policy'.
- To attach the policy to the group:
- Click 'User groups' on the left.
- Click the group name.
- Click the 'Permissions' tab.
- Click 'Add permission', then click 'Attach Policies'.
- Search for the policy that you created above, select it.
- Click 'Attach policy'.
- To create a user for the group:
- Click 'Users' on the left.
- Click 'Add user' and create a username.
- Select 'Access Key - Programmatic access' and click 'Next: Permissions'.
- Select the group you want to add the user to.
- Click 'Next: Tags', then 'Next: Review' and 'Create User'.
- Download the .csv file and save it well, since it contains this users access key and secret access key and can't be downloaded again.
- To install boto3 and django-storages:
pip3 install boto3
pip3 install django-storages
- Now update the requirements.txt file:
pip3 freeze > requirements.txt
- Add storages to INSTALLED APPS in `settings.py`.
- Add the following settings to `settings.py`:
if 'USE_AWS' in os.environ:
# Cache control
AWS_S3_OBJECT_PARAMETERS = {
'Expires': 'Thu, 31 Dec 2099 20:00:00 GMT',
'CacheControl': 'max-age=94608000',
}
# Bucket Config
AWS_STORAGE_BUCKET_NAME = '<bucket name>' eg. 'z-v-gallery'
AWS_S3_REGION_NAME = '<bucket region>' eg. 'eu-west-2'
AWS_ACCESS_KEY_ID = os.environ.get('AWS_ACCESS_KEY_ID')
AWS_SECRET_ACCESS_KEY = os.environ.get('AWS_SECRET_ACCESS_KEY')
AWS_S3_CUSTOM_DOMAIN = f'{AWS_STORAGE_BUCKET_NAME}.s3.amazonaws.com'
# Static and media files
STATICFILES_STORAGE = 'custom_storages.StaticStorage'
STATICFILES_LOCATION = 'static'
DEFAULT_FILE_STORAGE = 'custom_storages.MediaStorage'
MEDIAFILES_LOCATION = 'media'
# Override static and media URLs in production
STATIC_URL = f'https://{AWS_S3_CUSTOM_DOMAIN}/{STATICFILES_LOCATION}/'
MEDIA_URL = f'https://{AWS_S3_CUSTOM_DOMAIN}/{MEDIAFILES_LOCATION}/'
Cache control' will tell the browser that it's okay to cache static files for a long time.
Bucket Config' will tell Django which bucket it should be communicating with.
Static and media files' will tell where to find static and media files.
Override static and media URLs in production' will tell which url's to use in production.
- Go to Heroku and add these values to the Config Vars in the Settings section:
- Create a custom class to tell django that in production we want to use s3 to store our static files.
- Add the folowing code to custom_storages.py in your workspace:
from django.conf import settings
from storages.backends.s3boto3 import S3Boto3Storage
class StaticStorage(S3Boto3Storage):
location = settings.STATICFILES_LOCATION
class MediaStorage(S3Boto3Storage):
location = settings.MEDIAFILES_LOCATION
- Push to GitHub.
- In your Amazon S3 bucket click 'Create folder' and name it 'media'.
- Open the folder and click 'Upload'.
- Click 'Add files' and select all your product images.
- Under 'Permissions' select 'Grant public-read access'.
- Select 'I understand...' and click 'Upload'.
- Login to Stripe or create an [account](https://dashboard.stripe.com/register).
- Click developers and then API Keys.
- Copy the public and secret key and add them to Config Vars in Heroku SETTINGS
```
STRIPE_PUBLIC_KEY = <your Stripe public key>
STRIPE_SECRET_KEY = <your Stripe secret key>
```
- In Stripe - Open the Developers section and click 'webhooks'.
- Click on 'Add endpoint'.
- Enter your heroku url and add /checkout/wh/ in the end of the url.
Example:
https://<projectname>.herokuapp.com/checkout/wh/
- Select 'receive all events' and click 'Add endpoint.
- Scroll down to 'Signing secret' and click 'Reveal signing secret'.
- Copy the signing secret and add to the Config Vars in Heroku.
A fork is basically a copy of a repository.
Forking a repository allows you to freely experiment with changes
without affecting the original project.
1. Login to GitHub and follow this link to
Z-V-Gallery Repository. 2. At the top right of the page, click on the fork button. 3. Now You should have a copy of the repository in your GitHub account.
1. Login to GitHub and follow this link to
Z-V-Gallery Repository. 2. Click on the ‘Code’ button 3. To clone using HTTPS, copy the link that is displayed by clicking on the copy icon Code Clone Icon. 4. Open a terminal in your preferred IDE (e.g. GitPod, VSCode) 5. Use the ‘git clone’ command and add the link that you copied in step 3. 6. Click the button 'Clone Repository', add the url you copied above and hit enter. 8. A clone will be created locally.
For more info on how to clone a repository click here
Clone or fork this repository
Install the requirements by typing:
pip3 install -r requirements.txt
in the terminal.
Set the environment variables:
if you're using GitPod:
- In your workspace click 'Settings'.
- In Environment Variables insert the following variables:
'DEVELOPMENT', 'True'
'SECRET_KEY', '<your secret key>' e.g. from a key generator
'STRIPE_PUBLIC_KEY', '<your stripe public key>'
'STRIPE_SECRET_KEY', '<your stripe secret key>'
'STRIPE_WH_SECRET', '<your stripe webhook secret>'
If you're using a local IDE, like VSCode:
- Create a .gitignore file in the root directory, if there isn't one.
- Open the .gitignore file and add 'env.py' to it, if it isn't in there.
- Create an env.py file and set the environment variables by adding the following text:
import os
os.environ["STRIPE_PUBLIC_KEY"] = '<your stripe public key>'
os.environ["STRIPE_SECRET_KEY"] = '<your stripe secret key>'
os.environ["STRIPE_WH_SECRET"] = '<your stripe webhook secret>'
os.environ["SECRET_KEY"] = '<your secret key>' e.g. from a key generator
os.environ["DEVELOPMENT"] = 'True'
-
Set up the STRIPE As described above.
PLEASE NOTE: It is highly recomended to use random Django Secret Key Generator to generate your secret keys.
-
Migrate the database models Check before migrations
python3 manage.py makemigrations --dry-runMake migrations
python3 manage.py makemigrationsCheck before migrate
python3 manage.py migrate --planMigrate
python3 manage.py migrate -
Load product data. Type
python3 manage.py loaddata db.jsonor Load all your data manualy. -
Create a superuser account
python3 manage.py createsuperuserAdd a username and password. -
Run the app. In the terminal, type:
python3 manage.py runserver
All Tutorial videos are such a fantastic help and inspiration. Thanks to these tutorial videos of The Boutique Ado project, I was able to create most of my project. Thank You very much!
I always find it very motivational to scroll through other student's projects. I like to browse the Code Institute Submissions page and look deeper into interesting projects. There is by my opinion a lots of great projects and ideas. Some of these project functions I have unsuccessfully tried to apply, and some I have successfully applied into my project by adapting to how I wanted the Z-V-Gallery website to appear and perform. This is a great learning curve. I am glad to be a part of this community and learn the code. I hope that also my project will inspire someone out there.
-
The HTML code for this project is HIGHLY INSPIRED by The Code Institute, Boutique Ado Project, adjusted to fit this project's needs.
-
Code Institute Submissions As mentioned above.
- Some CSS was also used after research on Google and the websites W3-SCHOOLS and Stack Over Flow
- The main JavaScript functionalities are from The Code Institute, Boutique Ado Project.
-
The Python code for this project is HIGHLY INSPIRED by The Code Institute, Boutique Ado Project, adjusted to fit this project's needs.
-
Code Institute Submissions As mentioned above.
-
The majority of images used in this website are property of Zuzu Valla Photography (my spouse) zuzuvalla.com
-
Website's Top Header and The Footer theme background from teahub.io
- Contact Form by following steps from www.twilio.com
-
My BIGGEST THANK YOU goes to my loved wife Zuzana, for all her support in the past year.
-
BIG THANK YOU for my GREAT Mentor, Nishant Kumar Nishant Kumar Github, Thank You Nishant, for the whole year of mentoring!! Danke schoen!
-
THANK YOU to my friend Dariusz Huk for answering many of my questions regarding database.
-
The Code Institute for creating this learning program.
-
Tutoring support at The Code Institute for their help and patience.
09.01.2022 T Y G