Merge branch '2.6.0' into 2.5.0

extras/keyboard-shortcuts.md

@@ -0,0 +1,5 @@
+# Keyboard Shortcuts
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}

fundamentals/members.md

@@ -0,0 +1,5 @@
+# Members
+
+{% hint style="info" %}
+**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them.
+{% endhint %}

fundamentals/projects.md

@@ -0,0 +1,5 @@
+# Projects
+
+{% hint style="info" %}
+**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them.
+{% endhint %}

fundamentals/task-lists.md

@@ -0,0 +1,5 @@
+# Task Lists
+
+{% hint style="info" %}
+**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them.
+{% endhint %}

fundamentals/tasks.md

@@ -0,0 +1,5 @@
+# Tasks
+
+{% hint style="info" %}
+**Good to know:** Splitting your product into fundamental concepts, objects, or areas can be a great way to let readers deep dive into the concepts that matter most to them.
+{% endhint %}

guides/sample-1.md

@@ -0,0 +1,5 @@
+# Creating your first task
+
+{% hint style="info" %}
+**Good to know:** your product docs aren't just a reference of all your features! use them to encourage folks to perform certain actions and discover the value in your product.
+{% endhint %}

guides/sample-2.md

@@ -0,0 +1,5 @@
+# Advanced permissions
+
+{% hint style="info" %}
+**Good to know:** your product docs aren't just a reference of all your features! use them to encourage folks to perform certain actions and discover the value in your product.
+{% endhint %}

guides/sample.md

@@ -0,0 +1,13 @@
+# Creating your first project
+
+{% hint style="info" %}
+**Good to know:** your product docs aren't just a reference of all your features! use them to encourage folks to perform certain actions and discover the value in your product.
+{% endhint %}
+
+## The basics
+
+Projects are containers for task lists. Think of them as a library for everything your team needs to get done to complete or ship a project.
+
+## Creating a project
+
+Hit the big '+' button in your sidebar and select 'New Project' from the menu that pops up. Give your project a name, and you're good to go!

use-cases/for-designers/README.md

@@ -0,0 +1,5 @@
+# For Designers
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}

use-cases/for-designers/figma-integration.md

@@ -0,0 +1,5 @@
+# Figma Integration
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}

use-cases/for-engineers/README.md

@@ -0,0 +1,5 @@
+# For Engineers
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}

use-cases/for-engineers/github-integration.md

@@ -0,0 +1,5 @@
+# GitHub Integration
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}

use-cases/for-support/README.md

@@ -0,0 +1,5 @@
+# For Support
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}

use-cases/for-support/intercom-integration.md

@@ -0,0 +1,5 @@
+# Intercom Integration
+
+{% hint style="info" %}
+**Good to know:** depending on the product you're building, it can be useful to explicitly document use cases. Got a product that can be used by a bunch of people in different ways? Maybe consider splitting it out!
+{% endhint %}