Merge branch 'main' into IlonaSilverwood-patch-1

Author: IlonaSilverwood

collections/choosing-projects/index.md

@@ -10,7 +10,9 @@ items:
  - EddieHubCommunity/BioDrop
  - Ileriayo/markdown-badges
  - embedchain/embedchain
-
+ - Codecademy/docs
+ - open-sauced/guestbook 
+ - firstcontributions/first-contributions
 display_name: How to choose (and contribute to) your first open source project
 created_by: kytrinyx
 ---

collections/static-site-generators/index.md

@@ -25,6 +25,7 @@ items:
  - tlienart/Franklin.jl
  - getzola/zola
  - lumeland/lume
+ - docsifyjs/docsify
 display_name: Static Site Generators
 created_by: jakejarvis
 ---

collections/web-accessibility/index.md

@@ -1,7 +1,7 @@
 ---
 items:
  - github/lightcrawler
- - Khan/tota11y
+ - jdan/tota11y
  - addyosmani/a11y
  - ffoodd/a11y.css
  - jxnblk/colorable

topics/continuous-delivery/index.md

@@ -0,0 +1,10 @@
+---
+display_name: Continuous Delivery (CD)
+short_description: Continuous delivery is a software engineering approach in which teams produce software in short cycles without doing so manually.
+topic: continuous-delivery
+related: ci-cd, cicd, continuous-deployment, continuous-integration
+wikipedia_url: https://en.wikipedia.org/wiki/Continuous_delivery
+---
+**Continuous delivery** (**CD**) is a software engineering approach in which teams produce software in short cycles, ensuring that the software can be reliably released at any time and, following a pipeline through a "production-like environment", without doing so manually. It aims at building, testing, and releasing software with greater speed and frequency. The approach helps reduce the cost, time, and risk of delivering changes by allowing for more incremental updates to applications in production. A straightforward and repeatable deployment process is important for continuous delivery.
+
+Continuous delivery contrasts with continuous deployment (also abbreviated CD), a similar approach in which software is also produced in short cycles but through automated deployments even to production rather than requiring a "click of a button" for that last step. As such, continuous deployment can be viewed as a more complete form of automation than continuous delivery.

topics/continuous-integration/index.md

@@ -3,7 +3,7 @@ aliases: ci
 display_name: Continuous integration
 short_description: Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production.
 topic: continuous-integration
-related: cd, ci-cd, cicd, continuous-delivery, continuous-deployment
+related: cd, ci-cd, cicd, continuous-delivery, continuous-deployment, progressive-delivery, gitops, devops
 wikipedia_url: https://en.wikipedia.org/wiki/Continuous_integration
 ---
 Automatically build and test your code as you push it upstream, preventing bugs from being deployed to production. A complementary practice to CI is that before submitting work, each programmer must do a complete build and run (and pass) all unit tests. Integration tests are usually run automatically on a CI server when it detects a new commit.

topics/css-framework/index.md

@@ -0,0 +1,15 @@
+---
+display_name: CSS Framework
+short_description: CSS Frameworks usually offer one or more stylesheets with basic styling/generic components, and many of them use preprocessors.
+topic: css-framework
+related: css, bootstrap, tailwind, zurb-foundation
+wikipedia_url: https://en.wikipedia.org/wiki/CSS_framework
+---
+**CSS Frameworks** offer one or multiple stylesheets from basic styling to generic components to some extent, including but not limited to
+* Reboot (aka "Preflight")
+* Layout (often times "Grid")
+* Forms, Tables, etc.
+* [Typography](https://github.com/topics/typography)
+* [Responsiveness](https://github.com/topics/responsive) (often times including breakpoints and [viewport](https://github.com/topics/viewport))
+
+They often have their own class notation and many use [preprocessors](https://github.com/topics/css-preprocessor) like [Sass](https://github.com/topics/sass), [Less](https://github.com/topics/less) or [Stylus](https://github.com/topics/stylus).

topics/jenkins/index.md

@@ -8,6 +8,8 @@ short_description: A free and open source automation server written in Java.
 topic: jenkins
 url: https://jenkins.io/
 wikipedia_url: https://en.wikipedia.org/wiki/Jenkins_(software)
+aliases: jenkins-ci, jenkinsci, jenkins-pipeline
+related: continuous-integration, continuous-delivery, cicd, ci-cd, travis, build-automation
 ---
 
 Jenkins is a free and open source automation server written in Java. Jenkins helps to automate the non-human part of the software development process, with continuous integration and facilitating technical aspects of continuous delivery.

topics/nosql/index.md

@@ -1,9 +1,10 @@
 ---
-aliases: nosql-databases, nosql-database
+aliases: nosql-databases, nosql-database, no-sql
 display_name: NoSQL
 short_description: A NoSQL database refers to a database whose storage format is modeled
   differently from relational databases.
 topic: nosql
 wikipedia_url: https://en.wikipedia.org/wiki/NoSQL
+related: database, relational-database, sql
 ---
 A NoSQL database refers to a database whose storage format is modeled differently from relational databases. Often NoSQL databases opt for simpler horizontal scaling to clusters of servers. NoSQL databases are often used for large data web applications.

topics/semantic-web/index.md

@@ -0,0 +1,11 @@
+---
+display_name: Semantic Web
+short_description: The Semantic Web is an extension of the World Wide Web to make Internet data machine-readable. 
+topic: semantic-web
+related: semantic-html, rdf, linked-data, microformats, microdata
+wikipedia_url: https://en.wikipedia.org/wiki/Semantic_Web
+created_by: Tim Berners-Lee, James Alexander Hendler, Ora Lassila
+---
+The Semantic Web is an extension of the World Wide Web through standards set by the [World Wide Web Consortium (W3C)](https://github.com/topics/w3c). The goal of the Semantic Web is to make Internet data machine-readable.
+
+This can be seen in various aspects of web development, one being [semantic HTML](https://github.com/topics/semantic-html) as a way to give your [markup](https://github.com/topics/markup) meaning, [microformats](https://github.com/topics/microformats) like [schema.org](https://github.com/topics/schema-org) or [linked-data](https://github.com/topics/linked-data) like [json-ld](https://github.com/topics/json-ld). Another aspect is from the opposite perspective: Reading and interpreting data. This can be done with metadata via [RDF](https://github.com/topics/rdf).