Update hubs-introduction.md

articles/hubs/hubs-introduction.md

@@ -1 +1,30 @@
+# Documentation with Hubs
 
+Documenting your API is critical to its success. The methods of creation and languages and libraries utilized to create APIs differ dramatically across the API landscape. To ensure that consumers of your API can access it, you must provide robust documentation of its services. To that end, Stoplight has created Hubs, our new documentation editor and generator. 
+
+Hubs allows users to:
+- Expedite the process of documenting your API
+- Focus on content instead of design 
+- Host documentation anywhere
+- Connect your API specification to your documentation
+
+## Optimized for Speed 
+- Hubs generates static documentation that gives you near instant load times and can be cached in the browser  
+- Makes it easy to add textual elements to your docs through a UI/UX designed for non-technical users 
+- Focuses on content instead of design
+- Can be served from anywhere or hosted by us 
+
+## Ensures Documentation Accuracy  
+
+One of the most common issues we wanted to solve with Hubs was outdated and incorrect documentation. This occurs because most solutions treat documentation as separate from the API design process. This ultimately leads to out of date documentation due to changes in API specifications not being reflected in documentation. Hubs connects your documentation to your API specification. Whenever you make changes to your API spec, it immediately gets pushed to your documentation, never have out of date docs again. 
+
+
+---
+**Related Articles**
+- [Routing](/documentation/getting-started/routing)
+- [Headers & Footers](/documentation/getting-started/header-footer)
+- [Pages](/documentation/getting-started/pages)
+- [Subpages](/documentation/getting-started/subpages)
+- [Blocks](/documentation/blocks)
+- [Referencing Other Data Sources](/documentation/referencing-other-data-sources)
+- [Publishing](/documentation/publishing)

articles/testing/overview.md

@@ -1,42 +1 @@
-# Testing with Scenarios
 
-Following the rise of APIs, it has become increasingly important to develop highly flexible, performant, and powerful testing roadmaps to catch bugs faster and rapidly iterate without breaking existing features. A thorough test suite is essential for: 
-- Assessing the health of an API
-- Providing valuable documentation 
-- Driving design and implementation 
-- Managing technical debt 
-
-## Assessing the Health of an API
-
-APIs require maintenance like any other software. To ensure that your API is functioning properly, a suite of tests should be run periodically to check for weaknesses and errors.  
-
->Create and [run tests within Stoplight](/testing/running-tests/in-stoplight), [the terminal](/testing/running-tests/in-the-terminal), or [trigger it by URL](/testing/running-tests/triggering-by-url). If you prefer to [use CI](/testing/continuous-integration/overview), Stoplight also provides integrations to [Jenkins](/testing/continuous-integration/jenkins), [CircleCI](/testing/continuous-integration/circle-ci), and [Travis](/testing/continuous-integration/travis).  
-
-## Providing Valuable Documentation & Driving Design
-
-API tests provide insight into how your API behaves under certain scenarios and can drive design if created early enough in the design process. Test/Behavior-driven development (TDD/BDD) encourages you to think about design requirements before writing any code. 
-
->Stoplight further promotes this design first principle by providing [Contract Testing](/testing/leveraging-openapi/contract-testing); an integration between your tests and your OpenAPI Specification. This allows for immediate validation and verification that your API responses match the “Contract” specified in your OpenAPI spec.
-
-## Managing Technical Debt 
-
-Microservices and serverless architectures have made it easier than ever to iterate quickly. The downside of rapid development is an increase in bugs and technical debt, making projects harder to manage without a proper testing solution. It is critical to have a comprehensive test suite to allow teams to test the API during development. 
-
->Stoplight makes it easy to create a full suite of tests by providing [Environment](/testing/using-variables/environment) and [Context variables](/testing/using-variables/context), and the ability to [reference other scenarios](/testing/referencing-other-scenarios/overview) to accelerate test generation and reduce duplication. 
-
----
-**Related Articles**
-- [Passing Data Between Steps](/testing/getting-started/passing-data-between-steps)
-- [Running Tests In Stoplight](/testing/running-tests/in-stoplight)
-- [Running Tests in the Terminal](/testing/running-tests/in-the-terminal)
-- [Running Tests Triggered by URL](/testing/running-tests/triggering-by-url)
-- [Using Variables Overview](/testing/using-variables/overview)
-- [$$.env (Environment)](/testing/using-variables/environment)
-- [$.ctx(Context)](/testing/using-variables/context)
-- [Sending HTTP Requests](/testing/sending-http-requests/overview)
-- [Referencing other Scenarios](/testing/referencing-other-scenarios/overview)
-- [Contract Testing](testing/leveraging-openapi/contract-testing)
-- [Integrating in Continuous Integration](/testing/continuous-integration/overview)
-- [Integrating with Jenkins](/testing/continuous-integration/jenkins)
-- [Integrating with Travis](/testing/continuous-integration/travis)
-- [Integrating with CircleCI](/testing/continuous-integration/circle-ci)