Feature: auth (#635)

* Get basic auth running with errors

* add login method

* logging

* add register endpoint

* stop using forked version of form

* testing error states

* fix dev settings

* fix up error handling and add some new methods

* Add additional auth utilities

* add schema to response

* begin adding join route

* rename CmsAuth

* remove logging

* begin adding some cms actions

* begin adding event fetching

* Add ts packages

* use tsconfig

# Conflicts:
#	tsconfig.json

* remove some comments

* add remix type defs

* update server.js to match remix example

* convert entry files to ts

* use ts

* allow redirect on success

* add event forwarding

* query all calendars

* display message

* move auth into membership route

* use ts

* add route protection back in to dashboard

* return value from loader

* move files into frontend route

* update paths from rename

* Move app files into __app

* Add tailwind

* remove tailwind.css from vc

* ignore tailwind

* add spread params to svgs

* move around auth routes and add styles

* rename dashboard to membership index

* adjust styles

* move join into auth

* remove old thing

* renive extra links

* fix up auth

* add getCalendars

* move auth into pathless

* move layouts into correct folder

* use new singletask layout

* convert to ts

* use updated types

* add first pass of events

* add inter font

* use classNames

* rename method

* add events calendar

* add events calendar views

* description

* update calendar formatting

* add popover for event

* remove console.log

* go stacked layout

* adjust for stacked layout

* add meta data

* begin adding more components and details

* Add ts versions

* move files

* reset dependencies

* check for null data

* fix some ts issues

* update dependencies

* update utility types

* update heroicons

* abstract some components

* clean up styling

* use sky instead of indigo

* upgrade remix dependencies and scripts

* add tiny-invariant

* convert to ts

* allow for netlify dev

* use globals

* open in new tab

* continue debugging

* auth debugging go away

* ignore

* convert to ts and wrap in global

* split out cms functions

* removing logging

* check for user

* move tls reject to env variable

* read user via getUser

* removing

* clean up events

* authenticate

* use split versions

* remove esbuild from node bundler

* turn on defaults

* turn off esnext for now

* update login form

* add note

* fix this thing

* remove console.log call

* use custom livereload from 1.6.4 of remix

see remix-run/remix#2997 (comment)

* remove debugging help

* move file

* fix faker fn

* tweak Button styling and add fullWidth prop

* Add TextInput and FieldGroup

* style reset password form

* clean up auth forms

* convert to ts

* convert some ts

* add wide option

* add FieldSet, TextArea, and addons for TextInput

* clean up register

* fix up register form / hide form for now

* use solid icons

* Abstract events list and add ics link

* use updated imports

* add events to dashboard

* turn on esnext

* correct link address

* remove comment

* add getCalendar

* add black and white buttons

* Add passedRef prop

* Add subscribe links

* move join files

* fix links

* fix import

* Fix path for mdx loading

* abstract out not found content

* Add splat page to catch non-loader 404s

* do not default to empty string

* remove extra h1

.github/workflows/monthly-challenge-issue.yml

@@ -20,7 +20,7 @@ jobs:
             ## Issue Context
             *Add New Challenge to the Site*
 
-            You can use [June 2021](/~https://github.com/Virtual-Coffee/virtualcoffee.io/blob/main/app/routes/monthlychallenges/june-2021.jsx) as kind of a template
+            You can use [June 2021](/~https://github.com/Virtual-Coffee/virtualcoffee.io/blob/main/app/routes/__frontend/monthlychallenges/june-2021.jsx) as kind of a template
 
             ## Steps
             - [ ] Follow the instructions for [creating monthly challenge pages](/~https://github.com/Virtual-Coffee/virtualcoffee.io/#monthly-challenges)

.gitignore

@@ -10,10 +10,11 @@ node_modules
 
 
 
-/netlify/functions/server/index.js
+/netlify/functions/server
 /public/build
 
 # Local Netlify folder
 .netlify
 /app/styles
 /.tmp
+/app/tailwind.css

README.md

@@ -183,26 +183,26 @@ If you'd like to work on a feature that requires an API key, please reach out to
 
 Our [VC Resources](https://virtualcoffee.io/resources) are creating using [MDX](https://mdxjs.com/). MDX is basically a combination of Markdown and React.
 
-Any files added to `app/routes/resources` will be automatically loaded and added to the appropriate index page.
+Any files added to `app/routes/__frontend/resources` will be automatically loaded and added to the appropriate index page.
 
 A good way to start adding a new page would be to copy one of the existing pages, then edit the details and content.
 
 ### Newsletters
 
-The newsletters (for now) are simply `jsx` files, and can be found in `app/routes/newsletter/issues`.
+The newsletters (for now) are simply `jsx` files, and can be found in `app/routes/__frontend/newsletter/issues`.
 
 When you add a new issue, **make sure to add it to the index**. Here's how:
 
 - Open `app/data/newsletters.js`
 - `import` the new issue
 - Add the new issue to the `newsletters` array.
 
-So, if you have created `app/routes/newsletter/issues/2022-03.jsx`:
+So, if you have created `app/routes/__frontend/newsletter/issues/2022-03.jsx`:
 
 ```diff
-+ import { handle as issue202203 } from '~/routes/newsletter/issues/2022-03';
-import { handle as issue202202 } from '~/routes/newsletter/issues/2022-02';
-import { handle as issue202201 } from '~/routes/newsletter/issues/2022-01';
++ import { handle as issue202203 } from '~/routes/__frontend/newsletter/issues/2022-03';
+import { handle as issue202202 } from '~/routes/__frontend/newsletter/issues/2022-02';
+import { handle as issue202201 } from '~/routes/__frontend/newsletter/issues/2022-01';
 
 const newsletters = [
 + 	{ handleData: issue202203, slug: '2022-03' },
@@ -213,20 +213,20 @@ const newsletters = [
 
 ### Monthly Challenges
 
-The monthly challenges (for now) are simply `jsx` files, and can be found in `app/routes/monthlychallenges`.
+The monthly challenges (for now) are simply `jsx` files, and can be found in `app/routes/__frontend/monthlychallenges`.
 
 When you add a new challenge, **make sure to add it to the index**. Here's how:
 
 - Open `app/data/monthlyChallenges/getChallenges.js`
 - `import` the new challenge
 - Add the new challenge to the `challenges` array.
 
-So, if you have created `app/routes/monthlychallenges/apr-2022.jsx`:
+So, if you have created `app/routes/__frontend/monthlychallenges/apr-2022.jsx`:
 
 ```diff
-+ import { handle as apr2022 } from '~/routes/monthlychallenges/apr-2022';
-import { handle as mar2022 } from '~/routes/monthlychallenges/mar-2022';
-import { handle as feb2022 } from '~/routes/monthlychallenges/feb-2022';
++ import { handle as apr2022 } from '~/routes/__frontend/monthlychallenges/apr-2022';
+import { handle as mar2022 } from '~/routes/__frontend/monthlychallenges/mar-2022';
+import { handle as feb2022 } from '~/routes/__frontend/monthlychallenges/feb-2022';
 
 const challenges = [
 + 	{ handleData: apr2022, slug: 'apr-2022' },