-
Simplicity and Scannability: The Tukidoo front page is designed to be simple and easy to scan. The white background and clean layout make it easy to see what's important.
-
Content Prioritization: The most important content on the front page, such as the Videos Feed and Slideshow, is placed on the top of the screen. This ensures that users see it first.
-
Visual Hierarchy: The use of different colors, sizes, and weights of text creates a visual hierarchy that guides users' attention. For example, important icons are present on the left bar.
-
Use of White Space: White space is used generously throughout the front page to make it feel less cluttered and more inviting.
-
Users are familiar with Tukidoo's interface: The designers assumed that users would be familiar with the basic layout and functionality of Tukidoo, so they didn't need to label everything explicitly.
-
Users are visually literate: The designers used visual cues, such as icons and colors, to communicate information to users.
-
Users have a high-speed internet connection: The designers assumed that users would have a high-speed internet connection so that they can easily have a video conference and video stream service available to them.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify