Adding content to 101-typescript-types

.astro/settings.json

@@ -1,8 +0,0 @@
-{
-	"devToolbar": {
-		"enabled": false
-	},
-	"_variables": {
-		"lastUpdateCheck": 1757411878192
-	}
-}

.astro/types.d.ts

@@ -1 +0,0 @@
-/// <reference types="astro/client" />

.cursor/rules/content-migration.mdc

@@ -1,155 +0,0 @@
----
-description: When user requests migrating old roadmap content to new folder from content-old to content folder
-globs: 
-alwaysApply: false
----
-# Content Migration Rule
-
-## Rule Name: content-migration
-
-## Description
-This rule provides a complete process for migrating roadmap content from old structure to new structure using migration mapping files.
-
-## When to Use
-Use this rule when you need to:
-- Migrate content from content-old directories to content directories
-- Use a migration-mapping.json file to map topic paths to content IDs
-- Populate empty content files with existing content from legacy structure
-
-## Process
-
-### 1. Prerequisites Check
-- Verify the roadmap directory has a `migration-mapping.json` file
-- Confirm `content-old/` directory exists with source content
-- Confirm `content/` directory exists with target files
-
-### 2. Migration Script Creation
-Create a Node.js script with the following functionality:
-
-```javascript
-const fs = require('fs');
-const path = require('path');
-
-// Load the migration mapping
-const migrationMapping = JSON.parse(fs.readFileSync('migration-mapping.json', 'utf8'));
-
-// Function to find old content file based on topic path
-function findOldContentFile(topicPath) {
-  const parts = topicPath.split(':');
-  
-  if (parts.length === 1) {
-    // Top level file like "introduction"
-    return path.join('content-old', parts[0], 'index.md');
-  } else if (parts.length === 2) {
-    // Like "introduction:what-is-rust"
-    const [folder, filename] = parts;
-    return path.join('content-old', folder, `${filename}.md`);
-  } else if (parts.length === 3) {
-    // Like "language-basics:syntax:variables"
-    const [folder, subfolder, filename] = parts;
-    return path.join('content-old', folder, subfolder, `${filename}.md`);
-  }
-  
-  return null;
-}
-
-// Function to find new content file based on content ID
-function findNewContentFile(contentId) {
-  const contentDir = 'content';
-  const files = fs.readdirSync(contentDir);
-  
-  // Find file that ends with the content ID
-  const matchingFile = files.find(file => file.includes(`@${contentId}.md`));
-  
-  if (matchingFile) {
-    return path.join(contentDir, matchingFile);
-  }
-  
-  return null;
-}
-
-// Process each mapping
-console.log('Starting content migration...\n');
-
-let migratedCount = 0;
-let skippedCount = 0;
-
-for (const [topicPath, contentId] of Object.entries(migrationMapping)) {
-  const oldFilePath = findOldContentFile(topicPath);
-  const newFilePath = findNewContentFile(contentId);
-  
-  if (!oldFilePath) {
-    console.log(`❌ Could not determine old file path for: ${topicPath}`);
-    skippedCount++;
-    continue;
-  }
-  
-  if (!newFilePath) {
-    console.log(`❌ Could not find new file for content ID: ${contentId} (topic: ${topicPath})`);
-    skippedCount++;
-    continue;
-  }
-  
-  if (!fs.existsSync(oldFilePath)) {
-    console.log(`❌ Old file does not exist: ${oldFilePath} (topic: ${topicPath})`);
-    skippedCount++;
-    continue;
-  }
-  
-  try {
-    // Read old content
-    const oldContent = fs.readFileSync(oldFilePath, 'utf8');
-    
-    // Write to new file
-    fs.writeFileSync(newFilePath, oldContent);
-    
-    console.log(`✅ Migrated: ${topicPath} -> ${path.basename(newFilePath)}`);
-    migratedCount++;
-  } catch (error) {
-    console.log(`❌ Error migrating ${topicPath}: ${error.message}`);
-    skippedCount++;
-  }
-}
-
-console.log(`\n📊 Migration complete:`);
-console.log(`   Migrated: ${migratedCount} files`);
-console.log(`   Skipped: ${skippedCount} files`);
-console.log(`   Total: ${Object.keys(migrationMapping).length} mappings`);
-```
-
-### 3. Execution Steps
-1. Navigate to the roadmap directory (e.g., `src/data/roadmaps/[roadmap-name]`)
-2. Create the migration script as `migrate_content.cjs`
-3. Run: `node migrate_content.cjs`
-4. Review the migration results
-5. Clean up the temporary script file
-
-### 4. Validation
-After migration:
-- Verify a few migrated files have proper content (not just titles)
-- Check that the content structure matches the old content
-- Ensure proper markdown formatting is preserved
-
-## File Structure Expected
-```
-roadmap-directory/
-├── migration-mapping.json
-├── content/
-│   ├── file1@contentId1.md
-│   ├── file2@contentId2.md
-│   └── ...
-└── content-old/
-    ├── section1/
-    │   ├── index.md
-    │   ├── topic1.md
-    │   └── subsection1/
-    │       └── subtopic1.md
-    └── section2/
-        └── ...
-```
-
-## Notes
-- The migration mapping uses colons (`:`) to separate nested paths
-- Content files in the new structure use the pattern `filename@contentId.md`
-- The script handles 1-3 levels of nesting in the old structure
-- Always create the script with `.cjs` extension to avoid ES module issues

.cursor/rules/gh-cli.mdc

@@ -1,389 +0,0 @@
----
-description: GitHub pull requests
-globs: 
-alwaysApply: false
----
-# gh cli
-
-Work seamlessly with GitHub from the command line.
-
-USAGE
-  gh <command> <subcommand> [flags]
-
-CORE COMMANDS
-  auth:          Authenticate gh and git with GitHub
-  browse:        Open repositories, issues, pull requests, and more in the browser
-  codespace:     Connect to and manage codespaces
-  gist:          Manage gists
-  issue:         Manage issues
-  org:           Manage organizations
-  pr:            Manage pull requests
-  project:       Work with GitHub Projects.
-  release:       Manage releases
-  repo:          Manage repositories
-
-GITHUB ACTIONS COMMANDS
-  cache:         Manage GitHub Actions caches
-  run:           View details about workflow runs
-  workflow:      View details about GitHub Actions workflows
-
-ALIAS COMMANDS
-  co:            Alias for "pr checkout"
-
-ADDITIONAL COMMANDS
-  alias:         Create command shortcuts
-  api:           Make an authenticated GitHub API request
-  attestation:   Work with artifact attestations
-  completion:    Generate shell completion scripts
-  config:        Manage configuration for gh
-  extension:     Manage gh extensions
-  gpg-key:       Manage GPG keys
-  label:         Manage labels
-  preview:       Execute previews for gh features
-  ruleset:       View info about repo rulesets
-  search:        Search for repositories, issues, and pull requests
-  secret:        Manage GitHub secrets
-  ssh-key:       Manage SSH keys
-  status:        Print information about relevant issues, pull requests, and notifications across repositories
-  variable:      Manage GitHub Actions variables
-
-HELP TOPICS
-  accessibility: Learn about GitHub CLI's accessibility experiences
-  actions:       Learn about working with GitHub Actions
-  environment:   Environment variables that can be used with gh
-  exit-codes:    Exit codes used by gh
-  formatting:    Formatting options for JSON data exported from gh
-  mintty:        Information about using gh with MinTTY
-  reference:     A comprehensive reference of all gh commands
-
-FLAGS
-  --help      Show help for command
-  --version   Show gh version
-
-EXAMPLES
-  $ gh issue create
-  $ gh repo clone cli/cli
-  $ gh pr checkout 321
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr
-
-Work with GitHub pull requests.
-
-USAGE
-  gh pr <command> [flags]
-
-GENERAL COMMANDS
-  create:        Create a pull request
-  list:          List pull requests in a repository
-  status:        Show status of relevant pull requests
-
-TARGETED COMMANDS
-  checkout:      Check out a pull request in git
-  checks:        Show CI status for a single pull request
-  close:         Close a pull request
-  comment:       Add a comment to a pull request
-  diff:          View changes in a pull request
-  edit:          Edit a pull request
-  lock:          Lock pull request conversation
-  merge:         Merge a pull request
-  ready:         Mark a pull request as ready for review
-  reopen:        Reopen a pull request
-  review:        Add a review to a pull request
-  unlock:        Unlock pull request conversation
-  update-branch: Update a pull request branch
-  view:          View a pull request
-
-FLAGS
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-INHERITED FLAGS
-  --help   Show help for command
-
-ARGUMENTS
-  A pull request can be supplied as argument in any of the following formats:
-  - by number, e.g. "123";
-  - by URL, e.g. "https://github.com/OWNER/REPO/pull/123"; or
-  - by the name of its head branch, e.g. "patch-1" or "OWNER:patch-1".
-
-EXAMPLES
-  $ gh pr checkout 353
-  $ gh pr create --fill
-  $ gh pr view --web
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr list
-
-List pull requests in a GitHub repository. By default, this only lists open PRs.
-
-The search query syntax is documented here:
-<https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests>
-
-For more information about output formatting flags, see `gh help formatting`.
-
-USAGE
-  gh pr list [flags]
-
-ALIASES
-  gh pr ls
-
-FLAGS
-      --app string        Filter by GitHub App author
-  -a, --assignee string   Filter by assignee
-  -A, --author string     Filter by author
-  -B, --base string       Filter by base branch
-  -d, --draft             Filter by draft state
-  -H, --head string       Filter by head branch ("<owner>:<branch>" syntax not supported)
-  -q, --jq expression     Filter JSON output using a jq expression
-      --json fields       Output JSON with the specified fields
-  -l, --label strings     Filter by label
-  -L, --limit int         Maximum number of items to fetch (default 30)
-  -S, --search query      Search pull requests with query
-  -s, --state string      Filter by state: {open|closed|merged|all} (default "open")
-  -t, --template string   Format JSON output using a Go template; see "gh help formatting"
-  -w, --web               List pull requests in the web browser
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-JSON FIELDS
-  additions, assignees, author, autoMergeRequest, baseRefName, baseRefOid, body,
-  changedFiles, closed, closedAt, closingIssuesReferences, comments, commits,
-  createdAt, deletions, files, fullDatabaseId, headRefName, headRefOid,
-  headRepository, headRepositoryOwner, id, isCrossRepository, isDraft, labels,
-  latestReviews, maintainerCanModify, mergeCommit, mergeStateStatus, mergeable,
-  mergedAt, mergedBy, milestone, number, potentialMergeCommit, projectCards,
-  projectItems, reactionGroups, reviewDecision, reviewRequests, reviews, state,
-  statusCheckRollup, title, updatedAt, url
-
-EXAMPLES
-  # List PRs authored by you
-  $ gh pr list --author "@me"
-  
-  # List PRs with a specific head branch name
-  $ gh pr list --head "typo"
-  
-  # List only PRs with all of the given labels
-  $ gh pr list --label bug --label "priority 1"
-  
-  # Filter PRs using search syntax
-  $ gh pr list --search "status:success review:required"
-  
-  # Find a PR that introduced a given commit
-  $ gh pr list --search "<SHA>" --state merged
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr diff
-
-View changes in a pull request.
-
-Without an argument, the pull request that belongs to the current branch
-is selected.
-
-With `--web` flag, open the pull request diff in a web browser instead.
-
-
-USAGE
-  gh pr diff [<number> | <url> | <branch>] [flags]
-
-FLAGS
-      --color string   Use color in diff output: {always|never|auto} (default "auto")
-      --name-only      Display only names of changed files
-      --patch          Display diff in patch format
-  -w, --web            Open the pull request diff in the browser
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr merge
-
-Merge a pull request on GitHub.
-
-Without an argument, the pull request that belongs to the current branch
-is selected.
-
-When targeting a branch that requires a merge queue, no merge strategy is required.
-If required checks have not yet passed, auto-merge will be enabled.
-If required checks have passed, the pull request will be added to the merge queue.
-To bypass a merge queue and merge directly, pass the `--admin` flag.
-
-
-USAGE
-  gh pr merge [<number> | <url> | <branch>] [flags]
-
-FLAGS
-      --admin                   Use administrator privileges to merge a pull request that does not meet requirements
-  -A, --author-email text       Email text for merge commit author
-      --auto                    Automatically merge only after necessary requirements are met
-  -b, --body text               Body text for the merge commit
-  -F, --body-file file          Read body text from file (use "-" to read from standard input)
-  -d, --delete-branch           Delete the local and remote branch after merge
-      --disable-auto            Disable auto-merge for this pull request
-      --match-head-commit SHA   Commit SHA that the pull request head must match to allow merge
-  -m, --merge                   Merge the commits with the base branch
-  -r, --rebase                  Rebase the commits onto the base branch
-  -s, --squash                  Squash the commits into one commit and merge it into the base branch
-  -t, --subject text            Subject text for the merge commit
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr review 
-
-Add a review to a pull request.
-
-Without an argument, the pull request that belongs to the current branch is reviewed.
-
-
-USAGE
-  gh pr review [<number> | <url> | <branch>] [flags]
-
-FLAGS
-  -a, --approve           Approve pull request
-  -b, --body string       Specify the body of a review
-  -F, --body-file file    Read body text from file (use "-" to read from standard input)
-  -c, --comment           Comment on a pull request
-  -r, --request-changes   Request changes on a pull request
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-EXAMPLES
-  # Approve the pull request of the current branch
-  $ gh pr review --approve
-  
-  # Leave a review comment for the current branch
-  $ gh pr review --comment -b "interesting"
-  
-  # Add a review for a specific pull request
-  $ gh pr review 123
-  
-  # Request changes on a specific pull request
-  $ gh pr review 123 -r -b "needs more ASCII art"
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr checkout
-
-Check out a pull request in git
-
-USAGE
-  gh pr checkout [<number> | <url> | <branch>] [flags]
-
-FLAGS
-  -b, --branch string        Local branch name to use (default [the name of the head branch])
-      --detach               Checkout PR with a detached HEAD
-  -f, --force                Reset the existing local branch to the latest state of the pull request
-      --recurse-submodules   Update all submodules after checkout
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-EXAMPLES
-  # Interactively select a PR from the 10 most recent to check out
-  $ gh pr checkout
-  
-  # Checkout a specific PR
-  $ gh pr checkout 32
-  $ gh pr checkout https://github.com/OWNER/REPO/pull/32
-  $ gh pr checkout feature
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-  ## gh pr close
-
-  Close a pull request
-
-USAGE
-  gh pr close {<number> | <url> | <branch>} [flags]
-
-FLAGS
-  -c, --comment string   Leave a closing comment
-  -d, --delete-branch    Delete the local and remote branch after close
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-## gh pr comment
-
-Add a comment to a GitHub pull request.
-
-Without the body text supplied through flags, the command will interactively
-prompt for the comment text.
-
-
-USAGE
-  gh pr comment [<number> | <url> | <branch>] [flags]
-
-FLAGS
-  -b, --body text        The comment body text
-  -F, --body-file file   Read body text from file (use "-" to read from standard input)
-      --create-if-none   Create a new comment if no comments are found. Can be used only with --edit-last
-      --delete-last      Delete the last comment of the current user
-      --edit-last        Edit the last comment of the current user
-  -e, --editor           Skip prompts and open the text editor to write the body in
-  -w, --web              Open the web browser to write the comment
-      --yes              Skip the delete confirmation prompt when --delete-last is provided
-
-INHERITED FLAGS
-      --help                     Show help for command
-  -R, --repo [HOST/]OWNER/REPO   Select another repository using the [HOST/]OWNER/REPO format
-
-EXAMPLES
-  $ gh pr comment 13 --body "Hi from GitHub CLI"
-
-LEARN MORE
-  Use `gh <command> <subcommand> --help` for more information about a command.
-  Read the manual at https://cli.github.com/manual
-  Learn about exit codes using `gh help exit-codes`
-  Learn about accessibility experiences using `gh help accessibility`
-
-
-

.env.example

@@ -1,12 +0,0 @@
-PUBLIC_API_URL=https://api.roadmap.sh
-PUBLIC_AVATAR_BASE_URL=https://dodrc8eu8m09s.cloudfront.net/avatars
-PUBLIC_EDITOR_APP_URL=https://draw.roadmap.sh
-PUBLIC_COURSE_APP_URL=http://localhost:5173
-
-PUBLIC_STRIPE_INDIVIDUAL_MONTHLY_PRICE_ID=
-PUBLIC_STRIPE_INDIVIDUAL_YEARLY_PRICE_ID=
-
-PUBLIC_STRIPE_INDIVIDUAL_MONTHLY_PRICE_AMOUNT=10
-PUBLIC_STRIPE_INDIVIDUAL_YEARLY_PRICE_AMOUNT=100
-
-ROADMAP_API_KEY=

.github/ISSUE_TEMPLATE/01-suggest-changes.yml

@@ -1,25 +0,0 @@
-name: "✍️ ​ ​Missing or Deprecated Roadmap Topics"
-description: Help us improve the roadmaps by suggesting changes
-labels: [topic-change]
-assignees: []
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to help us improve the roadmaps with your suggestions.
-  - type: input
-    id: url
-    attributes:
-      label: Roadmap URL
-      description: Please provide the URL of the roadmap you are suggesting changes to.
-      placeholder: https://roadmap.sh
-    validations:
-      required: true
-  - type: textarea
-    id: roadmap-suggestions
-    attributes:
-      label: Suggestions
-      description: What changes would you like to suggest?
-      placeholder: Enter your suggestions here.
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/02-bug-report.yml

@@ -1,42 +0,0 @@
-name: "🐛 ​ ​Bug Report"
-description: Report an issue or possible bug
-labels: [bug]
-assignees: []
-body:
-  - type: input
-    id: url
-    attributes:
-      label: What is the URL where the issue is happening
-      placeholder: https://roadmap.sh
-    validations:
-      required: true
-  - type: dropdown
-    id: browsers
-    attributes:
-      label: What browsers are you seeing the problem on?
-      multiple: true
-      options:
-        - Firefox
-        - Chrome
-        - Safari
-        - Microsoft Edge
-        - Other
-  - type: textarea
-    id: bug-description
-    attributes:
-      label: Describe the Bug
-      description: A clear and concise description of what the bug is.
-    validations:
-      required: true
-  - type: textarea
-    id: logs
-    attributes:
-      label: Output from browser console (if any)
-      description: Please copy and paste any relevant log output.
-  - type: checkboxes
-    id: will-pr
-    attributes:
-      label: Participation
-      options:
-        - label:  I am willing to submit a pull request for this issue.
-          required: false

.github/ISSUE_TEMPLATE/03-feature-suggestion.yml

@@ -1,12 +0,0 @@
-name: "✨ ​ ​Feature Suggestion"
-description: Is there a feature you'd like to see on Roadmap.sh? Let us know!
-labels: [feature request]
-assignees: []
-body:
-  - type: textarea
-    id: feature-description
-    attributes:
-      label: Feature Description
-      description: Please provide a detailed description of the feature you are suggesting and how it would help you/others.
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/04-roadmap-contribution.yml

@@ -1,25 +0,0 @@
-name: "🙏 ​ ​Submit a Roadmap"
-description: Help us launch a new roadmap with your expertise.
-labels: [roadmap contribution]
-assignees: []
-body:
-  - type: markdown
-    attributes:
-      value: |
-        Thanks for taking the time to submit a roadmap! Please fill out the information below and we'll get back to you as soon as we can.
-  - type: input
-    id: roadmap-title
-    attributes:
-      label: What is the title of the roadmap you are submitting?
-      placeholder: e.g. Roadmap to learn Data Science
-    validations:
-      required: true
-  - type: textarea
-    id: roadmap-description
-    attributes:
-      label: Roadmap Link
-      description: Please create the roadmap [using our roadmap editor](https://twitter.com/kamrify/status/1708293162693767426) and submit the roadmap link.
-      placeholder: |
-          https://roadmap.sh/xyz
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/05-something-else.yml

@@ -1,12 +0,0 @@
-name: "🤷‍♂️ ​ ​Something else"
-description: If none of the above templates fit your needs, please use this template to submit your issue.
-labels: []
-assignees: []
-body:
-  - type: textarea
-    id: issue-description
-    attributes:
-      label: Detailed Description
-      description: Please provide a detailed description of the issue.
-    validations:
-      required: true

.github/ISSUE_TEMPLATE/config.yml

@@ -1,14 +0,0 @@
-blank_issues_enabled: false
-contact_links:
-  - name: ✋ ​ ​Roadmap Request
-    url: https://roadmap.sh/discord
-    about: Please do not open issues with roadmap requests, hop onto the discord server for that.
-  - name: 📝 ​ ​Typo or Grammatical Mistake
-    url: https://github.com/kamranahmedse/developer-roadmap/tree/master/src/data
-    about: Please submit a pull request instead of reporting it as an issue.
-  - name: 💬 ​ ​Chat on Discord
-    url: https://roadmap.sh/discord
-    about: Join the community on our Discord server.
-  - name: 🤝 ​ ​Guidance
-    url: https://roadmap.sh/discord
-    about: Join the community in our Discord server.

.github/workflows/close-feedback-pr.yml

@@ -1,50 +0,0 @@
-name: Close PRs with Feedback
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '0 0 * * *'
-jobs:
-  close-pr:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Close PR if it has label "feedback left" and no changes in 7 days
-        uses: actions/github-script@v3
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          script: |
-            const { data: pullRequests } = await github.pulls.list({
-              owner: context.repo.owner,
-              repo: context.repo.repo,
-              state: 'open',
-              base: 'master',
-            });
-
-            for (const pullRequest of pullRequests) {
-              const { data: labels } = await github.issues.listLabelsOnIssue({
-                owner: context.repo.owner,
-                repo: context.repo.repo,
-                issue_number: pullRequest.number,
-              });
-
-              const feedbackLabel = labels.find((label) => label.name === 'feedback left');
-              if (feedbackLabel) {
-                const lastUpdated = new Date(pullRequest.updated_at);
-                const sevenDaysAgo = new Date();
-                sevenDaysAgo.setDate(sevenDaysAgo.getDate() - 7);
-
-                if (lastUpdated < sevenDaysAgo) {
-                  await github.issues.createComment({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    issue_number: pullRequest.number,
-                    body: 'Closing this PR because there has been no activity for the past 7 days. Feel free to reopen if you have any feedback.',
-                  });
-                  await github.pulls.update({
-                    owner: context.repo.owner,
-                    repo: context.repo.repo,
-                    pull_number: pullRequest.number,
-                    state: 'closed',
-                  });
-                }
-              }
-            }

.github/workflows/cloudfront-api-cache.yml

@@ -1,16 +0,0 @@
-name: Clears API Cloudfront Cache
-on:
-  workflow_dispatch:
-jobs:
-  cloudfront_api_cache:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Clear Cloudfront Caching
-        run: |
-          curl -L \
-            -X POST \
-            -H "Accept: application/vnd.github+json" \
-            -H "Authorization: Bearer ${{ secrets.GH_PAT }}" \
-            -H "X-GitHub-Api-Version: 2022-11-28" \
-            https://api.github.com/repos/roadmapsh/infra-ansible/actions/workflows/playbook.yml/dispatches \
-            -d '{ "ref":"master", "inputs": { "playbook": "roadmap_web.yml", "tags": "cloudfront-api", "is_verbose": false } }'

.github/workflows/cloudfront-fe-cache.yml

@@ -1,16 +0,0 @@
-name: Clears Frontend Cloudfront Cache
-on:
-  workflow_dispatch:
-jobs:
-  cloudfront_fe_cache:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Clear Cloudfront Caching
-        run: |
-          curl -L \
-            -X POST \
-            -H "Accept: application/vnd.github+json" \
-            -H "Authorization: Bearer ${{ secrets.GH_PAT }}" \
-            -H "X-GitHub-Api-Version: 2022-11-28" \
-            https://api.github.com/repos/roadmapsh/infra-ansible/actions/workflows/playbook.yml/dispatches \
-            -d '{ "ref":"master", "inputs": { "playbook": "roadmap_web.yml", "tags": "cloudfront,cloudfront-course", "is_verbose": false } }'

.github/workflows/deploy.yml

@@ -0,0 +1,36 @@
+name: Deployment to GH Pages
+on:
+  push:
+    branches: [ master ]
+env:
+  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+  PAT: ${{ secrets.PAT }}
+  CI: true
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+      with:
+        persist-credentials: false
+    - uses: actions/setup-node@v1
+      with:
+        node-version: 18
+    - run: git config --global url."https://${{ secrets.PAT }}@github.com/".insteadOf ssh://git@github.com/
+    - uses: pnpm/action-setup@v2.2.2
+      with:
+        version: 7.13.4
+    - name: Setup Environment
+      run: |
+        pnpm install
+    - name: Generate meta and build
+      run: |
+        npm run build
+        touch ./dist/.nojekyll
+        echo 'roadmap.sh' > ./dist/CNAME
+    - name: Deploy to GH Pages
+      run: |
+        git config user.email "kamranahmed.se@gmail.com"
+        git config user.name "Kamran Ahmed"
+        git remote set-url origin https://x-access-token:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}.git
+        npm run deploy

.github/workflows/deployment.yml

@@ -1,75 +0,0 @@
-name: Deploy to EC2
-
-on:
-  workflow_dispatch:
-
-jobs:
-  deploy:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout Repository
-        uses: actions/checkout@v4
-        with:
-          fetch-depth: 2
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-      - uses: pnpm/action-setup@v4.0.0
-        with:
-          version: 9
-
-      # -------------------
-      # Setup configuration
-      # -------------------
-      - name: Prepare configuration files
-        run: |
-          git clone https://${{ secrets.GH_PAT }}@github.com/roadmapsh/infra-config.git configuration --depth 1
-      - name: Copy configuration files
-        run: |
-          cp configuration/dist/github/developer-roadmap.env .env
-
-      # -----------------
-      # Prepare the Build
-      # -----------------
-      - name: Install Dependencies
-        run: |
-          pnpm install
-
-      - name: Generate Production Build
-        run: |
-          git clone https://${{ secrets.GH_PAT }}@github.com/roadmapsh/web-draw.git .temp/web-draw --depth 1
-          npm run generate-renderer
-          npm run compress:images
-          npm run build
-
-      # --------------------
-      # Deploy to EC2
-      # --------------------
-      - uses: webfactory/ssh-agent@v0.7.0
-        with:
-          ssh-private-key: ${{ secrets.EC2_PRIVATE_KEY }}
-      - name: Deploy Application to EC2
-        run: |
-          rsync -apvz --delete --no-times --exclude "configuration" -e "ssh -o StrictHostKeyChecking=no" -p ./ ${{ secrets.EC2_USERNAME }}@${{ secrets.EC2_HOST }}:/var/www/roadmap.sh/
-      - name: Restart PM2
-        uses: appleboy/ssh-action@master
-        with:
-          host: ${{ secrets.EC2_HOST }}
-          username: ${{ secrets.EC2_USERNAME }}
-          key: ${{ secrets.EC2_PRIVATE_KEY }}
-          script: |
-            cd /var/www/roadmap.sh
-            sudo pm2 restart web-roadmap
-
-      # ----------------------
-      # Clear cloudfront cache
-      # ----------------------
-      - name: Clear Cloudfront Caching
-        run: |
-          curl -L \
-            -X POST \
-            -H "Accept: application/vnd.github+json" \
-            -H "Authorization: Bearer ${{ secrets.GH_PAT }}" \
-            -H "X-GitHub-Api-Version: 2022-11-28" \
-            https://api.github.com/repos/roadmapsh/infra-ansible/actions/workflows/playbook.yml/dispatches \
-            -d '{ "ref":"master", "inputs": { "playbook": "roadmap_web.yml", "tags": "cloudfront", "is_verbose": false } }'

.github/workflows/label-issue.yml

@@ -1,40 +0,0 @@
-name: Label Issue
-
-on:
-  issues:
-    types: [ opened, edited ]
-  
-jobs:
-  label-topic-change-issue:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Add Labels To Issue
-        uses: actions/github-script@v7
-        with:
-          github-token: ${{ secrets.GITHUB_TOKEN }}
-          script: |
-            const issue = context.payload.issue;
-            const roadmapUrl = issue.body.match(/https?:\/\/roadmap.sh\/[^ ]+/);
-
-            // if the issue is labeled as a topic-change, add the roadmap slug as a label
-            if (issue.labels.some(label => label.name === 'topic-change')) {
-              if (roadmapUrl) {
-                const roadmapSlug = new URL(roadmapUrl[0]).pathname.replace(/\//, '');
-                github.rest.issues.addLabels({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issue.number,
-                  labels: [roadmapSlug]
-                });
-              }
-            
-              // Close the issue if it has no roadmap URL
-              if (!roadmapUrl) {
-                github.rest.issues.update({
-                  owner: context.repo.owner,
-                  repo: context.repo.repo,
-                  issue_number: issue.number,
-                  state: 'closed'
-                });
-              }
-            }

.github/workflows/refresh-roadmap-content-json.yml

@@ -1,52 +0,0 @@
-name: Refresh Roadmap Content JSON
-
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '0 0 * * *'
-
-jobs:
-  refresh-content:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup pnpm@v9
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-          run_install: false
-
-      - name: Setup Node.js Version 20 (LTS)
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: 'pnpm'
-
-      - name: Install Dependencies and Generate Content JSON
-        run: |
-          pnpm install
-          npm run generate:roadmap-content-json
-      
-      - name: Create PR
-        uses: peter-evans/create-pull-request@v7
-        with:
-          delete-branch: false
-          branch: "chore/update-content-json"
-          base: "master"
-          labels: |
-            dependencies
-            automated pr
-          reviewers: kamranahmedse
-          commit-message: "chore: update roadmap content json"
-          title: "Updated Roadmap Content JSON - Automated"
-          body: |
-            ## Updated Roadmap Content JSON
-            
-            > [!IMPORTANT]
-            > This PR Updates the Roadmap Content JSON files stored in the `public` directory.
-            >
-            > Commit: ${{ github.sha }}
-            > Workflow Path: ${{ github.workflow_ref }}
-
-            **Please Review the Changes and Merge the PR if everything is fine.**

.github/workflows/sync-content-to-repo.yml

@@ -1,66 +0,0 @@
-name: Sync Content to Repo
-
-on:
-  workflow_dispatch:
-    inputs:
-      roadmap_slug:
-        description: "The ID of the roadmap to sync"
-        required: true
-        default: "__default__"
-
-jobs:
-  sync-content:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup pnpm@v9
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-          run_install: false
-
-      - name: Setup Node.js Version 20 (LTS)
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: 'pnpm'
-
-      - name: Install Dependencies and Sync Content
-        run: |
-          echo "Installing Dependencies"
-          pnpm install
-          echo "Syncing Content to Repo"
-          npm run sync:content-to-repo -- --roadmap-slug=${{ inputs.roadmap_slug }} --secret=${{ secrets.GH_SYNC_SECRET }}
-
-      - name: Check for changes
-        id: verify-changed-files
-        run: |
-          if [ -n "$(git status --porcelain)" ]; then
-            echo "changed=true" >> $GITHUB_OUTPUT
-          else
-            echo "changed=false" >> $GITHUB_OUTPUT
-          fi
-      
-      - name: Create PR
-        if: steps.verify-changed-files.outputs.changed == 'true'
-        uses: peter-evans/create-pull-request@v7
-        with:
-          delete-branch: false
-          branch: "chore/sync-content-to-repo-${{ inputs.roadmap_slug }}"
-          base: "master"
-          labels: |
-            automated pr
-          reviewers: jcanalesluna,kamranahmedse
-          commit-message: "chore: sync content to repo"
-          title: "chore: sync content to repository - ${{ inputs.roadmap_slug }}"
-          body: |
-            ## Sync Content to Repo
-            
-            > [!IMPORTANT]
-            > This PR Syncs the Content to the Repo for the Roadmap: ${{ inputs.roadmap_slug }}
-            >
-            > Commit: ${{ github.sha }}
-            > Workflow Path: ${{ github.workflow_ref }}
-
-            **Please Review the Changes and Merge the PR if everything is fine.** 

.github/workflows/sync-repo-to-database.yml

@@ -1,67 +0,0 @@
-name: Sync on Roadmap Changes
-
-on:
-  push:
-    branches:
-      - master
-    paths:
-      - 'src/data/roadmaps/**'
-
-jobs:
-  sync-on-changes:
-    runs-on: ubuntu-latest
-    if: github.actor != 'github-actions[bot]' && github.actor != 'dependabot[bot]'
-    steps:
-      - uses: actions/checkout@v4
-        with:
-          fetch-depth: 2  # Fetch previous commit to compare changes
-
-      - name: Setup pnpm@v9
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-          run_install: false
-
-      - name: Setup Node.js Version 20 (LTS)
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          cache: 'pnpm'
-
-      - name: Get changed files
-        id: changed-files
-        run: |
-          echo "Getting changed files in /src/data/roadmaps/"
-          
-          # Get changed files between HEAD and previous commit
-          CHANGED_FILES=$(git diff --name-only HEAD~1 HEAD -- src/data/roadmaps/)
-          
-          if [ -z "$CHANGED_FILES" ]; then
-            echo "No changes found in roadmaps directory"
-            echo "has_changes=false" >> $GITHUB_OUTPUT
-            exit 0
-          fi
-          
-          echo "Changed files:"
-          echo "$CHANGED_FILES"
-          
-          # Convert to space-separated list for the script
-          CHANGED_FILES_LIST=$(echo "$CHANGED_FILES" | tr '\n' ',')
-          
-          echo "has_changes=true" >> $GITHUB_OUTPUT
-          echo "changed_files=$CHANGED_FILES_LIST" >> $GITHUB_OUTPUT
-
-      - name: Install Dependencies
-        if: steps.changed-files.outputs.has_changes == 'true'
-        run: |
-          echo "Installing Dependencies"
-          pnpm install
-
-      - name: Run sync script with changed files
-        if: steps.changed-files.outputs.has_changes == 'true'
-        run: |
-          echo "Running sync script for changed roadmap files"
-          echo "Changed files: ${{ steps.changed-files.outputs.changed_files }}"
-          
-          # Run your script with the changed file paths
-          npm run sync:repo-to-database -- --files="${{ steps.changed-files.outputs.changed_files }}" --secret=${{ secrets.GH_SYNC_SECRET }}

.github/workflows/update-deps.yml

@@ -0,0 +1,38 @@
+name: Update dependencies
+
+on:
+  workflow_dispatch: # allow manual run
+  schedule:
+    - cron: '0 0 * * 0' # every sunday at midnight
+
+jobs:
+  upgrade-deps:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 18
+      - uses: pnpm/action-setup@v2.2.2
+        with:
+          version: 7.13.4
+      - name: Upgrade dependencies
+        run: |
+          pnpm install
+          npm run upgrade
+          pnpm install --lockfile-only
+      - name: Create PR
+        uses: peter-evans/create-pull-request@v4
+        with:
+          delete-branch: false
+          branch: "update-deps"
+          base: "master"
+          labels: |
+            dependencies
+            automated pr
+          reviewers: kamranahmedse
+          commit-message: "chore: update dependencies to latest"
+          title: "Upgrade dependencies to latest"
+          body: |
+            Updates all dependencies to latest versions.
+            Please review the changes and merge if everything looks good.

.github/workflows/upgrade-dependencies.yml

@@ -1,51 +0,0 @@
-name: Upgrade Dependencies
-
-on:
-  workflow_dispatch:
-  schedule:
-    - cron: '0 0 * * 0'
-
-jobs:
-  upgrade-deps:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-
-      - name: Setup Node.js Version 20 (LTS)
-        uses: actions/setup-node@v4
-        with:
-          node-version: 20
-
-      - name: Setup pnpm@v9
-        uses: pnpm/action-setup@v4
-        with:
-          version: 9
-
-      - name: Install & Upgrade Dependencies
-        run: |
-          pnpm install
-          npm run upgrade
-          pnpm install --lockfile-only
-
-      - name: Create Pull Request
-        uses: peter-evans/create-pull-request@v7
-        with:
-          delete-branch: false
-          branch: "update-deps"
-          base: "master"
-          labels: |
-            dependencies
-            automated pr
-          reviewers: kamranahmedse
-          commit-message: "chore: update dependencies to latest"
-          title: "Upgrade Dependencies To Latest - Automated"
-          body: |
-            ## Updated all Dependencies to Latest Versions.
-
-            > [!IMPORTANT]
-            > This PR Upgrades the Dependencies to the their latest versions.
-            >
-            > Commit: ${{ github.sha }}
-            > Workflow Path: ${{ github.workflow_ref }}
-
-            **Please Review the Changes and Merge the PR if everything is fine.**

.gitignore

@@ -1,7 +1,3 @@
-.idea
-.temp
-.astro
-
 # build output
 dist/
 .output/
@@ -9,7 +5,7 @@ dist/
 # dependencies
 node_modules/
 
-scripts/developer-roadmap
+bin/developer-roadmap
 
 # logs
 npm-debug.log*
@@ -27,7 +23,4 @@ pnpm-debug.log*
 /test-results/
 /playwright-report/
 /playwright/.cache/
-tests-examples
-*.csveditor/
-
-packages/editor
+tests-examples

.npmrc

@@ -1,2 +0,0 @@
-auto-install-peers=true
-strict-peer-dependencies=false

.prettierignore

@@ -1,7 +0,0 @@
-app-dist
-dist
-.idea
-.github
-public
-node_modules
-pnpm-lock.yaml

.prettierrc.cjs

@@ -1,18 +0,0 @@
-module.exports = {
-  semi: true,
-  singleQuote: true,
-  overrides: [
-    {
-      files: '*.astro',
-      options: {
-        parser: 'astro',
-        singleQuote: true,
-        jsxSingleQuote: true,
-      },
-    },
-  ],
-  plugins: [
-    require.resolve('prettier-plugin-astro'),
-    'prettier-plugin-tailwindcss',
-  ],
-};

.vscode/settings.json

@@ -1,14 +0,0 @@
-{
-  "prettier.documentSelectors": ["**/*.astro"],
-  "[astro]": {
-    "editor.defaultFormatter": "esbenp.prettier-vscode"
-  },
-  "tailwindCSS.experimental.classRegex": [
-    ["\\b\\w+[cC]lassName\\s*=\\s*[\"']([^\"']*)[\"']"],
-    ["\\b\\w+[cC]lassName\\s*=\\s*`([^`]*)`"],
-    ["[\\w]+[cC]lassName[\"']?\\s*:\\s*[\"']([^\"']*)[\"']"],
-    ["[\\w]+[cC]lassName[\"']?\\s*:\\s*`([^`]*)`"],
-    ["cva\\(((?:[^()]|\\([^()]*\\))*)\\)", "[\"'`]([^\"'`]*).*?[\"'`]"],
-    ["cx\\(((?:[^()]|\\([^()]*\\))*)\\)", "(?:'|\"|`)([^']*)(?:'|\"|`)"]
-  ]
-}

astro.config.mjs

@@ -1,31 +1,13 @@
 // https://astro.build/config
 import sitemap from '@astrojs/sitemap';
-import node from '@astrojs/node';
+import tailwind from '@astrojs/tailwind';
+import compress from 'astro-compress';
 import { defineConfig } from 'astro/config';
 import rehypeExternalLinks from 'rehype-external-links';
 import { serializeSitemap, shouldIndexPage } from './sitemap.mjs';
-import tailwindcss from '@tailwindcss/vite';
 
-import react from '@astrojs/react';
-
-// https://astro.build/config
 export default defineConfig({
-  site: 'https://roadmap.sh/',
-  redirects: {
-    '/devops/devops-engineer': {
-      status: 301,
-      destination: '/devops',
-    },
-    '/ai-tutor': {
-      status: 301,
-      destination: '/ai',
-    },
-  },
-  vite: {
-    server: {
-      allowedHosts: ['roadmap.sh', 'port3k.kamranahmed.info'],
-    },
-  },
+  site: 'https://roadmap.sh',
   markdown: {
     shikiConfig: {
       theme: 'dracula',
@@ -35,42 +17,26 @@ export default defineConfig({
         rehypeExternalLinks,
         {
           target: '_blank',
-          rel: function (element) {
-            const href = element.properties.href;
-            const whiteListedStarts = [
-              '/',
-              '#',
-              'mailto:',
-              'https://github.com/kamranahmedse',
-              'https://thenewstack.io',
-              'https://kamranahmed.info',
-              'https://roadmap.sh',
-            ];
-            if (whiteListedStarts.some((start) => href.startsWith(start))) {
-              return [];
-            }
-            return 'noopener noreferrer nofollow';
-          },
         },
       ],
     ],
   },
-  output: 'server',
-  adapter: node({
-    mode: 'standalone',
-  }),
-  trailingSlash: 'never',
+  build: {
+    format: 'file',
+  },
   integrations: [
+    tailwind({
+      config: {
+        applyBaseStyles: false,
+      },
+    }),
     sitemap({
       filter: shouldIndexPage,
       serialize: serializeSitemap,
     }),
-    react(),
+    compress({
+      css: false,
+      js: false,
+    }),
   ],
-  vite: {
-    plugins: [tailwindcss()],
-    ssr: {
-      noExternal: [/^@roadmapsh\/editor.*$/],
-    },
-  },
 });

bin/best-practice-content.cjs

@@ -0,0 +1,144 @@
+const fs = require('fs');
+const path = require('path');
+
+const CONTENT_DIR = path.join(__dirname, '../content');
+// Directory containing the best-practices
+const BEST_PRACTICE_CONTENT_DIR = path.join(__dirname, '../src/best-practices');
+const bestPracticeId = process.argv[2];
+
+const allowedBestPracticeId = fs.readdirSync(BEST_PRACTICE_CONTENT_DIR);
+if (!bestPracticeId) {
+  console.error('bestPractice is required');
+  process.exit(1);
+}
+
+if (!allowedBestPracticeId.includes(bestPracticeId)) {
+  console.error(`Invalid best practice key ${bestPracticeId}`);
+  console.error(`Allowed keys are ${allowedBestPracticeId.join(', ')}`);
+  process.exit(1);
+}
+
+// Directory holding the best parctice content files
+const bestPracticeDirName = fs
+  .readdirSync(BEST_PRACTICE_CONTENT_DIR)
+  .find((dirName) => dirName.replace(/\d+-/, '') === bestPracticeId);
+
+if (!bestPracticeDirName) {
+  console.error('Best practice directory not found');
+  process.exit(1);
+}
+
+const bestPracticeDirPath = path.join(BEST_PRACTICE_CONTENT_DIR, bestPracticeDirName);
+const bestPracticeContentDirPath = path.join(
+  BEST_PRACTICE_CONTENT_DIR,
+  bestPracticeDirName,
+  'content'
+);
+
+// If best practice content already exists do not proceed as it would override the files
+if (fs.existsSync(bestPracticeContentDirPath)) {
+  console.error(`Best Practice content already exists @ ${bestPracticeContentDirPath}`);
+  process.exit(1);
+}
+
+function prepareDirTree(control, dirTree) {
+  // Directories are only created for groups
+  if (control.typeID !== '__group__') {
+    return;
+  }
+
+  // e.g. 104-testing-your-apps:other-options
+  const controlName = control?.properties?.controlName || '';
+
+  // No directory for a group without control name
+  if (!controlName || controlName.startsWith('check:') || controlName.startsWith('ext_link:')) {
+    return;
+  }
+
+  // e.g. ['testing-your-apps', 'other-options']
+  const dirParts = controlName.split(':');
+
+  // Nest the dir path in the dirTree
+  let currDirTree = dirTree;
+  dirParts.forEach((dirPart) => {
+    currDirTree[dirPart] = currDirTree[dirPart] || {};
+    currDirTree = currDirTree[dirPart];
+  });
+
+  const childrenControls = control.children.controls.control;
+  // No more children
+  if (childrenControls.length) {
+    childrenControls.forEach((childControl) => {
+      prepareDirTree(childControl, dirTree);
+    });
+  }
+
+  return { dirTree };
+}
+
+const bestPractice = require(path.join(__dirname, `../public/jsons/best-practices/${bestPracticeId}`));
+const controls = bestPractice.mockup.controls.control;
+
+// Prepare the dir tree that we will be creating
+const dirTree = {};
+
+controls.forEach((control) => {
+  prepareDirTree(control, dirTree);
+});
+
+/**
+ * @param parentDir Parent directory in which directory is to be created
+ * @param dirTree Nested dir tree to be created
+ * @param filePaths The mapping from groupName to file path
+ */
+function createDirTree(parentDir, dirTree, filePaths = {}) {
+  const childrenDirNames = Object.keys(dirTree);
+  const hasChildren = childrenDirNames.length !== 0;
+
+  // @todo write test for this, yolo for now
+  const groupName = parentDir
+    .replace(bestPracticeContentDirPath, '') // Remove base dir path
+    .replace(/(^\/)|(\/$)/g, '') // Remove trailing slashes
+    .replaceAll('/', ':') // Replace slashes with `:`
+    .replace(/:\d+-/, ':');
+
+  const humanizedGroupName = groupName
+    .split(':')
+    .pop()
+    ?.replaceAll('-', ' ')
+    .replace(/^\w/, ($0) => $0.toUpperCase());
+
+  // If no children, create a file for this under the parent directory
+  if (!hasChildren) {
+    let fileName = `${parentDir}.md`;
+    fs.writeFileSync(fileName, `# ${humanizedGroupName}`);
+
+    filePaths[groupName || 'home'] = fileName.replace(CONTENT_DIR, '');
+    return filePaths;
+  }
+
+  // There *are* children, so create the parent as a directory
+  // and create `index.md` as the content file for this
+  fs.mkdirSync(parentDir);
+
+  let readmeFilePath = path.join(parentDir, 'index.md');
+  fs.writeFileSync(readmeFilePath, `# ${humanizedGroupName}`);
+
+  filePaths[groupName || 'home'] = readmeFilePath.replace(CONTENT_DIR, '');
+
+  // For each of the directory names, create a
+  // directory inside the given directory
+  childrenDirNames.forEach((dirName) => {
+    createDirTree(
+      path.join(parentDir, dirName),
+      dirTree[dirName],
+      filePaths
+    );
+  });
+
+  return filePaths;
+}
+
+// Create directories and get back the paths for created directories
+createDirTree(bestPracticeContentDirPath, dirTree);
+console.log('Created best practice content directory structure');

bin/compress-jsons.cjs

@@ -0,0 +1,19 @@
+const fs = require('node:fs');
+const path = require('node:path');
+
+const jsonsDir = path.join(process.cwd(), 'public/jsons');
+const childJsonDirs = fs.readdirSync(jsonsDir);
+
+childJsonDirs.forEach((childJsonDir) => {
+  const fullChildJsonDirPath = path.join(jsonsDir, childJsonDir);
+  const jsonFiles = fs.readdirSync(fullChildJsonDirPath);
+
+  jsonFiles.forEach((jsonFileName) => {
+    console.log(`Compressing ${jsonFileName}...`);
+
+    const jsonFilePath = path.join(fullChildJsonDirPath, jsonFileName);
+    const json = require(jsonFilePath);
+
+    fs.writeFileSync(jsonFilePath, JSON.stringify(json));
+  });
+});

bin/readme.md

@@ -0,0 +1,28 @@
+## CLI Tools
+> A bunch of CLI scripts to make the development easier
+
+## `roadmap-links.cjs`
+
+Generates a list of all the resources links in any roadmap file.
+
+## `compress-jsons.cjs`
+
+Compresses all the JSON files in the `public/jsons` folder
+
+## `roadmap-content.cjs`
+
+This command is used to create the content folders and files for the interactivity of the roadmap. You can use the below command to generate the roadmap skeletons inside a roadmap directory:
+
+```bash
+npm run roadmap-content [frontend|backend|devops|...]
+```
+
+For the content skeleton to be generated, we should have proper grouping, and the group names in the project files. You can follow the steps listed below in order to add the meta information to the roadmap.
+
+- Remove all the groups from the roadmaps through the project editor. Select all and press `cmd+shift+g`
+- Identify the boxes that should be clickable and group them together with `cmd+shift+g`
+- Assign the name to the groups.
+  - Group names have the format of `[sort]-[slug]` e.g. `100-internet`. Each group name should start with a number starting from 100 which helps with sorting of the directories and the files. Groups at the same level have the sequential sorting information.
+  - Each groups children have a separate group and have the name similar to `[sort]-[parent-slug]:[child-slug]` where sort refers to the sorting of the `child-slug` and not the parent. Also parent-slug does not need to have the sorting information as a part of slug e.g. if parent was `100-internet` the children would be `100-internet:how-does-the-internet-work`, `101-internet:what-is-http`, `102-internet:browsers`.
+
+

bin/roadmap-content.cjs

@@ -0,0 +1,163 @@
+const fs = require('fs');
+const path = require('path');
+
+const CONTENT_DIR = path.join(__dirname, '../content');
+// Directory containing the roadmaps
+const ROADMAP_CONTENT_DIR = path.join(__dirname, '../src/roadmaps');
+const roadmapId = process.argv[2];
+
+const allowedRoadmapIds = fs.readdirSync(ROADMAP_CONTENT_DIR);
+if (!roadmapId) {
+  console.error('roadmapId is required');
+  process.exit(1);
+}
+
+if (!allowedRoadmapIds.includes(roadmapId)) {
+  console.error(`Invalid roadmap key ${roadmapId}`);
+  console.error(`Allowed keys are ${allowedRoadmapIds.join(', ')}`);
+  process.exit(1);
+}
+
+// Directory holding the roadmap content files
+const roadmapDirName = fs
+  .readdirSync(ROADMAP_CONTENT_DIR)
+  .find((dirName) => dirName.replace(/\d+-/, '') === roadmapId);
+
+if (!roadmapDirName) {
+  console.error('Roadmap directory not found');
+  process.exit(1);
+}
+
+const roadmapDirPath = path.join(ROADMAP_CONTENT_DIR, roadmapDirName);
+const roadmapContentDirPath = path.join(
+  ROADMAP_CONTENT_DIR,
+  roadmapDirName,
+  'content'
+);
+
+// If roadmap content already exists do not proceed as it would override the files
+if (fs.existsSync(roadmapContentDirPath)) {
+  console.error(`Roadmap content already exists @ ${roadmapContentDirPath}`);
+  process.exit(1);
+}
+
+function prepareDirTree(control, dirTree, dirSortOrders) {
+  // Directories are only created for groups
+  if (control.typeID !== '__group__') {
+    return;
+  }
+
+  // e.g. 104-testing-your-apps:other-options
+  const controlName = control?.properties?.controlName || '';
+  // e.g. 104
+  const sortOrder = controlName.match(/^\d+/)?.[0];
+
+  // No directory for a group without control name
+  if (!controlName || !sortOrder) {
+    return;
+  }
+
+  // e.g. testing-your-apps:other-options
+  const controlNameWithoutSortOrder = controlName.replace(/^\d+-/, '');
+  // e.g. ['testing-your-apps', 'other-options']
+  const dirParts = controlNameWithoutSortOrder.split(':');
+
+  // Nest the dir path in the dirTree
+  let currDirTree = dirTree;
+  dirParts.forEach((dirPart) => {
+    currDirTree[dirPart] = currDirTree[dirPart] || {};
+    currDirTree = currDirTree[dirPart];
+  });
+
+  dirSortOrders[controlNameWithoutSortOrder] = Number(sortOrder);
+
+  const childrenControls = control.children.controls.control;
+  // No more children
+  if (childrenControls.length) {
+    childrenControls.forEach((childControl) => {
+      prepareDirTree(childControl, dirTree, dirSortOrders);
+    });
+  }
+
+  return { dirTree, dirSortOrders };
+}
+
+const roadmap = require(path.join(__dirname, `../public/jsons/roadmaps/${roadmapId}`));
+const controls = roadmap.mockup.controls.control;
+
+// Prepare the dir tree that we will be creating and also calculate the sort orders
+const dirTree = {};
+const dirSortOrders = {};
+
+controls.forEach((control) => {
+  prepareDirTree(control, dirTree, dirSortOrders);
+});
+
+/**
+ * @param parentDir Parent directory in which directory is to be created
+ * @param dirTree Nested dir tree to be created
+ * @param sortOrders Mapping from groupName to sort order
+ * @param filePaths The mapping from groupName to file path
+ */
+function createDirTree(parentDir, dirTree, sortOrders, filePaths = {}) {
+  const childrenDirNames = Object.keys(dirTree);
+  const hasChildren = childrenDirNames.length !== 0;
+
+  // @todo write test for this, yolo for now
+  const groupName = parentDir
+    .replace(roadmapContentDirPath, '') // Remove base dir path
+    .replace(/(^\/)|(\/$)/g, '') // Remove trailing slashes
+    .replace(/(^\d+?-)/g, '') // Remove sorting information
+    .replaceAll('/', ':') // Replace slashes with `:`
+    .replace(/:\d+-/, ':');
+
+  const humanizedGroupName = groupName
+    .split(':')
+    .pop()
+    ?.replaceAll('-', ' ')
+    .replace(/^\w/, ($0) => $0.toUpperCase());
+
+  const sortOrder = sortOrders[groupName] || '';
+
+  // Attach sorting information to dirname
+  // e.g. /roadmaps/100-frontend/content/internet
+  // ———> /roadmaps/100-frontend/content/103-internet
+  if (sortOrder) {
+    parentDir = parentDir.replace(/(.+?)([^\/]+)?$/, `$1${sortOrder}-$2`);
+  }
+
+  // If no children, create a file for this under the parent directory
+  if (!hasChildren) {
+    let fileName = `${parentDir}.md`;
+    fs.writeFileSync(fileName, `# ${humanizedGroupName}`);
+
+    filePaths[groupName || 'home'] = fileName.replace(CONTENT_DIR, '');
+    return filePaths;
+  }
+
+  // There *are* children, so create the parent as a directory
+  // and create `index.md` as the content file for this
+  fs.mkdirSync(parentDir);
+
+  let readmeFilePath = path.join(parentDir, 'index.md');
+  fs.writeFileSync(readmeFilePath, `# ${humanizedGroupName}`);
+
+  filePaths[groupName || 'home'] = readmeFilePath.replace(CONTENT_DIR, '');
+
+  // For each of the directory names, create a
+  // directory inside the given directory
+  childrenDirNames.forEach((dirName) => {
+    createDirTree(
+      path.join(parentDir, dirName),
+      dirTree[dirName],
+      dirSortOrders,
+      filePaths
+    );
+  });
+
+  return filePaths;
+}
+
+// Create directories and get back the paths for created directories
+createDirTree(roadmapContentDirPath, dirTree, dirSortOrders);
+console.log('Created roadmap content directory structure');

bin/roadmap-links.cjs

@@ -6,7 +6,7 @@ if (!roadmapId) {
   console.error('Error: roadmapId is required');
 }
 
-const fullPath = path.join(__dirname, `../src/data/roadmaps/${roadmapId}`);
+const fullPath = path.join(__dirname, `../src/roadmaps/${roadmapId}`);
 if (!fs.existsSync(fullPath)) {
   console.error(`Error: path not found: ${fullPath}!`);
   process.exit(1);

code_of_conduct.md

@@ -14,21 +14,21 @@ appearance, race, religion, or sexual identity and orientation.
 Examples of behavior that contributes to creating a positive environment
 include:
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or
+* The use of sexualized language or imagery and unwelcome sexual attention or
   advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
   address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
+* Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Our Responsibilities

contributing.md

@@ -1,150 +1,40 @@
-# ✨ Contribution Guidelines ✨
+# Contribution
 
-First of all, thank you for considering to contribute. Please look at the details below:
+First of all thank you for considering to contribute. Please look at the details below:
 
-- [New Roadmaps](#new-roadmaps)
-- [Existing Roadmaps](#existing-roadmaps)
-- [Adding Projects](#adding-projects)
-- [Adding Content](#adding-content)
-  - [How To Structure Content](#how-to-structure-content)
-- [Guidelines](#guidelines)
-- [Good vs. Not So Good Contributions](#good-vs-not-so-good-contributions)
-- [Local Development](#local-development)
+- [Contribution](#contribution)
+  - [New Roadmaps](#new-roadmaps)
+  - [Existing Roadmaps](#existing-roadmaps)
+  - [Adding Content](#adding-content)
+  - [Guidelines](#guidelines)
 
 ## New Roadmaps
 
-For new roadmaps, you can either:
-
-- Submit a roadmap by providing [a textual roadmap similar to this roadmap](https://gist.github.com/kamranahmedse/98758d2c73799b3a6ce17385e4c548a5) in an [issue](https://github.com/kamranahmedse/developer-roadmap/issues).
-- Create an interactive roadmap yourself using [our roadmap editor](https://draw.roadmap.sh/) & submit the link to that roadmap in an [issue](https://github.com/kamranahmedse/developer-roadmap/issues).
+For new roadmaps, submit a roadmap by providing [a textual roadmap similar to this roadmap](https://gist.github.com/kamranahmedse/98758d2c73799b3a6ce17385e4c548a5) in an issue.
 
 ## Existing Roadmaps
 
 For the existing roadmaps, please follow the details listed for the nature of contribution:
 
-- **Fixing Typos** — Make your changes in the [roadmap markdown file](https://github.com/kamranahmedse/developer-roadmap/tree/master/src/data/roadmaps) and submit a [PR](https://github.com/kamranahmedse/developer-roadmap/pulls).
-- **Adding or Removing Nodes** — Please open an [issue](https://github.com/kamranahmedse/developer-roadmap/issues) with your suggestion.
+- **Fixing Typos** — Make your changes in the [roadmap JSON file](https://github.com/kamranahmedse/developer-roadmap/tree/master/public/jsons)
+- **Adding or Removing Nodes** — Please open an issue with your suggestion.
 
-**Note:** Please note that our goal is **not to have the biggest list of items**. Our goal is to list items or skills most relevant today.
-
-## Adding Projects
-
-If you have a project idea that you think we should add to the roadmap, feel free to open an issue with as many details about the project as possible and the roadmap you think it should be added to.
-
-The detailed format for the issue should be as follows:
-
-```md
-## What is this project about?
-
-(Add an introduction to the project.)
-
-## Skills this Project Covers
-
-(Comma separated list of skills, e.g. Programming Knowledge, Database, etc.)
-
-## Requirements
-
-( Detailed list of requirements, i.e. input, output, hints to help build this, etc.)
-```
-
-Have a look at this project to get an idea of [what we are looking for](https://roadmap.sh/projects/github-user-activity).
+**Note:** Please note that our goal is not to have the biggest list of items. Our goal is to list items or skills most relevant today.
 
 ## Adding Content
 
-Find [the content directory inside the relevant roadmap](https://github.com/kamranahmedse/developer-roadmap/tree/master/src/data/roadmaps). Please keep the following guidelines in mind when submitting content:
+Find [the content directory inside the relevant roadmap](https://github.com/kamranahmedse/developer-roadmap/tree/master/src/roadmaps). Please keep the following guidelines in mind when submitting content:
 
 - Content must be in English.
-- Maximum of 8 links per topic.
-- **No GeeksforGeeks links** — Links to geeksforgeeks.org are not accepted.
-- Follow the below style guide for content.
-
-Please note that we are intentionally keeping the content under the topic popup concise. You MUST always aim to explain the topic simply in a **single paragraph** or so and provide external resources where users can learn more about the topic.
-
-### How To Structure Content
-
-Please adhere to the following style when adding content to a topic:
-
-```md
-# Topic Title
-
-(Content)
-
-Visit the following resources to learn more:
-
-- [@type@Title/Description of Link](Link)
-```
-
-`@type@` must be one of the following and describe the type of content you are adding:
-
-- `@official@`
-- `@opensource@`
-- `@article@`
-- `@course@`
-- `@podcast@`
-- `@video@`
-- `@book@`
-
-It's important to add a valid type, this will help us categorize the content and display it properly on the roadmap. The order of the links based on type is same as above.
+- Put a brief description about the topic on top of the file and the a list of links below with each link having title of the URL.
 
 ## Guidelines
 
-- <p><strong>Please don't use the project for self-promotion!</strong><br/>
-
-  We believe this project is a valuable asset to the developer community, and it includes numerous helpful resources. We kindly ask you to avoid submitting pull requests for the sole purpose of self-promotion. We appreciate contributions that genuinely add value, such as guides from maintainers of well-known frameworks, and will consider accepting these even if they're self authored. Thank you for your understanding and cooperation!
-
-- <p><strong>Adding everything available out there is not the goal!</strong><br/>
-
-  The roadmaps represent the skillset most valuable today, i.e., if you were to enter any of the listed fields today, what would you learn? There might be things that are of-course being used today, but prioritize the things that are most in demand today, e.g., agree that lots of people are using angular.js today, but you wouldn't want to learn that instead of React, Angular, or Vue. Use your critical thinking to filter out non-essential stuff. Give honest arguments for why the resource should be included.</p>
-
-- <p><strong>Do not add things you have not evaluated personally!</strong><br/>
-
+- <p><strong>Adding everything available out there is not the goal!</strong><br /> 
+  The roadmaps represent the skillset most valuable today, i.e., if you were to enter any of the listed fields today, what would you learn?! There might be things that are of-course being used today but prioritize the things that are most in demand today, e.g., agreed that lots of people are using angular.js today but you wouldn't want to learn that instead of React, Angular, or Vue. Use your critical thinking to filter out non-essential stuff. Give honest arguments for why the resource should be included.</p>
+- <p><strong>Do not add things you have not evaluated personally!</strong><br /> 
   Use your critical thinking to filter out non-essential stuff. Give honest arguments for why the resource should be included. Have you read this book? Can you give a short article?</p>
-
 - <p><strong>Create a Single PR for Content Additions</strong></p>
-
-  If you are planning to contribute by adding content to the roadmaps, I recommend you to clone the repository, add content to the [content directory of the roadmap](./src/data/roadmaps/) and create a single PR to make it easier for me to review and merge the PR.
-
-- <p><strong>Write meaningful commit messages</strong><br/>
-
-  Meaningful commit messages help speed up the review process as well as help other contributors gain a good overview of the repositories commit history without having to dive into every commit.
-
-  </p>
-- <p><strong>Look at the existing issues/pull requests before opening new ones</strong></p>
-
-## Good vs. Not So Good Contributions
-
-<strong>Good</strong>
-
-- New Roadmaps.
-- Engaging and fresh content links.
-- Typos and grammatical fixes.
-- Enhanced Existing Content.
-- Content copy in topics that do not have any (or minimal copy exists).
-
-<strong>Not So Good</strong>
-
-- Adding whitespace that doesn't add to the readability of the content.
-- Rewriting content in a way that doesn't add any value.
-- Non-English content.
-- PR's that don't follow our style guide, have no description, and a default title.
-- Links to your own blog articles.
-
-## Local Development
-
-For local development, you can use the following commands:
-
-```bash
-git clone git@github.com:kamranahmedse/developer-roadmap.git --depth 1
-cd developer-roadmap
-pnpm add @roadmapsh/editor@npm:@roadmapsh/dummy-editor -w
-pnpm install
-```
-Run the development server with:
-
-```bash
-pnpm dev
-```
-
-***
-
-Have a look at the [License](./license) file.
+  If you are planning to contribute by adding content to the roadmaps, I recommend you to clone the repository, add content to the [content directory of the roadmap](./content/roadmaps/) and create a single PR to make it easier for me to review and merge the PR.
+- Write meaningful commit messages
+- Look at the existing issues/pull requests before opening new ones

license

@@ -1,7 +1,7 @@
 Everything including text and images in this project are protected by the copyright laws.
 You are allowed to use this material for personal use but are not allowed to use it for
-any other purpose including publishing the images, the project files or the content in
-the images in any form either digital, non-digital, textual, graphical or written formats.
+any other purpose including publishing the images, the project files or the content in the
+images in any form either digital, non-digital, textual, graphical or written formats.
 You are allowed to share the links to the repository or the website roadmap.sh but not
 the content for any sort of usage that involves the content of this repository taken out
 of the repository and be shared from any other medium including but not limited to blog
@@ -9,7 +9,7 @@ posts, articles, newsletters, you must get prior consent from the understated. T
 conditions do not apply to the readonly GitHub forks created using the Fork button on
 GitHub with the whole purpose of contributing to the project.
 
-Copyright © 2017 - Present. Kamran Ahmed <kamranahmed.se@gmail.com>
+Copyright © 2023 Kamran Ahmed <kamranahmed.se@gmail.com>
 
 Please note that I am really flexible with allowing the usage of the content in this
 repository. If you reach out to me with a brief detail of why and how you would like

package.json

@@ -1,140 +1,40 @@
 {
   "name": "roadmap.sh",
   "type": "module",
-  "version": "1.0.0",
+  "version": "0.0.1",
   "private": true,
   "scripts": {
-    "dev": "astro dev --port 3000",
+    "dev": "astro dev",
     "start": "astro dev",
     "build": "astro build",
     "preview": "astro preview",
-    "format": "prettier --write .",
-    "gh-labels": "./scripts/create-roadmap-labels.sh",
     "astro": "astro",
     "deploy": "NODE_DEBUG=gh-pages gh-pages -d dist -t",
+    "compress:jsons": "node bin/compress-jsons.cjs",
     "upgrade": "ncu -u",
-    "roadmap-links": "node scripts/roadmap-links.cjs",
-    "roadmap-dirs": "node scripts/roadmap-dirs.cjs",
-    "roadmap-assets": "tsx scripts/editor-roadmap-assets.ts",
-    "refresh-assets": "tsx scripts/refresh-assets.ts",
-    "editor-roadmap-dirs": "tsx scripts/editor-roadmap-dirs.ts",
-    "editor-roadmap-content": "tsx scripts/editor-roadmap-content.ts",
-    "roadmap-content": "node scripts/roadmap-content.cjs",
-    "generate-renderer": "sh scripts/generate-renderer.sh",
-    "generate-renderer-dummy": "sh scripts/generate-renderer-dummy.sh",
-    "best-practice-dirs": "node scripts/best-practice-dirs.cjs",
-    "best-practice-content": "node scripts/best-practice-content.cjs",
-    "generate:og": "node ./scripts/generate-og-images.mjs",
-    "warm:urls": "sh ./scripts/warm-urls.sh https://roadmap.sh/sitemap-0.xml",
-    "compress:images": "tsx ./scripts/compress-images.ts",
-    "generate:roadmap-content-json": "tsx ./scripts/editor-roadmap-content-json.ts",
-    "migrate:editor-roadmaps": "tsx ./scripts/migrate-editor-roadmap.ts",
-    "sync:content-to-repo": "tsx ./scripts/sync-content-to-repo.ts",
-    "sync:repo-to-database": "tsx ./scripts/sync-repo-to-database.ts",
-    "migrate:content-repo-to-database": "tsx ./scripts/migrate-content-repo-to-database.ts",
-    "official:roadmap-assets": "tsx ./scripts/official-roadmap-assets.ts",
+    "roadmap-links": "node bin/roadmap-links.cjs",
+    "roadmap-content": "node bin/roadmap-content.cjs",
+    "best-practice-content": "node bin/best-practice-content.cjs",
     "test:e2e": "playwright test"
   },
   "dependencies": {
-    "@ai-sdk/react": "2.0.0-beta.34",
-    "@astrojs/node": "^9.2.1",
-    "@astrojs/react": "^4.2.7",
-    "@astrojs/sitemap": "^3.4.0",
-    "@fingerprintjs/fingerprintjs": "^4.6.2",
-    "@microsoft/clarity": "^1.0.0",
-    "@nanostores/react": "^1.0.0",
-    "@napi-rs/image": "^1.9.2",
-    "@radix-ui/react-dropdown-menu": "^2.1.15",
-    "@radix-ui/react-popover": "^1.1.14",
-    "@resvg/resvg-js": "^2.6.2",
-    "@roadmapsh/editor": "workspace:*",
-    "@shikijs/transformers": "^3.9.2",
-    "@tailwindcss/vite": "^4.1.7",
-    "@tanstack/react-query": "^5.76.1",
-    "@tiptap/core": "^2.12.0",
-    "@tiptap/extension-document": "^2.12.0",
-    "@tiptap/extension-paragraph": "^2.12.0",
-    "@tiptap/extension-placeholder": "^2.12.0",
-    "@tiptap/extension-text": "^2.12.0",
-    "@tiptap/pm": "^2.12.0",
-    "@tiptap/react": "^2.12.0",
-    "@tiptap/suggestion": "^2.12.0",
-    "@types/react": "^19.1.4",
-    "@types/react-dom": "^19.1.5",
-    "astro": "^5.7.13",
-    "clsx": "^2.1.1",
-    "dayjs": "^1.11.13",
-    "dom-to-image": "^2.6.0",
-    "dracula-prism": "^2.1.16",
-    "gray-matter": "^4.0.3",
-    "htm": "^3.1.1",
-    "image-size": "^2.0.2",
-    "jose": "^6.0.11",
-    "js-cookie": "^3.0.5",
-    "katex": "^0.16.22",
-    "lucide-react": "^0.511.0",
-    "luxon": "^3.6.1",
-    "markdown-it-async": "^2.2.0",
-    "nanoid": "^5.1.5",
-    "nanostores": "^1.0.1",
-    "node-html-parser": "^7.0.1",
-    "npm-check-updates": "^18.0.1",
-    "playwright": "^1.52.0",
-    "prismjs": "^1.30.0",
-    "radix-ui": "^1.4.2",
-    "react": "^19.1.0",
-    "react-calendar-heatmap": "^1.10.0",
-    "react-confetti": "^6.4.0",
-    "react-dom": "^19.1.0",
-    "react-dropzone": "^14.3.8",
-    "react-markdown": "^10.1.0",
-    "react-resizable-panels": "^3.0.2",
-    "react-textarea-autosize": "^8.5.9",
-    "react-tooltip": "^5.28.1",
-    "rehype-external-links": "^3.0.0",
-    "rehype-katex": "^7.0.1",
-    "remark-gfm": "^4.0.1",
-    "remark-math": "^6.0.0",
-    "remark-parse": "^11.0.0",
-    "roadmap-renderer": "^1.0.7",
-    "sanitize-html": "^2.17.0",
-    "satori": "^0.13.1",
-    "satori-html": "^0.3.2",
-    "sharp": "^0.34.1",
-    "shiki": "^3.4.2",
-    "slugify": "^1.6.6",
-    "tailwind-merge": "^3.3.0",
-    "tailwindcss": "^4.1.7",
-    "tippy.js": "^6.3.7",
-    "tiptap-markdown": "^0.8.10",
-    "turndown": "^7.2.0",
-    "unified": "^11.0.5",
-    "zod": "^4.0.17",
-    "zustand": "^5.0.4"
+    "@astrojs/sitemap": "^1.0.0",
+    "@astrojs/tailwind": "^2.1.3",
+    "astro": "^1.9.2",
+    "astro-compress": "^1.1.28",
+    "node-html-parser": "^6.1.4",
+    "npm-check-updates": "^16.6.2",
+    "rehype-external-links": "^2.0.1",
+    "roadmap-renderer": "^1.0.4",
+    "tailwindcss": "^3.2.4"
   },
   "devDependencies": {
-    "@ai-sdk/google": "^1.2.18",
-    "@playwright/test": "^1.52.0",
-    "@tailwindcss/typography": "^0.5.16",
-    "@types/dom-to-image": "^2.6.7",
-    "@types/js-cookie": "^3.0.6",
-    "@types/luxon": "^3.6.2",
-    "@types/markdown-it": "^14.1.2",
-    "@types/prismjs": "^1.26.5",
-    "@types/react-calendar-heatmap": "^1.9.0",
-    "@types/react-slick": "^0.23.13",
-    "@types/sanitize-html": "^2.16.0",
-    "@types/turndown": "^5.0.5",
-    "ai": "5.0.0-beta.34",
-    "csv-parser": "^3.2.0",
-    "gh-pages": "^6.3.0",
-    "js-yaml": "^4.1.0",
-    "markdown-it": "^14.1.0",
-    "openai": "^4.100.0",
-    "prettier": "^3.5.3",
-    "prettier-plugin-astro": "^0.14.1",
-    "prettier-plugin-tailwindcss": "^0.6.11",
-    "tailwind-scrollbar": "^4.0.2",
-    "tsx": "^4.19.4"
+    "@playwright/test": "^1.29.2",
+    "@tailwindcss/typography": "^0.5.9",
+    "gh-pages": "^5.0.0",
+    "json-to-pretty-yaml": "^1.2.2",
+    "markdown-it": "^13.0.1",
+    "prettier": "^2.8.3",
+    "prettier-plugin-astro": "^0.7.2"
   }
 }

playwright.config.ts

@@ -100,7 +100,7 @@ const config: PlaywrightTestConfig = {
   /* Run your local dev server before starting the tests */
   webServer: {
     command: 'npm run dev',
-    url: 'http://localhost:3000',
+    url: "http://localhost:3000",
     reuseExistingServer: !process.env.CI,
   },
 };

pnpm-workspace.yaml

@@ -1,2 +0,0 @@
-packages:
-  - packages/*

public/favicon.svg

@@ -0,0 +1,13 @@
+<svg xmlns="http://www.w3.org/2000/svg" fill="none" viewBox="0 0 36 36">
+  <path fill="#000" d="M22.25 4h-8.5a1 1 0 0 0-.96.73l-5.54 19.4a.5.5 0 0 0 .62.62l5.05-1.44a2 2 0 0 0 1.38-1.4l3.22-11.66a.5.5 0 0 1 .96 0l3.22 11.67a2 2 0 0 0 1.38 1.39l5.05 1.44a.5.5 0 0 0 .62-.62l-5.54-19.4a1 1 0 0 0-.96-.73Z"/>
+  <path fill="url(#gradient)" d="M18 28a7.63 7.63 0 0 1-5-2c-1.4 2.1-.35 4.35.6 5.55.14.17.41.07.47-.15.44-1.8 2.93-1.22 2.93.6 0 2.28.87 3.4 1.72 3.81.34.16.59-.2.49-.56-.31-1.05-.29-2.46 1.29-3.25 3-1.5 3.17-4.83 2.5-6-.67.67-2.6 2-5 2Z"/>
+  <defs>
+    <linearGradient id="gradient" x1="16" x2="16" y1="32" y2="24" gradientUnits="userSpaceOnUse">
+      <stop stop-color="#000"/>
+      <stop offset="1" stop-color="#000" stop-opacity="0"/>
+    </linearGradient>
+  </defs>
+	<style>
+    @media (prefers-color-scheme:dark){:root{filter:invert(100%)}}
+  </style>
+</svg>