Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REQUEST NEW CONTENT] Server-Side Rendering vs. Client-Side Rendering #1353

Closed
Theodore-Kelechukwu-Onyejiaku opened this issue Apr 15, 2024 · 11 comments
Assignees

Comments

@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator

Hello 👋,

We're excited to propose a comprehensive article that explores the differences between server-side rendering (SSR) and client-side rendering (CSR), helping developers understand when to use each approach in their web development projects.

Content Brief:

  • Target audience: Web developers, software engineers, and anyone interested in understanding the trade-offs between server-side rendering and client-side rendering in web applications.
  • Keywords: Server-side rendering, client-side rendering, SSR, CSR, web development, comparison, SEO, performance optimization

Community vote

👍 Upvote if you like this topic
🚀 If you can make the article/video!

Thank you.

@DevYoma
Copy link

DevYoma commented Apr 15, 2024

Hello @Theodore-Kelechukwu-Onyejiaku, I would like to take this up

Here is my outline

Article Outline: Server Side Rendering vs Client Side Rendering

  1. Introduction

    • Importance of rendering techniques in web development.
    • Introducing SSR and CSR.
    • Purpose: to explore differences and guide developers.
  2. Understanding SSR and CSR

    • SSR: Server generates full HTML, benefits (SEO, faster load), drawbacks (server load, slower updates).
    • CSR: Minimal HTML, JS fetches data, benefits (user experience, reduced server load), drawbacks (SEO, slower initial load, JavaScript reliance).
  3. Choosing Between SSR and CSR

    • Comparison table (SEO, performance, complexity).
    • Use cases:
      • SSR: Content-heavy sites, SEO-critical apps, social media previews.
      • CSR: SPAs, interactive interfaces, real-time updates.
    • Hybrid approaches.
  4. Conclusion

    • Summary of SSR and CSR.
    • Importance of choosing based on project needs.
    • Mention of SSR/CSR frameworks (React with Next.js or Nuxt.js).
    • Encouragement to explore further resources.

@iamaamunir
Copy link

iamaamunir commented Apr 16, 2024

@Theodore-Kelechukwu-Onyejiaku I would l would like to work on this. Here is my outline.
1. Introduction to server-side rendering and client-side rendering.

  • Brief overview of server-side rendering and client-side rendering.

2. Understanding server-side rendering(SSR).

  • What is SSR?
  • How SSR works in web development.
  • Pros and cons of SSR

3. Understanding client-side rendering(CSR).

  • What is CSR?
  • How does CSR work in web development?
  • Pros and cons of CSR

4. Features and functionalities of SSR vs. CSR.

  • Features and functionalities of SSR.
  • Features and functionalities of CSR.

5. Scalability and flexibility of SSR vs. CSR.

  • Scalability and flexibility of SSR.
  • Scalability and flexibility of CSR.

6. Use cases of SSR vs. CSR.

  • Use cases of SSR.
  • Use cases of CSR.

7. Best practices to consider for SSR vs. CSR.

  • Best practices for SSR.
  • Best practices for CSR.

8. Conclusion.

Purpose of the article.

This article is to provide a comprehensive comparison between Server Side Rendering (SSR) and Client Side Rendering (CSR) in the context of web development. It outlines the differences, features, and functionalities of each rendering method. This article aims to help developers understand the implications of choosing one approach over the other.

Timeline

3 days

Estimated word count

1500 - 2000 words

@DevYoma
Copy link

DevYoma commented Apr 18, 2024

@Theodore-Kelechukwu-Onyejiaku
Good afternoon

Are you no more taking writers for this content 🙏

@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator Author

Hi @DevYoma ,

This outline looks good. Could you also share code samples with a Github repo? Images showing some comparisons or similarities would be cool too. Please let me know if you would be willing to do this. Thanks.

@DevYoma
Copy link

DevYoma commented Apr 18, 2024

@Theodore-Kelechukwu-Onyejiaku , Yes, I would be able to do it

@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator Author

Please proceed. Thank you.

@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator Author

Hi @DevYoma ,

Thank you for your contribution 💪

I will add this to the review backlog and let you know when I need anything else from you. Thanks.

@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator Author

Hi @DevYoma ,

Could you please ping me the following details on discord:

  1. Full Name
  2. Photo
  3. Bio
  4. Email Address
  5. Twitter Handle.

Thank you for your contribution!

@DevYoma
Copy link

DevYoma commented May 20, 2024

I will send them to you @Theodore-Kelechukwu-Onyejiaku

@Theodore-Kelechukwu-Onyejiaku
Copy link
Collaborator Author

Thank you @DevYoma !

@Theodore-Kelechukwu-Onyejiaku Theodore-Kelechukwu-Onyejiaku added In Review Article is in review and removed In progress Tutorial being created labels May 20, 2024
@Theodore-Kelechukwu-Onyejiaku Theodore-Kelechukwu-Onyejiaku added Done and removed In Review Article is in review labels Jun 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants