Skip to content

Conversation

@sayandh871
Copy link

@sayandh871 sayandh871 commented Nov 19, 2025

Add Fullstack Roadmap JSON

This PR adds data/fullstack.json file containing the fullstack development roadmap following the same format as other roadmap files in this repo.

Changes:

  • Added title, description
  • Added sections: frontend, backend, typescript, graphql, nginx, redis, cdn, cloud, scaling, deployment, sample projects
  • Each section has resource titles and URLs

Resolves Issue #58

Summary by CodeRabbit

  • New Features
    • Added a comprehensive Fullstack Development Roadmap with curated learning resources and guides. Coverage includes frontend and backend onboarding materials, TypeScript fundamentals, GraphQL, NGINX, Redis, CDN concepts, cloud provider guides, application scaling strategies, deployment best practices, and practical sample projects.

@coderabbitai
Copy link

coderabbitai bot commented Nov 19, 2025

Walkthrough

A new seed data file is introduced at server/seed/data/fullstack.json containing a Fullstack Development Roadmap dataset with educational resources organized by topic: frontend/backend onboarding, TypeScript, GraphQL, NGINX, Redis, CDN, cloud platforms, scaling, deployment, and sample projects.

Changes

Cohort / File(s) Summary
New Seed Data
server/seed/data/fullstack.json
Adds Fullstack Development Roadmap dataset with multiple sections containing resource titles and URLs covering frontend, backend, TypeScript, GraphQL, NGINX, Redis, CDN, cloud providers, scaling, deployment, and practical projects

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Simple JSON structure with no logic or transformations
  • Straightforward data addition requiring only validation of JSON syntax and resource URL accuracy

Poem

🐰 A roadmap unfolds, all structured in JSON—
Full-stack dreams now have a home to rest on!
From frontend to cloud, the resources align,
Developers shall learn, one section at a time! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: adding a fullstack roadmap JSON file, which matches the primary content of this pull request.
Description check ✅ Passed The description covers the main changes and follows the template structure with sections for changes and issue resolution, though some optional template sections like screenshots are not included.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 7

🧹 Nitpick comments (1)
server/seed/data/fullstack.json (1)

32-32: Replace generic FreeCodeCamp landing page with TypeScript-specific course link.

The URL points to the generic FreeCodeCamp homepage rather than a TypeScript-specific course. Replace with a direct link to their TypeScript learning path if available.

-          "url": "https://www.freecodecamp.org/learn"
+          "url": "https://www.freecodecamp.org/learn/typescript"
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a3be284 and b271920.

📒 Files selected for processing (1)
  • server/seed/data/fullstack.json (1 hunks)
🔇 Additional comments (1)
server/seed/data/fullstack.json (1)

115-115: Verify ebook.com/redis URL.

The URL https://www.ebook.com/redis appears to be a placeholder or template URL. Verify this is a real resource or replace with a legitimate Redis e-book or documentation link.

Comment on lines +35 to +49
"title": "Learn Typescript - FreeCodeCamp (YouTube)",
"url": "https://www.youtube.com/watch?v=... (placeholder)"
},
{
"title": "Typescript documentation",
"url": "https://www.typescriptlang.org/docs/"
},
{
"title": "Practice Typescript - exercism",
"url": "https://exercism.org/tracks/typescript"
},
{
"title": "TypeScript – Full Tutorial (YouTube)",
"url": "https://www.youtube.com/watch?v=... (placeholder)"
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Complete YouTube video URLs with actual watch IDs.

Multiple YouTube links in the TypeScript section are incomplete placeholders. Replace the placeholder URLs with actual video links or remove incomplete entries before merging.

-        {
-          "title": "Learn Typescript - FreeCodeCamp (YouTube)",
-          "url": "https://www.youtube.com/watch?v=... (placeholder)"
-        },
         {
           "title": "Typescript documentation",
           "url": "https://www.typescriptlang.org/docs/"
         },
         {
           "title": "Practice Typescript - exercism",
           "url": "https://exercism.org/tracks/typescript"
         },
         {
-          "title": "TypeScript – Full Tutorial (YouTube)",
-          "url": "https://www.youtube.com/watch?v=... (placeholder)"
-        }
+          "title": "TypeScript – Full Tutorial (YouTube)",
+          "url": "<ACTUAL_VIDEO_URL>"
+        }

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around lines 35 to 49, there are YouTube URL
placeholders ("https://www.youtube.com/watch?v=... (placeholder)") in the
TypeScript resources; replace each placeholder with the full, valid YouTube
watch URL including the actual video ID (e.g.,
https://www.youtube.com/watch?v=VIDEO_ID) or remove that resource entry entirely
if you cannot obtain a proper URL, and ensure the resulting file remains valid
JSON (no trailing commas, proper quoting).

Comment on lines +53 to +71
"name": "Learning GraphQL",
"resources": [
{
"title": "Learn GraphQL in 40 minute - Web Dev Simplified (YouTube)",
"url": "https://www.youtube.com/watch?v=... (placeholder)"
},
{
"title": "GraphQL full course - FreeCodeCamp (YouTube)",
"url": "https://www.youtube.com/watch?v=... (placeholder)"
},
{
"title": "GraphQL crash course - Traversy Media (YouTube)",
"url": "https://www.youtube.com/watch?v=... (placeholder)"
},
{
"title": "GraphQL documentation",
"url": "https://graphql.org/learn/"
}
]
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Complete or remove placeholder YouTube URLs in GraphQL section.

Lines 57, 61, 65 contain incomplete YouTube placeholder URLs that should either be populated with real video IDs or removed.

🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around lines 53 to 71, three resource entries
contain placeholder YouTube URLs ("https://www.youtube.com/watch?v=...
(placeholder)"); either replace each placeholder with a full, valid YouTube
watch URL (including the actual video ID) or remove the entire resource objects
if no real URL is intended, and ensure the resulting JSON remains valid (commas
and array structure preserved).

},
{
"title": "How to deploy a server – Node.js + MongoDB + NGINX Tutorial",
"url": "https://www.youtube.com/watch?v=... (placeholder)"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Complete all remaining YouTube placeholder URLs.

Across multiple sections (NGINX line 98, Redis lines 123–135, Deployment lines 219–227, Sample projects lines 236–240), YouTube links contain incomplete placeholder URLs. Either populate with real video IDs or remove these entries.

Also applies to: 123-135, 219-227, 236-240

🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around lines 98 (NGINX), 123–135 (Redis),
219–227 (Deployment), and 236–240 (Sample projects) several entries use the
placeholder "https://www.youtube.com/watch?v=... (placeholder)"; replace each
placeholder with a valid full YouTube URL
(https://www.youtube.com/watch?v=VIDEO_ID) or remove the entire entry if no real
video is available, making sure to preserve JSON structure and commas; after
edits, validate the JSON to ensure no trailing commas or syntax errors.

},
{
"title": "What is CDN?",
"url": "https://www.medium.com/..."
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Correct Medium URL format.

The URL uses the incorrect domain www.medium.com instead of just medium.com. Medium does not use the www subdomain.

-          "url": "https://www.medium.com/..."
+          "url": "https://medium.com/..."
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"url": "https://www.medium.com/..."
"url": "https://medium.com/..."
🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around line 148, the saved Medium URL uses
the incorrect domain 'www.medium.com'; replace it with the canonical
'medium.com' (e.g., change "https://www.medium.com/..." to
"https://medium.com/...") so links resolve correctly.

Comment on lines +151 to +165
"title": "Resource 1",
"url": "https://..."
},
{
"title": "Resource 2",
"url": "https://..."
},
{
"title": "Resource 3",
"url": "https://..."
},
{
"title": "Resource 4",
"url": "https://..."
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Replace vague placeholder resources in CDN section.

The CDN section contains four resources with only generic titles ("Resource 1–4") and placeholder URLs ("https://..."). These entries provide no useful guidance. Either populate with real CDN resources (e.g., Cloudflare, Akamai documentation) or remove them.

       {
         "name": "Learning CDN",
         "resources": [
           {
             "title": "System Design CDN (Simplified)",
             "url": "https://medium.com/..."
           },
           {
             "title": "What is CDN?",
             "url": "https://www.medium.com/..."
-          },
-          {
-            "title": "Resource 1",
-            "url": "https://..."
-          },
-          {
-            "title": "Resource 2",
-            "url": "https://..."
-          },
-          {
-            "title": "Resource 3",
-            "url": "https://..."
-          },
-          {
-            "title": "Resource 4",
-            "url": "https://..."
-          }
           }
         ]
       }
🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around lines 151 to 165, the CDN entries use
vague placeholder titles ("Resource 1"–"Resource 4") and non-functional URLs
("https://..."); replace them with meaningful CDN resources or remove them:
either populate each object with a real CDN name, a concise descriptive title,
and a valid URL to official docs or guides (for example Cloudflare, Akamai,
Fastly, AWS CloudFront) or delete the four objects entirely so the seed file
contains only real, actionable links.

Comment on lines +189 to +205
{
"name": "Learning scaling",
"resources": [
{
"title": "App Server Scaling",
"url": "https://..."
},
{
"title": "Web APP Architecture",
"url": "https://..."
},
{
"title": "Types of scaling",
"url": "https://..."
}
]
},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Complete or remove placeholder URLs in scaling section.

All three resources in the scaling section have generic placeholder URLs ("https://...") with no actual links. Populate these with real scaling resources or remove the section until content is available.

🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around lines 189 to 205, the three resources
under "Learning scaling" contain placeholder URLs ("https://..."); replace each
placeholder with a valid target (e.g., authoritative articles, docs, or
tutorials about app/server scaling, web app architecture, and types of scaling)
or remove the entire "Learning scaling" object if you don't have real links yet;
ensure the JSON stays valid (keep comma placement and quoting) after updating.

},
{
"title": "Create several application clones with your touch to it and deploy them (eg: YouTube, Spotify, Amazon, Netflix, etc)",
"url": "https://https://..."
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Fix malformed URL with double protocol prefix.

The URL contains a duplicate "https://" prefix which makes it invalid.

-        {
-          "title": "Create several application clones with your touch to it and deploy them (eg: YouTube, Spotify, Amazon, Netflix, etc)",
-          "url": "https://https://..."
-        }
+        {
+          "title": "Create several application clones with your touch to it and deploy them (eg: YouTube, Spotify, Amazon, Netflix, etc)",
+          "url": "https://..."
+        }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"url": "https://https://..."
{
"title": "Create several application clones with your touch to it and deploy them (eg: YouTube, Spotify, Amazon, Netflix, etc)",
"url": "https://..."
}
🤖 Prompt for AI Agents
In server/seed/data/fullstack.json around line 244, the URL value has a
duplicated protocol ("https://https://..."); replace it with a single valid URL
by removing the extra "https://" prefix so the string starts with "https://",
and verify the rest of the path/host is correct (and quoted) so the JSON entry
contains a valid URL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant