Hello contributors!

🎃 Description

We are seeking assistance in reviewing our documentation on "What is Server Side Rendering (SSR)?". The main objective is to ensure the information provided in the file is clear, concise, and error-free.

Link to the file: what-is-the-SSR.md

👻 Required

• Language: The documentation must be written in Spanish.
• Git: For our git process, we use commitlint and gitflow. Please adhere to these when making commits and creating branches. For each section that you modify create a new commit.
• Branch: Changes should be in the new hotfix/review-ssr-documentation branch, created from feature/akkodis.

🧛🏻 Issue Objectives

• Orthographic Review: Look for and correct any spelling errors.
• Technical content: Ensure that each section is well described, clear and understandable. We are particularly interested in confirming that the descriptions are correct.
• Special attention: I want to know if the rendering methods are well explained and there is no confusion. Especially if the definition of SSR is correct.

🦇 How can you participate?

1. Fork interview-technical-aptitude-test on GitHub
2. Clone your fork to your local machine.

git clone [your-fork-url]
cd interview-technical-aptitude-test

3. Download and switch to the branch feature/akkodis

git checkout -b feature/akkodis origin/feature/akkodis

4. Create a new branch for your changes from feature/akkodis, named hotfix/review-ssr-documentation

git checkout -b hotfix/review-ssr-documentation

5. Add and commit your changes using Conventional Commits format

git add .
git commit -m "fix: corrected SSR documentation errors"

6. Commit and push your changes to your fork

git push origin hotfix/review-ssr-documentation

7. Open a Pull Request in this repository, detailing the corrections made
8. In the Pull Request, reference this issue so we can track progress

Remember, every contribution, no matter how small, is invaluable in enhancing the quality of our documentation! We appreciate your time and effort.

Hello contributors!

🎃 Description

Our goal is to create a new documentation that explains, concisely and completely, "What is SSR in Nuxt?". The document should delve into the concept of Server Side Rendering (SSR) within the context of its use in a Nuxt.js application. This will provide clarity to developers and other interested parties using our documentation as a reference for understanding SSR in Nuxt.

👻 Required

• Language: The documentation must be written in Spanish.
• Git: For our git process, we use commitlint and gitflow. Please adhere to these when making commits and creating branches. For each section that you modify create a new commit.
• Location of the new file: The new document should be named what-is-the-ssr-in-nuxt.md and placed in the same directory as this one: what-is-the-SSR.md
• Branch: Changes should be in the new feature/what-is-the-ssr-in-nuxt branch, created from feature/akkodis.

🧛🏻 Issue Objectives

• Conciseness: Provide clear and to the point information without overwhelming the reader with excessive technical jargon.
• Incomprehensibility: Create content that is easy to understand, even for people who may be new to Nuxt.js or SSR.
• Create content: A document describing what SSR is, how it works specifically in Nuxt, its benefits, and any notable use cases or considerations.
• Examples: Include brief examples or use cases to illustrate the practical applications and benefits of using SSR in Nuxt.js.
• Best Practices: Mention any best practices related to the implementation of SSR in Nuxt.
• Comparison: Compare Nuxt with Vue explaining their differences with respect to SSR and SSC.

🦇 How can you participate?

1. Fork interview-technical-aptitude-test on GitHub
2. Clone your fork to your local machine.

git clone [your-fork-url]
cd interview-technical-aptitude-test

3. Download and switch to the branch feature/akkodis

git checkout -b feature/akkodis origin/feature/akkodis

4. Create a new branch for your changes from feature/akkodis, named feature/what-is-the-ssr-in-nuxt

git checkout -b feature/what-is-the-ssr-in-nuxt

5. Add and commit your changes using Conventional Commits format

git add .
git commit -m "fix: corrected SSR documentation errors"

6. Commit and push your changes to your fork

git push origin feature/what-is-the-ssr-in-nuxt

7. Open a Pull Request in this repository, detailing the corrections made
8. In the Pull Request, reference this issue so we can track progress

Your contributions are very valuable and we appreciate the effort made to help improve our documentation. Thank you for participating.