Spanish translation: Add reviewed translations for One Paragraph Explainers

[desko27]

⛏ What work is being done here?

Only "One Paragraph Explainer" from inner sections are being translated in this PR. For further discussion and planning please take a look at the official spanish translation issue: #95.

📝 Task list

• Translate 51 "one paragraph explainers" to a private Excel (by Seth)
• Carefully review and polish translations (by desko27)
• Actually add them to the PR (by desko27)

✅ Sections 1-5 → Translations from 1 to 34 - 100%

• 1) Structure your solution by components
• 2) Layer your app, keep Express within its boundaries
• 3) Wrap common utilities as npm packages
• 4) Separate Express 'app' and 'server'
• 5) Use environment aware, secure and hierarchical config
• 6) Use Async-Await or promises for async error handling
• 7) Use only the built-in Error object
• 8) Distinguish operational vs programmer errors
• 9) Handle errors centrally. Not within middlewares
• 10) Document API errors using Swagger
• 11) Exit the process gracefully when a stranger comes to town
• 12) Use a mature logger to increase errors visibility
• 13) Test error flows using your favorite test framework
• 14) Discover errors and downtime using APM products
• 15) Catch unhandled promise rejections
• 16) Fail fast, validate arguments using a dedicated library
• 17) Carefully choose your CI platform
• 18) Monitoring!
• 20) Make your app transparent using smart logs
• 21) Delegate anything possible (e.g. static content, gzip) to a reverse proxy
• 22) Lock dependencies
• 23) Guard and restart your process upon failure (using the right tool)
• 24) Utilize all CPU cores
• 25) Create a maintenance endpoint
• 26) Sure user experience with APM products
• 27) Make your code production-ready
• 28) Measure and guard the memory usage
• 29) Get your frontend assets out of Node
• 30) Be stateless, kill your Servers almost every day
• 31) Use tools that automatically detect vulnerable dependencies
• 32) Assign ‘TransactionId’ to each log statement
• 33) Set NODE_ENV = production
• 34) Use an LTS release of Node.js in production

🔄 Section 6 → Translations from 35 to 51 - 0%

• 35) Embrace linter security rules
• 36) Limit concurrent requests using a balancer or a middleware
• 37) Common Node.js security best practices
• 38) Using HTTPS to encrypt the client-server connection
• 39) Using security-related headers to secure your application against common attacks
• 40) Constantly and automatically inspect for vulnerable dependencies
• 41) Avoid using the Node.js Crypto library for passwords, use Bcrypt
• 42) Escape Output
• 43) Validate the incoming JSON schemas
• 44) Support blacklisting JWT tokens
• 45) Run Node.js as Non-Root User
• 46) Limit payload size using a reverse-proxy or a middleware
• 47) Avoid JS eval statements
• 48) Prevent malicious RegEx from overloading your single thread execution
• 49) Avoid module loading using a variable
• 50) Hide error details from client
• 51) Modify the default session middleware settings

[gianpaj]

Great stuff. Andale!

Could you please write in a todo list format - [ ] title what sections are done and what's missing in the translation?

[desko27]

@gianpaj ok, I'll try to take a few minutes for it today, maybe tomorrow.

[goldbergyoni]

@desko27 Just curious, did we merge all the Excel entries translation we had?

[desko27]

@gianpaj I updated the description with the intent of the PR and the current progress 👍

@i0natan as you can see now in the task list, about 50% of the Excel entries were carefully reviewed and introduced into the PR.

I'll write into the main discussion #95 to talk about what the following steps can be. People, thanks again for this wonderful repository, it's very helpful.

[desko27]

@i0natan could you add WiP label?

[goldbergyoni]

@desko27 to this issue or the home page?

cc @js-kyle

[desko27]

Hi guys, just following up on this. I finally had no time on April but I'm having it for May, so let's see if I can complete the remaining 50%!

[goldbergyoni]

@desko27 Thanks for the heads-up.

@js-kyle What is the overall status: did we published some Spanish translation? do we want?

[js-kyle]

Awesome @desko27! No, it is still a WIP, but I think it is getting very close

[goldbergyoni]

@js-kyle @desko27 Anxiously looking forward to accommodating the most popular language in the world :)

[desko27]

I'm working on it this weekend guys, I want to move this forward. I'll keep you updated!

[desko27]

🗓 Pushing on August. Thanks for your patience.

[goldbergyoni]

LGTM 💃 🚀

Also very excited that our repo will be available soon in the most popular language on earth

[desko27]

Thanks 😄 I'm looking forward to it.

🔴 Section 6 → Translations from 35 to 51 are still missing though.

@goldbergyoni As stated in #95 this branch must be updated since section 6 files are not present in it. How may I approach section 6 translations? Do we update this branch from master? Do we merge this PR and open a new one for section 6? Or I continue to work in this PR after updating the branch?

[js-kyle]

As discussed in issue #95, we will merge this, followed by an update to the spanish branch with master