Minor changes: Updated the license, Updated some read me documentation, And fixed some typos

LICENSE

···
+MIT License
+
+Copyright (c) 2025 Barry Prendergast
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

SETUP.md

···
-# Lanyard Setup Guide
+# Lanyards Setup Guide
 
 ## Quick Start with App Password (Recommended for Development)
 
···
 
 1. Go to [https://bsky.app/settings/app-passwords](https://bsky.app/settings/app-passwords)
 2. Click "Add App Password"
-3. Give it a name (e.g., "Lanyard Development")
+3. Give it a name (e.g., "Lanyards Development")
 4. Copy the generated password
 
 ### 2. Configure Environment Variables
···
 
 ## Authentication Methods
 
-Lanyard supports two authentication methods:
+Lanyards supports two authentication methods:
 
 ### App Password (Development)
 - **Pros**: Simple setup, no OAuth configuration needed

lexicons/README.md

···
-# Lanyard Lexicons
+# Lanyards Lexicons
 
 This directory contains the AT Protocol lexicon definitions for Lanyard.
+
+> [!NOTE]
+> Lanyards uses the AT Protocol Lexicon CLI [@atproto/lex-cli](https://www.npmjs.com/package/@atproto/lex-cli) to automatically generate TypeScript types from the lexicon JSON definitions.
 
 ## Namespace Structure
 
···
 
 ```
 at.lanyard/
-├── actor/              - Researcher identity and relationships
-│   ├── profile         - Core researcher profile
-│   └── affiliation     - Professional affiliations
-├── document/           - Research outputs
-│   └── work            - Scholarly contributions (DOI-based)
-├── event/              - Academic activities
-│   └── academic        - Conferences, symposiums, workshops
-├── link/               - External connections
-│   ├── social          - Social network profiles
-│   └── web             - Custom web links
-├── location/           - Geographic data (reusable)
-│   └── place           - ISO country/region/city codes
-└── organization/       - Institutions (reusable)
-    └── institution     - Universities, companies (Ringgold/GRID)
+├── researcher          - Core researcher profile (singleton record)
+├── work                - Scholarly contributions (DOI-based, multiple records)
+├── event               - Academic events (conferences, workshops, multiple records)
+├── link                - External profiles and links (unified, multiple records)
+├── publication         - Publication venues (journals, conferences, embedded object)
+├── organization        - Institutions and entities (embedded object)
+└── location            - Geographic locations (embedded object)
 ```
 
-## Lexicon Hierarchy
+## Lexicon Details
 
-### Core Objects (Independent)
+### Records (Top-level collections)
 
-**`at.lanyard.location.place`**
-- Geographic location using ISO codes
-- Used by: profile, institution, event
-- Fields: country (ISO 3166-1), region (ISO 3166-2), city
+Records are stored as collections in the user's repository with `at-uri` identifiers.
 
-**`at.lanyard.organization.institution`**
-- Academic/research institutions
-- Used by: affiliation, event (as organizer)
-- Identifiers: Ringgold ID, GRID ID
-- References: location.place
+> [!NOTE]
+> The following records are given as example. Referred to the lexicon themselves from more complete and up-to-date documentation.
 
-### Actor (Researcher)
+**`at.lanyard.researcher`**
+- **Type**: Record (singleton, key: `literal:self`)
+- **Description**: The researcher's core profile and identity
+- **Required Fields**: `did`, `handle`, `createdAt`
+- **Optional Fields**: `displayName`, `avatar`, `description` (synced from Bluesky), `honorifics`, `location`, `affiliations`, `updatedAt`
+- **Embeds**: `location` (at.lanyard.location), `affiliations[]` (affiliation object)
+- **Subdefs**: `affiliation` - professional relationships with organizations
 
-**`at.lanyard.actor.profile`**
-- Central researcher identity
-- Key: `self` (singleton record)
-- References: location.place
-- Synced from: Bluesky profile (avatar, displayName, description)
-- Additional: honorifics (Dr, Prof)
+**`at.lanyard.work`**
+- **Type**: Record (multiple, key: `tid`)
+- **Description**: Scholarly contributions identified by DOI
+- **Required Fields**: `doi`, `type`, `createdAt`
+- **Optional Fields**: `title`, `authors[]`, `publicationDate`, `venue`, `publication` (ref), `event` (at-uri ref)
+- **Work Types**: `abstract`, `poster`, `paper`, `conference-proceeding`, `journal-article`, `book-chapter`, `book`, `preprint`, `dataset`, `other`
+- **Note**: Metadata auto-fetched from CrossRef/DataCite via DOI
 
-**`at.lanyard.actor.affiliation`**
-- Professional relationships
-- Key: `tid` (multiple records)
-- References: organization.institution
-- Fields: role, startDate, endDate, isPrimary
+**`at.lanyard.event`**
+- **Type**: Record (multiple, key: `tid`)
+- **Description**: Academic events where research is presented or discussed
+- **Required Fields**: `name`, `type`, `startDate`, `createdAt`
+- **Optional Fields**: `endDate`, `location` (ref), `organizer` (ref), `relatedWorks[]` (at-uri refs), `url`
+- **Event Types**: `conference`, `symposium`, `workshop`, `seminar`, `lecture`, `poster-session`, `webinar`, `other`
+- **Embeds**: `location` (at.lanyard.location), `organizer` (at.lanyard.organization)
 
-### Links (External Connections)
+**`at.lanyard.link`**
+- **Type**: Record (multiple, key: `tid`)
+- **Description**: External profiles and custom web links (unified collection)
+- **Required Fields**: `url`, `type`, `createdAt`
+- **Optional Fields**: `platform`, `title`, `username`, `isLocked`
+- **Link Types**:
+  - `social` - Twitter, LinkedIn, Bluesky
+  - `academic` - ORCID, Google Scholar, ResearchGate, Semble
+  - `web` - Custom web links (max 3 per profile)
+- **Platforms**: `bluesky`, `twitter`, `linkedin`, `researchgate`, `googlescholar`, `orcid`, `semble`, `custom`
+- **Constraints**: 1 per social/academic platform, max 3 custom web links
 
-**`at.lanyard.link.social`**
-- Social network profiles
-- Platforms: bluesky, twitter, linkedin, researchgate, googlescholar, semble
-- One per platform (Bluesky is locked/auto-synced)
+### Embedded Objects (Reusable components)
 
-**`at.lanyard.link.web`**
-- Custom web links
-- Maximum 3 per profile
-- Fields: title, url
+Embedded objects are not stored as separate records but are embedded within other records.
 
-### Research Output
+**`at.lanyard.location`**
+- **Type**: Object (embedded)
+- **Description**: Geographic location using ISO standard codes
+- **Fields**: `country` (ISO 3166-1 alpha-2), `region` (ISO 3166-2), `city`, `isVirtual`
+- **Used By**: researcher, organization, event
+- **Examples**: `{country: "US", region: "US-CA", city: "San Francisco"}`, `{isVirtual: true}`
 
-**`at.lanyard.document.work`**
-- Scholarly contributions
-- Primary identifier: DOI
-- Metadata auto-fetched from CrossRef/DataCite
-- Types: paper, poster, abstract, dataset, etc.
+**`at.lanyard.organization`**
+- **Type**: Object (embedded)
+- **Description**: Institutions, publishers, societies, funders, companies
+- **Required Fields**: `name`
+- **Optional Fields**: `type`, `ringgoldId`, `gridId`, `rorId`, `location` (ref), `website`, `logo` (blob)
+- **Organization Types**: `institution`, `publisher`, `society`, `funder`, `company`, `government`, `other`
+- **Used By**: researcher.affiliation, event.organizer, publication.publisher
+- **Identifiers**: Ringgold ID (academic institutions), GRID ID, ROR ID
 
-### Events
-
-**`at.lanyard.event.academic`**
-- Conferences, symposiums, workshops
-- References: location.place, organization.institution (organizer)
-- Can link to: document.work[] (presented works)
+**`at.lanyard.publication`**
+- **Type**: Object (embedded)
+- **Description**: Publication venues (journals, conference proceedings, preprint servers)
+- **Required Fields**: `name`
+- **Optional Fields**: `type`, `issn`, `publisher` (ref), `website`, `subjects[]`
+- **Publication Types**: `journal`, `proceedings`, `preprint`, `repository`, `book-series`, `other`
+- **Used By**: work.publication
+- **Examples**: Nature, PLOS ONE, arXiv, NeurIPS Proceedings
 
 ## Object Relationships
 
 ```
-actor.profile
-  ├─ refs → location.place (home location)
-  ├─ has → actor.affiliation[] (multiple)
-  └─ has → link.social[], link.web[]
+at.lanyard.researcher (record)
+  ├─ embeds → location (object)
+  └─ embeds → affiliations[] (objects)
+      └─ embed → organization (object)
+          └─ embed → location (object)
 
-actor.affiliation
-  └─ refs → organization.institution
+at.lanyard.work (record)
+  ├─ embeds → publication (object)
+  │   └─ embed → organization (object) [publisher]
+  └─ refs → event (at-uri) [optional]
 
-organization.institution
-  └─ refs → location.place
+at.lanyard.event (record)
+  ├─ embeds → location (object)
+  ├─ embeds → organizer (organization object)
+  └─ refs → relatedWorks[] (at-uri)
 
-event.academic
-  ├─ refs → organization.institution (organizer)
-  ├─ refs → location.place (venue)
-  └─ refs → document.work[] (presented)
+at.lanyard.link (record)
+  └─ (no references)
 ```
 
 ## Design Principles
 
-1. **Reusability** - location and organization are shared objects
-2. **Single Source of Truth** - No duplicated definitions
-3. **Clear Ownership** - actor.* owns links, affiliations
-4. **Modularity** - Each lexicon can evolve independently
-5. **AT Protocol Conventions** - Follows app.bsky.* patterns
+1. **Flat Namespace** - Simple top-level structure, no deep nesting
+2. **Embedded Objects** - Reusable components (location, organization, publication) embedded, not separate records
+3. **DOI-Centric** - Works primarily identified by DOI, metadata auto-fetched
+4. **Unified Links** - Single collection for social, academic, and custom links
+5. **AT Protocol Conventions** - Follows app.bsky.* patterns with records and embedded objects
+6. **Single Source of Truth** - Bluesky profile data is locked and synced
 
 ## Future Expansion
 
 The structure allows for growth:
-- `at.lanyard.actor.education` - Academic degrees
-- `at.lanyard.document.grant` - Research funding
-- `at.lanyard.document.patent` - Patents
-- `at.lanyard.event.workshop` - Specific workshop type
-- `at.lanyard.organization.funder` - Funding bodies
+- `at.lanyard.education` - Academic degrees and credentials
+- `at.lanyard.grant` - Research funding records
+- `at.lanyard.patent` - Patent records
+- `at.lanyard.dataset` - Research datasets
+- `at.lanyard.teaching` - Teaching activities and courses

src/app/[handle]/page.tsx

···
     // Get Bluesky profile
     const bskyProfile = await agent.getProfile({ actor: did });
 
-    // Get Lanyard profile
+    // Get Lanyards profile
     const repo = new ResearcherRepository(agent);
     const lanyardProfile = await repo.getProfile(did);
 
···
           <div className="text-center">
             <h1 className="text-2xl font-bold mb-4">Profile Not Found</h1>
             <p className="text-gray-600 mb-6">
-              This user hasn&apos;t created a Lanyard profile yet.
+              This user hasn&apos;t created a Lanyards profile yet.
             </p>
-            <a
-              href="/"
-              className="text-blue-600 hover:underline"
-            >
+            <a href="/" className="text-blue-600 hover:underline">
               Go to homepage
             </a>
           </div>
···
     }
 
     // Get all profile data
-    const [affiliations, webLinks, works, events] =
-      await Promise.all([
-        repo.listAffiliations(did),
-        repo.listWebLinks(did),
-        repo.listWorks(did),
-        repo.listEvents(did),
-      ]);
+    const [affiliations, webLinks, works, events] = await Promise.all([
+      repo.listAffiliations(did),
+      repo.listWebLinks(did),
+      repo.listWorks(did),
+      repo.listEvents(did),
+    ]);
 
     return (
       <ProfileView
···
           <p className="text-gray-600 mb-6">
             Unable to load this profile. Please try again later.
           </p>
-          <a
-            href="/"
-            className="text-blue-600 hover:underline"
-          >
+          <a href="/" className="text-blue-600 hover:underline">
             Go to homepage
           </a>
         </div>

src/app/layout.tsx

···
 import './globals.css';
 
 export const metadata: Metadata = {
-  title: 'Lanyard - Researcher Profiles on AT Protocol',
+  title: 'Lanyards - Researcher Profiles on AT Protocol',
   description:
     'A dedicated profile for researchers, built on the AT Protocol. An alternative to ORCID.',
 };

src/components/DashboardLayout/DashboardLayout.tsx

···
       {/* Header */}
       <header className={styles.header}>
         <div className={styles.headerContent}>
-          <h1 className={styles.title}>Lanyard Dashboard</h1>
+          <h1 className={styles.title}>Lanyards Dashboard</h1>
           <button onClick={handleLogoutClick} className={styles.logoutButton}>
             Logout
           </button>

src/components/auth/LoginForm.tsx

···
       </button>
 
       <p className="text-xs text-gray-500 text-center">
-        Sign in to access your Lanyard profile
+        Sign in to access your Lanyards profile
       </p>
     </form>
   );

src/types/README.md

···
+## Lanyards Types Generation
+
+Lanyards uses the AT Protocol Lexicon CLI [@atproto/lex-cli](https://www.npmjs.com/package/@atproto/lex-cli) to automatically generate TypeScript types from the lexicon JSON definitions.
+
+### Generated Files
+
+When you run the code generation, the following files are created in `src/types/generated/`:
+
+```
+src/types/generated/
+├── index.ts                          - Main export file with all types
+├── lexicons.ts                       - Lexicon definitions for runtime validation
+├── util.ts                           - Utility types and helpers
+└── types/at/lanyard/                 - Generated type definitions
+    ├── researcher.ts                 - Researcher record types
+    ├── work.ts                       - Work record types
+    ├── event.ts                      - Event record types
+    ├── link.ts                       - Link record types
+    ├── publication.ts                - Publication object types
+    ├── organization.ts               - Organization object types
+    └── location.ts                   - Location object types
+```
+
+> [!NOTE]
+> The types are **NOT** committed to git in most workflows, but are generated as part of the build process.
+
+### Commands
+
+**Generate types once:**
+```bash
+npm run lex:gen
+```
+This command reads all `.json` files in the `lexicons/` directory and generates TypeScript types in `src/types/generated/`.
+
+**Watch mode (development):**
+```bash
+npm run lex:watch
+```
+Watches for changes to lexicon files and automatically regenerates types.
+
+**Build process:**
+```bash
+npm run build
+```
+The build command automatically runs `lex:gen` before building the Next.js app to ensure types are up-to-date.
+
+### How It Works
+
+1. **Lexicon Definitions**: JSON files in `lexicons/` define the schema using AT Protocol lexicon syntax
+2. **CLI Tool**: `@atproto/lex-cli` parses the JSON definitions
+3. **Type Generation**: Creates TypeScript interfaces, types, and validation schemas
+4. **Import & Use**: Generated types are imported throughout the codebase via `@/types/generated`
+
+### Generated Type Structure
+
+Each generated file includes:
+- **Record types**: For top-level collection records (researcher, work, event, link)
+- **Object types**: For embedded objects (location, organization, publication)
+- **Input/Output schemas**: For API operations (create, update, delete)
+- **Validation functions**: Runtime validation using the lexicon definitions
+
+### Example Usage
+
+```typescript
+import {
+  Researcher,
+  Work,
+  Event,
+  Link
+} from '@/types/generated';
+
+// Use generated types in your code
+const researcher: Researcher.Record = {
+  did: 'did:plc:...',
+  handle: 'researcher.bsky.social',
+  createdAt: new Date().toISOString(),
+  // ... other fields
+};
+```
+
+### Type Declaration Fixes
+
+Due to import path resolution in generated types, we maintain custom type declarations in `src/types/`:
+- **`atproto.d.ts`**: Namespace declarations for AT Protocol repo operations
+- **`multiformats.d.ts`**: Module declaration for CID imports
+
+These ensure the generated types work correctly with the AT Protocol SDK.
+
+### Regenerating Types
+
+You should regenerate types whenever you:
+1. **Modify lexicon files**: Add/remove fields, change types, update descriptions
+2. **Add new lexicons**: Create new `.json` files in `lexicons/`
+3. **Change constraints**: Update validation rules (maxLength, enum values, etc.)
+4. **Pull changes**: After pulling changes that include lexicon updates
+
+

src/types/index.ts

···
 /**
- * Type exports for Lanyard application
+ * Type exports for Lanyards application
  * Re-exports generated AT Protocol lexicon types with convenient aliases
  */