Book Image

A Blueprint for Production-Ready Web Applications

By : Dr. Philip Jones
Book Image

A Blueprint for Production-Ready Web Applications

By: Dr. Philip Jones

Overview of this book

A Blueprint for Production-Ready Web Applications will help you expand upon your coding knowledge and teach you how to create a complete web application. Unlike other guides that focus solely on a singular technology or process, this book shows you how to combine different technologies and processes as needed to meet industry standards. You’ll begin by learning how to set up your development environment, and use Quart and React to create the backend and frontend, respectively. This book then helps you get to grips with managing and validating accounts, structuring relational tables, and creating forms to manage data. As you progress through the chapters, you’ll gain a comprehensive understanding of web application development by creating a to-do app, which can be used as a base for your future projects. Finally, you’ll find out how to deploy and monitor your application, along with discovering advanced concepts such as managing database migrations and adding multifactor authentication. By the end of this web development book, you’ll be able to apply the lessons and industry best practices that you’ve learned to both your personal and work projects, allowing you to further develop your coding portfolio.
Table of Contents (13 chapters)
Part 1 Setting Up Our System
Part 2 Building a To-Do App
Part 3 Releasing a Production-Ready App

Enabling data entry

Users of our app will need to enter their email and password to log in, and then a description, due date, and completion for their to-do tasks. These fields will need to be grouped into forms; building forms with a good user experience takes a lot of effort as the form must be validated and the touched state, error state, and focused state must be managed for each field and the form itself.

Form input states

A form input box will need to display a variety of different states to help the user understand how it is used and when there is an issue. To start, the input will be in an empty state with no value and no error. This is important as the input should not show an error until the user touches/interacts with it. Then, while the user is interacting with it, the input should show that it is focused. Finally, after the input has been touched, if the value doesn’t validate, it needs to show an error state.

We’ll use Formik ( to manage...