On Day 1 (or a few days later) you will be given a copy of a Google Apps Project that is a commercial grade DNS Server Management system that has been designed for Software as a Service (Saas) with you as the software platform owner.  It's novel in every way imaginable. 

You are going to use a relational database built in a google spreadsheet that allows your clients to use your website backend to create and update their own Domain ownership and DNS Zone records in your system -- which then automatically synchs with remote DNS servers sitting in other parts of the world -- all via a Google Apps project attached to a spreadsheet with no complex Google APIs required.   

Your cost for hosting your site is zero given you will be using Google Servers -- and your cost to rent a remote DNS server for this is $4 to 8$ per month for one, and $20 max for a robust pair of servers with all the bells needed for your initial launch. OR you can use our simiulation engine to save pennies until  you want to launch your own business or learn about remote Unix hosting. (and you don't have to make these decisions up front. Plan on the simulation engine and upgrade if it feels good later).      

This is far beyond anything Google ever invisioned for their "Single Page App" end point and it goes to show what "can be done" with internet technology if you understand "request-response basics" , "a little html, css and javascript", and the digital education needs of the next generation for our communal success.  

Your immersive first project includes: 

1. Website - it's a full website with a graphical  front end, login page and backend management system -- all written in HTML, CSS, and javascript (client and server side). Your site uses no frameworks but it relies on a lot of digital sleight of hand to change scenes and ajax calls,  neither of which are overly desirable for this type of application -- but were required to give you a single point learning platform. It relies on Google Scripting objects as needed for the data management and server to sever communction as well.  A Google Apps Project is NOT an ideal system for buiding a simple data driven websites.  This is very complex relative to other options BUT its a single programming interface with other benefits. Learn here and the rest will be easier. 

2. Authentication Engine - it includes a commercial grade, multi Tier User Management and Authentication system with Platform, Tenant and Client user levels and multiple auth levels (Saas level architecture. You'll never need more.)

3. RDBMS - it uses google sheets flat files for the basis for a relational database management system (RDBMS). You will learn about spreadsheets as flat files vs RDBMs and learn how to turn flat files into RDBMs. This will be as complex as it gets for managing data. All other applcations will be easier. 

4. Client Side Form handling - You will use digital slieght of hand client side form handling to manage forms, form inputs and delete records

5. DOM Manipulation and Advanced CSS - you will use DOM manipulation for client side data manageament.  You will use DOM manipulation combined with advanced CSS concepts to show and hide columns on the fly. 

6. AUD-G engine - It has a commercial grade Add, Update and Delete engine to assist with rapid scaling of database requirements. The G stands for get. This is a modern upgrade to the term "CRUD" that comes from the 60's but means the same thing (Create, Read, Update, Delete).  AUD-G sounds cooler for sure. 

7. Data Validation Engines - it includes data validation engines for both client side and server side validation. These integrate with spreadsheet tools for configuration file generation and rapid testing of the server side engine. 

8. Console Logging engine - it has a complex engine for console logging to assist with rapid troubleshooting that is not provided well in chrome for client side composite applications. 

9. Server to Server communction - it includes synch'd connections with remote Unix servers running DNS server software and systems as well as a remote webserver needed for bounce messaging for faux A record configuration.

10. Dev Tools - we had to build out dev tools to help fill in blanks where the Google Apps IDE and Chrome Browser failure reporting falls short.

11. Documenation Engine - it has a documentation that may be included 

NOTE: everything you learn here is transferable to traditional hosting configurations and other endpoint configurations.  The spreadsheet DB can be swapped for SQL, the client side calls can be converted into much simpler request response calls with server side scripting. 

This is a PhD level programming project and working business model that you are goign to get to use to start your Full Stack educational experience.