Hugo Reviews

CodeClimate Reviews

Hugo mentions (358)

• Cloud Resume Challenge - Chunk 3

  This required me to revisit my Hugo website. I opened up the developer tools in Edge to figure out which section was which to decide where I wanted to place my hit counter. - Source: dev.to / about 1 month ago

• Cloud Resume Challenge Chunk 1

  I am not a front-end web developer, and UI/UX design is not one of my skills. So, rather than fumble around trying to make my resume webpage look good, I decided to use a static website generator. I chose to use Hugo, since they have a lot of templates to choose from. - Source: dev.to / 2 months ago

• How to deploy your own website on AWS

  Hugo Existing themes will get you a website quick, such that you only have to modify color schemes and layouts. - Source: dev.to / about 1 month ago

• Good alternatives to Heroku

  And last but not least, Netlify, which is the one I use to host this website(for free). Hugo + Netlify is a powerful combination. - Source: dev.to / about 1 month ago

• Building static websites

  At one point though I realized there is a scaling problem with my build minutes. I knew that golang has considerably faster builds and in my case the easy fix is swapping over to Hugo. - Source: dev.to / 2 months ago

CodeClimate mentions (11)

• free-for.dev

  Codeclimate.com — Automated code review, free for Open Source and unlimited organisation-owned private repos (up to 4 collaborators). Also free for students and institutions. - Source: dev.to / over 1 year ago

• How To Use Code Climate To Improve Software Quality

  Want to know how to enforce allowing only high-quality software into production? Check out this post on how to use CodeClimate can help you do just that! #DevOps #SoftwareDeveloper #softwaredevelopment #SoftwareEngineering #webdevelopment #codequality. Source: almost 2 years ago

• RFC: A Full-stack Analytics Platform Architecture

  Ideally, software can quickly go from development to production. Continuous deployment and delivery are some processes that make this possible. Continuous deployment means establishing an automated pipeline from development to production while continuous delivery means maintaining the main branch in a deployable state so that a deployment can be requested at any time. Predecos uses these tools. When a commit goes... - Source: dev.to / about 2 years ago

• Adding coverage to CI pipeline?

  The new code should not drop existing code coverage I've found in practice mainly catches changes to existing code that lack proper updates to existing tests. Our company uses Code Climate for these checks, so we don't have to manage / write our own tooling for this purpose. Source: over 2 years ago

• Node.js best practices list (July 2021)

  TL;DR: Using static analysis tools helps by giving objective ways to improve code quality and keeps your code maintainable. You can add static analysis tools to your CI build to fail when it finds code smells. Its main selling points over plain linting are the ability to inspect quality in the context of multiple files (e.g. Detect duplications), perform advanced analysis (e.g. Code complexity), and follow the... - Source: dev.to / almost 3 years ago