GitHub - SandraBergstrom/travel-tickr: Travel Tickr | Project Portfolio 5 - Advanced Front End (PP5) | With Travel Tickr, your travel memories are beautifully organized, easily accessible, and ready to be shared with friends, family, and the global travel community.

Travel Tickr is your ultimate destination for all things travel. Whether you're a globetrotter, an avid explorer, or simply seeking inspiration for your next adventure, Travel Tickr has got you covered. Share your travel tales, from exhilarating hikes to serene beach getaways, by uploading stunning photos accompanied by captivating stories. Connect with fellow travelers, exchange tips and recommendations, and create meaningful connections with people who share your passion for exploration. With Travel Tickr, your travel memories are beautifully organized, easily accessible, and ready to be shared with friends, family, and the global travel community.

Join Travel Tickr today and embark on a journey of discovery, connection, and endless travel inspiration.

Developer: Sandra Bergström
Live webapp
Repository
APi
API Repository

Table of contents generated with markdown-toc

User Experience

The travel memory platform is designed to cater to a diverse range of users who share a common interest in travel and creating and sharing travel memories.

Objective:

The objective of Travel Tickr is to create a travel memory platform that caters to the needs and expectations of travel enthusiasts, adventure seekers, storytellers, travel planners, and members of the travel community.

Strategy

Project Goals

Create a Travel Memory Platform: Develop a user-friendly web application that allows travelers to save and share their travel memories in the form of text and pictures. Provide a seamless experience for users to upload photos, write accompanying stories, and organize their memories into albums. Enable users to create, read, comment, and vote/like on contents.
Mapped to User Story: 14, 15, 16, 17
Build a Traveler Community: Foster a vibrant community of travelers by enabling users to connect with each other, follow fellow travelers, and like and comment on their travel experiences. Implement features that allow users to search, filter, and categorize content, enhancing the discoverability of travel stories and recommendations.
Mapped to User Story: 18, 19, 20, 21, 23, 24, 25, 50, 51, 61
Offer Seamless Travel Exploration: Implement features that enhance the travel exploration process, such as enable travelers to search and filter content based on username, popularity, date created, title, content keywords, and category. Provide search functionality that allows users to easily find relevant content and resources.
Mapped to User Story: 18, 19 27, 36
Provide a Clean and Intuitive User Interface: Design an aesthetically pleasing and user-friendly interface that reflects the essence of a travel journal. Ensure the application meets accessibility guidelines, follows UX design principles, and provides a set of user interactions that intuitively guide users through the platform. Implement responsive design to ensure the application is accessible and functional across different devices.
Mapped to all user stories.
Implement Advanced Features (if time permits): Explore the possibility of implementing additional features, such as a world map where users' travel photos are geographically marked, a trip creation functionality that provide users with destination-specific information, safety warnings, packing checklists, and reminders for passport expiration.and a bucket list feature. Automatically create photo albums when a photo has a date that is within the time line of the created trip. A bucket list feature that will allow users to add destinations and travel experiences discovered through content shared by other users to their personal list of aspirations. Provide users with the ability to curate and manage their bucket list, making it a valuable tool for planning and tracking their travel goals.
Mapped to User Story: 28, 29, 30, 31, 32

User Goals

Capture and Preserve Travel Memories: Users want to save and preserve their travel memories, including photos, stories, and experiences, in a secure and organized manner.
Share Travel Experiences: Users aim to share their travel experiences with others, allowing them to inspire and connect with fellow travelers.
Discover New Destinations: Users are interested in exploring new destinations and discovering travel recommendations and tips shared by other community members.
Connect with Fellow Travelers: Users want to connect with like-minded travelers, follow their journeys, and engage in meaningful discussions and interactions.
Plan Future Adventures: Users seek inspiration and resources to plan their future travel adventures, including destination-specific information, safety guidelines, and packing checklists.
Curate a Personal Bucket List: Users aspire to create their own bucket list of destinations and travel experiences they wish to explore in the future.
Access a User-Friendly Platform: Users expect a user-friendly and intuitive platform that is easy to navigate, provides a seamless uploading and sharing experience, and offers search and filter functionalities for finding relevant content.

Site Owner Goals

Create a Vibrant Travel Community: The site owner aims to establish a vibrant community of travelers who actively engage, connect, and share their travel experiences and recommendations.
Facilitate Content Sharing: The site owner intends to provide a platform where users can easily upload, organize, and share their travel memories, fostering a culture of storytelling and inspiration.
Drive User Engagement: The site owner wants to encourage user engagement by implementing features such as likes, comments, and following functionalities, creating an interactive and supportive community.
Enhance User Experience: The site owner strives to deliver a seamless and enjoyable user experience through an aesthetically pleasing design, intuitive navigation, and responsive interface across devices.
Promote Travel Exploration: The site owner aims to facilitate travel exploration by offering features like search, filter, categorization, and destination-specific information, allowing users to discover new destinations and plan their adventures.
Monetization Opportunities: The site owner may seek monetization opportunities through partnerships, advertising, or premium features, while ensuring they align with the overall user experience and add value to the community.

Target Audience

The target audience includes:

Travel Enthusiasts: People who have a passion for traveling and want a platform to document and share their travel experiences.
Adventure Seekers: Individuals who actively seek out new destinations, experiences, and adventures.
Storytellers: Users who enjoy sharing their travel stories and inspiring others with their experiences and recommendations.
Travel Planners: People who are in the process of planning their future trips and seek inspiration, tips, and resources.
Travel Community Members: Individuals who value being part of a vibrant community of fellow travelers and engaging in discussions and interactions.

User Requirements and Expectations

To meet the needs and expectations of the target audience, the travel memory platform should fulfill the following requirements:

User-Friendly Interface: Users expect an intuitive and easy-to-navigate interface that allows them to quickly access features and functionalities.
Seamless Content Creation: Users require a smooth and streamlined process for uploading photos, writing accompanying stories, and organizing their memories into albums.
Social Interaction: Users expect the ability to connect with other travelers, follow their journeys, like and comment on their content, and engage in discussions.
Discoverability and Search: Users want to easily search, filter, and discover relevant travel stories, destinations, and recommendations based on their interests and preferences.
Responsive Design: Users anticipate a responsive design that adapts to different devices (e.g., desktop, tablet, mobile) for seamless access and functionality.
Accessibility: Users with disabilities expect the platform to adhere to accessibility guidelines, enabling them to access and use the platform effectively.

By considering these user requirements and expectations, Travel Tickr can provide a positive and fulfilling user experience, encouraging user engagement, and fostering a vibrant community of travelers.

Back up

Scope

Features

User Account Management

Registration: Users can register for an account on the Travel Tickr platform to explore and share their travel memories.
Login: Users can log in to their Travel Tickr account using their registered email and password to access personalized features.
Logout: Users can securely log out of their Travel Tickr account to protect their account and maintain privacy.
Profile Update: Users can update their profile information to reflect their current preferences and interests.

Post Management

Create Memory Post: Users can upload a photo with accompanying text to create a memory post and share their travel experiences with others.
View Posts: Users can view and read posts shared by other users to explore and discover travel stories.
Update Posts: Users can edit or add content to their own posts to make changes or additions to their shared content.
Delete Posts: Users can remove their own posts that are no longer relevant or desired.

Interactions and Engagement

Search: Users can search for specific posts or users to discover new travel stories and connect with like-minded travelers.
Sorting: Users can sort posts based on criteria such as date, popularity, or relevance to find the most relevant and interesting content.
Like Posts: Users can like posts shared by other users to show appreciation for inspiring content.
Commenting: Users can comment on posts shared by other users to engage in discussions and interact with the travel community.
View Comments: Users can view and read comments on posts to follow conversations and opinions shared by other users.
Update Comments: Users can edit or correct their own comments to modify their shared opinions.
Delete Comments: Users can remove their own comments to retract or remove their previous statements.
Follow Users: Users can follow other users to stay updated on their travel journeys and experiences.
Site Owner Administration: Account, Post, and Comment Management: Site owners can delete user accounts, posts, and comments to maintain a safe and high-quality user environment.

Navigation:

Universal Navigation:

Every page includes a prominent navigation bar at the top, offering accessible features across the platform. Interactive elements such as posts, traveler profiles, and comments are equipped with a recognizable icon displaying three vertically aligned dots, indicating an additional dropdown menu for user interaction.

Unauthenticated Users:

Unauthenticated users are presented with a clean, intuitive navigation bar comprising a logo and links to essential pages including 'About', 'Login', and 'Sign Up'.

Authenticated Users:

Upon successful login, the navigation bar adapts to include exclusive features tailored for authenticated users. The 'Login' and 'Sign Up' links are replaced with additional options, namely 'Following', 'Bucketlist', 'Logout', and a direct link to their profile page.

Authenticated and Current Users:

For authenticated users viewing their own posts, comments, and profile, an additional layer of interactivity is provided. The recognizable icon displaying three dots reveals a dropdown menu when interacted with. This menu presents options to update or delete the corresponding content, providing users with full control over their own contributions to the platform.

Travel Memory Management

Add to Bucket List: Users will be able to add travel memories shared by others to their bucket list on the Travel Tickr platform, allowing them to save and revisit those memories later.

Future Features

Multiple Photos per Post: Users will have the ability to upload several photos to a single post on the Travel Tickr platform, enabling them to share a collection of images for a particular memory.
Create Albums: Users will be able to create albums on the Travel Tickr platform, providing them with the capability to organize and categorize their travel memories.
Trip Creation and Auto-generated Photo Album: Users will be able to create a trip on the Travel Tickr platform before embarking on a journey. An auto-generated photo album will be created, incorporating photos taken during the trip. This feature will make it convenient for users to capture and share their travel moments seamlessly.
Trip Planning Resources: Users will have access to automated packing lists and information about destinations on the Travel Tickr platform. This information will include weather forecasts, safety warnings, recommended vaccinations, and other relevant details, ensuring that users are well-prepared for their travel plans.
Word Map with Photos: Users will have the option to display a word map on their profile, with photos spread out as pins representing the locations of their travel memories on the Travel Tickr platform. This feature will allow users to visually showcase their travel experiences.

User Stories

Epic 1: User Account Management

Epic 2: Post (CRUD) Management

Epic 3: Interactions and Engagement

Epic 4: Site Owner Administration and Functionality

Epic 5: Memory Management

Epic 6: Trip Planning and Information

Back up

Structure

Database

For more detailed information about the database, kindly refer to the API's README document.

Component Architecture and Reusability

Travel Tickr is a social web application that empowers users to share travel experiences, explore new destinations, and interact with other travel enthusiasts. The app's architecture comprises several reusable components that streamline development and ensure a consistent user experience.

Core Components

Asset: This component handles the display of a spinner or an image, along with an optional message. It's used across various parts of the application, such as NotFound, PostCreateForm, PostPage, PostsPage, PopularTravelers, and TravelerPage, to provide visual feedback during data loading or to display specific images for information.
Avatar: This component displays user profile images. It's reused in the NavBar, Posts, Comments, and Traveler sections to maintain consistency and personalization across the application.
MoreDropdown: A general-purpose dropdown menu component reused in Comment, Post, and the Traveler's profile page for various context-based actions.
NavBar: A navigation bar component shown on all pages to ensure seamless navigation across the app.
NotFound: A component shown when a requested resource is not found or a certain result does not exist.

Component Pages

Authentication:

LoginForm & SignupForm: Components handling user authentication processes.

Comments:

Comment: Used to display user comments.
CommentCreateForm & CommentEditForm: Forms used for creating and editing comments.

Posts:

Post: Component to display user posts.
PostCreateForm & PostEditForm: Forms used for creating and editing posts.
PostPage: Detailed view of a specific post.
PostsPage: List view of posts. It serves as the homepage, 'Following' page where posts by followed users are shown, and the 'Bucketlist' page for displaying posts added to a user's bucketlist.

Travelers:

PopularTravelers: This component shows the most followed travelers. It's displayed on the PostsPage for both mobile and desktop views, and on the PostPage for larger screens.
Traveler: Component to show user profile details.
TravelerEditForm: Form for editing user profile.
TravelerPage: Combines the Traveler component with a list of that traveler's posts.
UsernameForm & UsernamePassword: Forms for changing username and password.

Other:

AboutPage: A component to display information about the application or any relevant context.

Component relation to User Story

Component	User Story
LoginForm	10, 11, 12
SignupForm	10
Navbar	All user stories
Avatar	13, 51
TravelerEditForm	13
PostCreateForm	14, 31
Post	15, 16, 17, 27, 36
PostEditForm	16
PostsPage	15, 19, 27
PostPage	15, 21, 22
Comment	22, 23, 24
CommentCreateForm	21
CommentEditForm	23
Traveler	50, 51
PopularTravelers	50
About Page	61
NotFound	58

The use of the React library in the Travel Tickr project has significantly contributed to enhancing the user experience. React's component-based architecture has helped create reusable components such as Asset, Avatar, MoreDropdown, NavBar, and others. These components not only ensure consistent look and feel across the application but also make the codebase more maintainable and easier to update or extend.

One particular feature where React has been instrumental is the implementation of infinite scrolling using the react-infinite-scroll-component. This feature greatly enhances user experience by loading data incrementally as the user scrolls, providing a seamless browsing experience without traditional pagination interruptions. Coupled with the axios library for asynchronous data fetching, the application is able to provide users with a non-blocking, smooth, and enjoyable browsing experience. The use of the react-router-dom also enhances navigation experience, allowing us to create a single-page application with multiple views that load instantly, providing a near-native user experience.

Back up

Skeleton

Wireframes

The wireframes provide a visual representation of the different pages and features of the web application. They serve as a blueprint for the design and layout of each page, helping to visualize the user interface and overall user experience. These wireframes were created using Balsamiq, a tool that enables quick and intuitive sketching of design ideas.

Home / Following / Bucketlist

About

Sign Up / Login

Traveler Profile

Surface

Design Choices

The design of Travel Tickr embraces a minimalistic yet warm aesthetic, capturing the joy and tranquility we often experience during our travels. The design aimed to mirror the exciting, yet peaceful experiences of exploration and global discovery. This balance was achieved by using clean lines, easy-to-read typography, and a color palette inspired by the Earth's diverse landscapes.

Colour

The color palette was carefully chosen to represent the Earth and its multitude of natural wonders. A warm beige and dark brown color symbolize the earth and ground beneath our feet, bringing warmth and a sense of stability to the design. The contrasting color of a unique blend between dark green and dark blue represents the vast oceans and the lush greenery of nature, offering a refreshing counterpoint to the earthy tones. As the palette moves skyward, a light blue color encapsulates the expanse of the sky. To capture the ethereal beauty of a sunset, a contrasting pink tone has been included, mirroring the captivating hues that dance in the sky as day transitions into night. This comprehensive color palette harmoniously encapsulates the beauty of our planet, inviting users into a visually appealing and relatable space.

Typography

The typography chosen for Travel Tickr is both Lato and Roboto, selected for their readability and clean aesthetics. Lato, a sans-serif typeface, offers a warm yet professional tone, while still embodying an unassuming simplicity. It's highly legible at small sizes, making it ideal for body text. In contrast, Roboto, with its wide letterforms and clean lines, is used for headers and subheaders to grab user attention while maintaining readability. The combination of these fonts provides an engaging user experience, with typography that's accessible and friendly, yet polished and professional.

Back up

Technologies Used

Languages

HTML
CSS
Python
JSX (JavaScript XML)

Frameworks.

React: A JavaScript library for building user interfaces. It is commonly used for creating dynamic and interactive components in web applications.
Cloudinary: A cloud-based media management platform used for storing and serving images in the Travel Tickr project.
Bootstrap and React-bootstrap: The widely used CSS framework adapted for React. Used for faster and easier web development.

Database

ElephantSQL: ElephantSQL is a PostgreSQL database as a service. It is used as the database for the Travel Tickr project, providing a reliable and scalable storage solution for the application's data.

Tools

Git: A distributed version control system used for tracking changes in the project's source code.
GitHub: A web-based hosting service for version control repositories, used for storing and managing the project's source code.
Gitpod: An online integrated development environment (IDE) used for developing and testing the Travel Tickr project.
Heroku: A cloud platform that enables deployment and hosting of web applications. Heroku was used for deploying the Travel Tickr project to a live server.
Adobe Photoshop: A professional image editing software used for advanced image manipulation and design in the Travel Tickrproject.
Balsamiq: A wireframing tool used for creating mockups and prototypes of the Travel Tickr webapp.
Google Fonts: A collection of free and open-source fonts used for typography on the Travel Tickr webapp.
Font Awesome: A library of icons used for adding scalable vector icons to the Travel Tickr webapp.

Supporting Libraries and Packages

@testing-library/jest-dom, @testing-library/react, @testing-library/user-event: These libraries are part of the Testing Library, a lightweight solution for testing JavaScript and React code.
axios: Promise-based HTTP client for making asynchronous HTTP requests in JavaScript.
jwt-decode: A small browser library that helps decoding JWTs token which are Base64Url encoded.
react-dom: Serves as the entry point to the DOM and server renderers for React.
react-infinite-scroll-component: A component to implement 'infinite scroll' in a ReactJS application.
react-router-dom: A routing library for React, it allows the application to have multiple 'pages' or views.
react-scripts: Includes scripts and configuration used by Create React App.
web-vitals: A library for measuring, reporting and analyzing web vital metrics.
@babel/plugin-proposal-private-property-in-object (Dev): A Babel plugin transforming private properties in objects.
msw (Dev): Mock Service Worker library used for mocking your REST and GraphQL APIs on both client and server side.

Back up

Methodology

The Travel Tickr project has been developed using agile principles, enabling efficient collaboration, iterative development, and effective project management. The following methodology has been employed throughout the project:

Agile Project Management with GitHub Projects

GitHub Projects has been utilized to facilitate agile project management. User stories and bugs have been organized as GitHub issues, allowing for a clear and structured approach to development. The project board in GitHub Projects serves as a Kanban board, providing an overview of the project's progress.

User Stories as GitHub Issues

Each user story has been created as a GitHub issue, capturing the desired functionality from the user's perspective. The user stories are linked to their corresponding GitHub issues, allowing easy access to the acceptance criteria, tasks, and comments associated with each user story.

Commit and Issue Linking

In the spirit of maintaining transparency and traceability in the project's development, commits associated with a user story or a bug have been linked directly to the corresponding GitHub issue. This feature of GitHub helps in providing a complete picture of the changes made to address each user story or fix each bug.

By exploring the associated issue, users can track the journey from identifying the requirement or issue to the final resolution implemented in the code. This also makes it possible to verify how each commit contributes to the overall development of the application, enhancing the comprehensibility of the project's evolution.

See example:

Github Issues Traceback

Commit List Links

Bug Tracking

Bugs encountered during the development process have also been logged as GitHub issues. These issues contain details about the specific bug, its impact, and steps to reproduce it. By linking the bugs in the README.md to their respective GitHub issues and commits, it's possible to gain insights into the bugs' resolution progress and view any additional comments.

Iterative Development Approach

The Travel Tickr project follows an iterative development approach, allowing for continuous improvement and progress while adhering to time constraints. The development process is structured into sprints, with each sprint typically lasting around 6 days.

To ensure efficient prioritization, the project employs the MuSCoW (Must have, Should have, Could have, Won't have) method. User stories critical to the app's success are categorized as Must-haves, followed by Should-haves, Could-haves, and Won't-haves. You can refer to the Kanban board to view the prioritization.

Within each sprint, a MoSCoW method is used to further prioritize user stories. They are classified as Must Do, Should Do, Could Do, and Won't Do, representing the remaining user stories that will not be included in the sprints. This approach ensures a clear differentiation between the overall project prioritization and the prioritization within each sprint, minimizing any potential confusion.

Sprint 1 (June 13th - June 18th, 2023):

Planning & Documentation

Plan Sprint (Must do)
Create and write readme.md (Must do)
Design Database Schema (Should do)
Create the wireframes (Should do)
Plan Sprint 2 (Must do)

Backend

Create a repository for the api in Github (Must do)
Start a django project in Gitpod (Must do)
Install necessary libraries and dependencies (Must do)
Create an ElephantSQL database and connect it to the API (Must do)
Connect image uploads to Cloudinary (Must do)
Add filtering (Should do)
Deploy the Djano REST API (Should do)

Create Apps and models for:

Frontend

Create a repository for the Travel Tickr (Should do)
Start a React project in Gitpod (Could do)
Test deploy project on Heroku (Could do) - Moved to next sprint
Install component library (Could do) - Moved to next sprint
Design and implement navigation bar (Could do) - Moved to next sprint
Do so navigation bar and authorization works (Could do) - Moved to next sprint
Design and implement footer (Could do) - Moved to next sprint

Sprint 1 recap: In sprint 1 I accomplished critical planning and documentation tasks, and successfully created the backend of the project including the creation of numerous apps and models. The initiation of the frontend was also embarked upon, though several elements have been postponed to the subsequent sprint.

Sprint 2 (June 19th - June 24th, 2023):

Sprint 2 recap: During sprint 2 the focus was on the further development of the frontend, with significant progress made on the implementation of the navigation bar and authorization. Additionally, several crucial user stories pertaining to user registration, login, logout, and post creation and viewing were completed, while a few tasks and user stories have been transitioned to the next sprint.

Sprint 3 (June 25th - July 1st, 2023):

Sprint 3 recap: Although I have decided to move the "Location" user story to the next sprint, we have successfully accomplished a significant portion of the planned tasks for Sprint 3.

Sprint 4 (July 2nd - July 7th, 2023):

Backlog

Sprint 4 recap: The focus was on finalizing the project and completing essential user stories. The About page, the ability to like comments, and the implementation of the location feature were successfully accomplished. Documentation, including the creation of a 404-page, and improving application deployment were also completed. While some user stories were moved to the backlog for future consideration, the application was thoroughly tested to ensure its functionality and quality.

Backlog and Subsequent Iterations

The user stories are tracked on the project board, and the "To do" column represents the backlog of user stories (also see above), indicating the tasks that will be addressed in subsequent iterations.

Please note that even though the project timeline has been accelerated, the iterative development approach allows for ongoing improvements and enhancements to meet the evolving needs of users.

For a comprehensive view of the project progress, user stories, and bug tracking, please see the Kanban board.

Back up

Bugs

Known bugs

Bug	Status
Wrong message when hover bucket as not logged in	Due to current priorities and time constraints, this bug have been moved to the backlog and will be addressed as time allows.

Fixed bugs

Here is a summary of the identified bugs along with brief descriptions of their fixes. For more detailed information, please follow the provided link to the corresponding GitHub issue, where you can track the entire process including the bug report, commits, and the steps taken to resolve the issue.

Bug	Fix
Npm start error message	Run "nvm install 16"
Can't follow some travelers	Remove the .active css dark since that was making the button all dark when pressed which looked strange.(see also backend fix in issues details)
Can't signup from other than home page	Add "/" to navlink. See details and link to commit in bug report
Filter for bucketlist not working	Add correct sorting and connection to filter
Can't run React app	See steps in issue
No posts showing on home page	Remove filter
Filter function is not working	Correct imports and typos
Redirect after signup	Correct history push
Search input in the navbar, closes the menu when clicked.	Exclude search input from click event.
Can't start react	Add react template

Back up

Testing

The testing phase indicates that the application is reliable, offering a smooth and comprehensive user experience. To view the complete testing details and results, please click here.

Back up

Deployment

The website was deployed using Heroku, following the steps below:

Create a Heroku Account: If you do not have a Heroku account already, create one. Heroku is a platform that enables developers to build, run, and operate applications entirely in the cloud.
Prepare your Application: Commit and push your code to your GitHub repository. Ensure that all necessary changes have been made and the latest version of the application is ready for deployment.
Create a New Application on Heroku: From your Heroku dashboard, create a new application. Choose an appropriate name for your application and select a region.
Set Environment Variables: Ensure the environmental variables are also added to your Heroku app settings under the Config Vars section. This is done to protect sensitive data and also to allow the services to communicate with your Heroku app.
Deployment Process: In the Heroku dashboard, navigate to the "Deploy" section of your application. Here, you will be able to link your GitHub repository to your Heroku app. Ensure that the repository and branch that contain the version of your app that you wish to deploy are selected. Finally, click "Deploy Branch" under the "Manual deploy" section.
Verify Deployment: After the deployment process completes, Heroku will provide a URL to the live application. Open this URL in your browser to ensure the application has been deployed successfully and is functioning as expected.

You can for fork the repository by following these steps:

Go to the GitHub repository
Click on Fork button in upper right hand corner
Wait for the forking process to complete. Once done, you will have a copy of the repository in your GitHub account.

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 your preferred method for cloning: HTTPS, SSH, or GitHub CLI, and click the copy button to copy the repository URL to your clipboard.
Open Git Bash (or your preferred terminal).
Change the current working directory to the location where you want the cloned directory to be created.
Type the command 'git clone' followed by the URL you copied in step 3. The command should look like this: git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY.
Press Enter to create your local clone.

Back up

Credits

I would like to express my sincere gratitude to the following resources, which have been instrumental in the development of the Travel Tickr:

Media

All images used in the webapp is from Pexels and some have been altered in Adobe Photoshop by me. The images that are uploaded belong to the users except from the user Sandra that is using images from Pexels.

Fonts

Google Fonts

Other

API to fetch countries

Back up

Acknowledgements

I would like to express my gratitude to Code Institute's project "Moments" as it served as a significant source of inspiration for my own project. I am also incredibly thankful to my mentor, Jubrile Akolade, for providing guidance and valuable feedback throughout the development process. Additionally, I extend my appreciation to Kay Welfare for being readily available, offering support, and providing assistance whenever needed. Their contributions have been essential in the successful completion of this project.

I would also like to extend my gratitude to two of the testers who have made significant contributions: Debbie and Kim. They have been instrumental in providing necessary feedback, identifying errors, and offering valuable tips. Their involvement has greatly contributed to the overall refinement of the project.

Back up

Name		Name	Last commit message	Last commit date
Latest commit History 247 Commits
.github/ISSUE_TEMPLATE		.github/ISSUE_TEMPLATE
docs		docs
public		public
src		src
.gitignore		.gitignore
Procfile		Procfile
README.md		README.md
TESTING.md		TESTING.md
package-lock.json		package-lock.json
package.json		package.json

SandraBergstrom/travel-tickr

Folders and files

Latest commit

History

Repository files navigation

Table of Content

User Experience

Objective:

Strategy

Project Goals

User Goals

Site Owner Goals

Target Audience

User Requirements and Expectations

Scope

Features

User Account Management

Post Management

Interactions and Engagement

Navigation:

Universal Navigation:

Unauthenticated Users:

Authenticated Users:

Authenticated and Current Users:

Travel Memory Management

Future Features

User Stories

Epic 1: User Account Management

Epic 2: Post (CRUD) Management

Epic 3: Interactions and Engagement

Epic 4: Site Owner Administration and Functionality

Epic 5: Memory Management

Epic 6: Trip Planning and Information

Structure

Database

Component Architecture and Reusability

Core Components

Component Pages

Component relation to User Story

Skeleton

Wireframes

Surface

Design Choices

Colour

Typography

Technologies Used

Languages

Frameworks.

Database

Tools

Supporting Libraries and Packages

Methodology

Agile Project Management with GitHub Projects

User Stories as GitHub Issues

Commit and Issue Linking

Bug Tracking

Iterative Development Approach

Sprint 1 (June 13th - June 18th, 2023):

Sprint 2 (June 19th - June 24th, 2023):

Sprint 3 (June 25th - July 1st, 2023):

Sprint 4 (July 2nd - July 7th, 2023):

Backlog

Backlog and Subsequent Iterations

Bugs

Known bugs

Fixed bugs

Testing

Deployment

Credits

Media

Fonts

Other

Acknowledgements

About

Topics

Resources

Stars

Watchers

Forks

Languages