chore: Update Aetherspace Docs, CV

Author: codinsonn

features/cv-page/mocks/resumeData.mock.ts

@@ -45,15 +45,15 @@ export const dummyResumeData: TResumeData = {
       year: '2023',
       linkUrl: '',
       collaborators: '',
-      description: `6mo, NY, Built with expo, react-native & next.js, but can't say more sadly`,
+      description: `6mo, NY, Built with Expo, React-native & Next.js, but can't say more sadly`,
     },
     {
       title: 'Cancer Companion App',
       client: 'My Cancer Companion by Dr. Eric Lim, Thoracic Surgeon',
       year: '2022',
       linkUrl: 'https://www.mycancercompanion.com/',
       collaborators: '',
-      description: `My Cancer Companion is a free app providing the best, most up-to-date, and authoritative information for people with lung cancer. Cool features I worked on include Symptom logging (charts), Personalised recommendations, and Appointment management (calendars). Helped build this with Expo, React-Native, and Nest.js in Belgium and London.`,
+      description: `My Cancer Companion is an app I helped build providing the best, most up-to-date, and authoritative information for people with lung cancer. Cool features I worked on include Symptom logging (charts), Personalised recommendations, and Appointment management (calendars). Helped build this with Expo, React-Native, and Nest.js in Belgium and London.`,
     },
     {
       title: 'React renderer for a B2B eCommerce CMS',
@@ -75,6 +75,14 @@ export const dummyResumeData: TResumeData = {
     },
   ],
   writing: [
+    {
+      title: 'How to choose cross-platform tech',
+      year: '2023',
+      publisher: 'dev.to',
+      linkUrl: 'https://dev.to/codinsonn/why-use-react-native-over-flutter-a-recap-57b0',
+      collaborators: 'References work by Evan Bacon & Theo Browne (T3.gg)',
+      description: `Users increasingly prefer mobile apps to the mobile web, and there are many ways to build them. Should you choose React-Native over Flutter? Let's find out.`,
+    },
     {
       title: 'Move fast and Build Things',
       year: '2022',
@@ -113,14 +121,22 @@ export const dummyResumeData: TResumeData = {
   ],
   features: [],
   workExperience: [
+    {
+      title: 'Lead Full-Stack Consultant',
+      company: 'Talentguide',
+      from: '2023',
+      to: 'Now',
+      linkUrl: 'https://talentguide.com',
+      description: `Currently scaling the already built AI powered MVP for Talentguide to a production ready app. Mostly front-end web and back-end + cloud work, while the AI / ML core is constantly being improved by the client's internal team. Currently planning on building the Mobile version of the app with Aetherspace.`,
+    },
     {
       title: 'Full-Product Typescript Engineer',
       from: '2022',
       to: '2023',
       company: 'Bothrs',
-      location: 'Ghent, Belgium',
+      location: 'Ghent, Belgium (also: New York & London)',
       linkUrl: 'https://www.bothrs.com/',
-      description: `Built some cool Mobile Apps with Web features using Expo, React-Native, and Next.js here. Included clients in the US, London, Healthcare, and eCommerce sectors.`,
+      description: `Built some cool Mobile Apps with Web features using Expo, React-Native, and Next.js here. Often the initial MVP or incubator project was built & validated by our smaller teams, while the client scaled up their team to take over. Included clients in the US, UK, Healthcare, and ECommerce sectors.`,
     },
     {
       title: 'Full-Stack React Developer',
@@ -129,7 +145,7 @@ export const dummyResumeData: TResumeData = {
       company: 'Marlon, iO',
       location: 'Ghent, Belgium',
       linkUrl: 'https://www.iodigital.com/nl/history/marlon',
-      description: `Worked on a wide variety of projects here. Mostly Front-end work for their in-house eCommerce CMS that powers the likes of Dockx Rental and Denderwood. Aside from that, I also worked on some advanced web-based configurators for Daikin EU here, and even some Mobile apps with React-Native and Expo.`,
+      description: `Worked on a wide variety of projects here. Mostly Front-end work for their in-house ECommerce CMS that powers the likes of Dockx Rental and Denderwood. Aside from that, I also worked on some advanced web-based configurators for Daikin EU here, and even some Mobile apps with React-Native and Expo.`,
     },
     {
       title: 'Back-End, Web & Mobile Developer',
@@ -152,7 +168,7 @@ export const dummyResumeData: TResumeData = {
       description: '',
     },
     {
-      title: 'Free GREEN stack template repo',
+      title: 'GREEN stack template repo',
       from: '2020',
       to: 'Now',
       company: 'Aetherspace Digital',

packages/@aetherspace/navigation/AetherPage/README.md

@@ -55,28 +55,33 @@ import { aetherResolver } from 'aetherspace/utils/serverUtils'
 
 /* --- Schemas ------------- */
 
+// Our resolver args, defined as a zod schema
 export const HealthCheckArgs = aetherSchema('HealthCheckArgs', {
   echo: z.string().optional().describe('Echoes back the echo argument'),
 })
 
-// (You can reuse schema definitions with pick / omit / extend commands as well)
+// Same thing for our response schema, but we're picking the echo argument from the args schema
 export const HealthCheckResponse = HealthCheckArgs.pickSchema('HealthCheckResponse', {
   echo: true, // <- Pick the echo argument from the args schema, since we're echoing it back
 })
 
 /* --- Config -------------- */
 
+// Our resolver config, which will tell aetherResolver() what the args & response shape should be
 const resolverConfig = {
   argsSchema: HealthCheckArgs,
   responseSchema: HealthCheckResponse,
 }
 
 /* --- healthCheck() ------- */
 
-// Our actual business logic
+// Our actual business logic, wrapped with aetherResolver() and supplied with our resolverConfig
 export const healthCheck = aetherResolver(async ({ args }) => ({
     echo: args.echo, // <- Echo back the echo argument 🤷‍♂️
 }), resolverConfig)
+
+// We now have a nice bundle of our business logic function, with the args & response schemas attached
+// This bundle can be used in multiple ways, as we'll see below
 ```
 
 Later, in a `route.ts` file in the `/routes/` folder, you can export the following:
@@ -88,13 +93,15 @@ import { healthCheck } from '../resolvers/healthCheck'
 /* --- GraphQL ------------- */
 
 // Make resolver available to GraphQL (picked up by automation)
+// GraphQL schema definitions will be generated automatically from the attached args & response shapes
 export const graphResolver = makeGraphQLResolver(healthCheck)
 ```
 
 Optionally, you can also generate a REST api by exporting the following from that same `route.ts` file:
 
 ```ts
-import { makeNextApiHandler, makeGraphQLResolver } from 'aetherspace/utils/serverUtils'
+import { makeNextApiHandler } from 'aetherspace/utils/serverUtils'
+import { healthCheck } from '../resolvers/healthCheck'
 
 /* --- Next.js API Routes -- */
 
@@ -103,7 +110,7 @@ export const GET = makeNextRouteHandler(healthCheck)
 export const POST = makeNextRouteHandler(healthCheck)
 ```
 
-On top of that, the `healthCheck` function "bundle" we made by wrapping with `aetherResolver()` is still usable as a regular Javascript promise, so feel free to use it in other data resolvers as well.
+On top of that, the `healthCheck` function "bundle" we made by wrapping with `aetherResolver()` is still usable as a regular Javascript promise for use in other data resolvers as well.
 
 ### Easy mode -- Generating GraphQL Resolvers with the CLI
 

packages/@aetherspace/navigation/README.md

@@ -126,7 +126,7 @@ Use `AetherLink` from `aetherspace/navigation` to link to a route in your app:
 ```tsx
 import { Link } from 'aetherspace/nagivation'
 
-// e.g. for a /bio/[slug] route which could've come from e.g /{workspace}/routes/bio/[slug].tsx
+// e.g. for a '/bio/[slug]' route which could be defined at e.g '/{workspace}/routes/bio/[slug].tsx'
 
 <Link to="/bio/codinsonn">
      View links in bio page
@@ -143,7 +143,7 @@ import { useAetherRoute } from 'aetherspace/navigation'
 const { params } = useAetherRoute(props, screenConfig)
 ```
 
-If you're wondering what the `screenConfig` should contain, or are wondering how to access API route parameters, we suggest you continue with [GraphQL and Data-Fetching](/packages/@aetherspace/navigation/AetherPage/README.md)
+If you're wondering what the `screenConfig` should contain, how you should feed data to your screens or are wondering how to access API route parameters, we suggest you continue by reading our docs on [GraphQL and Data-Fetching](/packages/@aetherspace/navigation/AetherPage/README.md)
 
 ## Learn more about Aetherspace:
 

packages/@aetherspace/schemas/README.md

@@ -298,7 +298,7 @@ const RequiredSchema = OptionalSchema.requiredSchema('RequiredTopic')
 yarn ats add-schema
 ```
 
-This will prompt you for a tagrte workspace and name:
+This will prompt you for a target workspace and name:
 
 ```sh
 >>> Modify "aetherspace-green-stack-starter" using custom generators