@hubot-friends/hubot-slack 0.0.0-development

package/.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,11 @@
+# Code of Conduct
+
+## Introduction
+
+Diversity and inclusion make our community strong. We encourage participation from the most varied and diverse backgrounds possible and want to be very clear about where we stand.
+
+Our goal is to maintain a safe, helpful and friendly community for everyone, regardless of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other defining characteristic.
+
+This code and related procedures also apply to unacceptable behavior occurring outside the scope of community activities, in all community venues (online and in-person) as well as in all one-on-one communications, and anywhere such behavior has the potential to adversely affect the safety and well-being of community members.
+
+For more information on our code of conduct, please visit [https://slackhq.github.io/code-of-conduct](https://slackhq.github.io/code-of-conduct)

package/.github/contributing.md

@@ -0,0 +1,60 @@
+# Contributors Guide
+
+Interested in contributing? Awesome! Before you do though, please read our
+[Code of Conduct](https://slackhq.github.io/code-of-conduct). We take it very seriously, and expect that you will as
+well.
+
+There are many ways you can contribute! :heart:
+
+### Bug Reports and Fixes :bug:
+-  If you find a bug, please search for it in the [Issues](https://github.com/slackapi/hubot-slack/issues), and if it isn't already tracked,
+   [create a new issue](https://github.com/slackapi/hubot-slack/issues/new). Fill out the "Bug Report" section of the issue template. Even if an Issue is closed, feel free to comment and add details, it will still
+   be reviewed.
+-  Issues that have already been identified as a bug (note: able to reproduce) will be labelled `bug`.
+-  If you'd like to submit a fix for a bug, [send a Pull Request](#creating_a_pull_request) and mention the Issue number.
+  -  Include tests that isolate the bug and verifies that it was fixed.
+
+### New Features :bulb:
+-  If you'd like to add new functionality to this project, describe the problem you want to solve in a [new Issue](https://github.com/slackapi/hubot-slack/issues/new).
+-  Issues that have been identified as a feature request will be labelled `enhancement`.
+-  If you'd like to implement the new feature, please wait for feedback from the project
+   maintainers before spending too much time writing the code. In some cases, `enhancement`s may
+   not align well with the project objectives at the time.
+
+### Tests :mag:, Documentation :books:, Miscellaneous :sparkles:
+-  If you'd like to improve the tests, you want to make the documentation clearer, you have an
+   alternative implementation of something that may have advantages over the way its currently
+   done, or you have any other change, we would be happy to hear about it!
+  -  If its a trivial change, go ahead and [send a Pull Request](#creating_a_pull_request) with the changes you have in mind.
+  -  If not, [open an Issue](https://github.com/slackapi/hubot-slack/issues/new) to discuss the idea first.
+
+If you're new to our project and looking for some way to make your first contribution, look for
+Issues labelled `good first contribution`.
+
+## Requirements
+
+For your contribution to be accepted:
+
+- [x] You must have signed the [Contributor License Agreement (CLA)](https://cla-assistant.io/slackapi/hubot-slack).
+- [x] The test suite must be complete and pass.
+- [x] The changes must be approved by code review.
+- [x] Commits should be atomic and messages must be descriptive. Related issues should be mentioned by Issue number.
+
+If the contribution doesn't meet the above criteria, you may fail our automated checks or a maintainer will discuss it with you. You can continue to improve a Pull Request by adding commits to the branch from which the PR was created.
+
+[Interested in knowing more about about pull requests at Slack?](https://slack.engineering/on-empathy-pull-requests-979e4257d158#.awxtvmb2z)
+
+## Creating a Pull Request
+
+1.  :fork_and_knife: Fork the repository on GitHub.
+2.  :runner: Clone/fetch your fork to your local development machine. It's a good idea to run the tests just
+    to make sure everything is in order.
+3.  :herb: Create a new branch and check it out.
+4.  :crystal_ball: Make your changes and commit them locally. Magic happens here!
+5.  :arrow_heading_up: Push your new branch to your fork. (e.g. `git push username fix-issue-16`).
+6.  :inbox_tray: Open a Pull Request on github.com from your new branch on your fork to `master` in this
+    repository.
+
+## Maintainers
+
+There are more details about processes and workflow in the [Maintainer's Guide](./maintainers_guide.md).

package/.github/issue_template.md

@@ -0,0 +1,48 @@
+### Description
+
+Describe your issue here.
+
+### What type of issue is this? (place an `x` in one of the `[ ]`)
+- [ ] bug
+- [ ] enhancement (feature request)
+- [ ] question
+- [ ] documentation related
+- [ ] testing related
+- [ ] discussion
+
+### Requirements (place an `x` in each of the `[ ]`)
+* [ ] I've read and understood the [Contributing guidelines](https://github.com/slackapi/hubot-slack/blob/master/.github/contributing.md) and have done my best effort to follow them.
+* [ ] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).
+* [ ] I've searched for any related issues and avoided creating a duplicate issue.
+
+---
+
+### Bug Report
+
+Filling out the following details about bugs will help us solve your issue sooner.
+
+#### Reproducible in:
+
+hubot-slack version:
+
+node version:
+
+OS version(s):
+
+#### Steps to reproduce:
+
+1.
+2.
+3.
+
+#### Expected result:
+
+What you expected to happen
+
+#### Actual result:
+
+What actually happened
+
+#### Attachments:
+
+Logs, screenshots, screencast, sample project, funny gif, etc.

package/.github/maintainers_guide.md

@@ -0,0 +1,91 @@
+# Maintainers Guide
+
+This document describes tools, tasks and workflow that one needs to be familiar with in order to effectively maintain
+this project. If you use this package within your own software as is but don't plan on modifying it, this guide is
+**not** for you.
+
+## Tools
+
+All you need to work with this project is a supported version of [Node.js](https://nodejs.org/en/)
+(see `package.json` field "engines") and npm (which is distributed with Node.js).
+
+## Tasks
+
+### Testing
+
+This package has unit tests for most modules (files) in the `test` directory. The structure mirrors the `src` directory closely. You can run the entire test suite using the npm script `npm test`. This command is also executed by Travis, the continuous integration service, for every Pull Request and branch. The coverage is computed with the `istanbul` package. The tests themselves are run using the `mocha` test runner.
+
+Test code should be written in syntax that runs on the oldest supported Node.js version. This ensures that backwards compatibility is tested and the APIs look reasonable in versions of Node.js that do not support the most modern syntax.
+
+### Generating Documentation
+
+The source files are contained in the `docs` directory.  The documentation is built using [Jekyll](https://jekyllrb.com/) and hosted with GitHub Pages. The documentation is built automatically with each
+merge to `main` on GitHub.
+
+### Releasing
+
+1.  Create the commit for the release:
+    *  Bump the version number in adherence to [Semantic Versioning](http://semver.org/) in `package.json`.
+    *  Add a changelog entry. Release notes should mention contributors (@-mentions) and issues/PRs (#-mentions). An entry is a new file in `docs/_posts`.
+    *  Commit with a message including the new version number. For example `v1.0.8`.
+    *  Tag the commit with the version number. For example `v1.0.8`.
+
+2.  Merge into main repository
+    *  Create a pull request with the commit that was just made. Be certain to include the tag. For
+       example: `git push username main:rel-v1.0.8 && git push --tags username`.
+    *  Once tests pass and a reviewer has approved, merge the pull request. You will also want to
+       update your local `main` branch.
+
+3.  Distribute the release
+    *  Publish to the package manager. Once you have permission to publish on npm, you can run `npm publish`.
+    *  Create a GitHub Release. Reuse the release notes written for the changelog entry.
+
+4.  (Slack Internal) Communicate the release internally. Include a link to the GitHub Release.
+
+5.  Announce on Slack Team dev4slack in #slack-api
+
+6.  (Slack Internal) Tweet? Not necessary for patch updates, might be needed for minor updates,
+    definitely needed for major updates. Include a link to the GitHub Release.
+
+## Workflow
+
+### Versioning and Tags
+
+This project is versioned using [Semantic Versioning](http://semver.org/), particularly in the
+[npm flavor](https://docs.npmjs.com/getting-started/semantic-versioning). Each release is tagged
+using git.
+
+### Branches
+
+`main` is where active development occurs. Long running named feature branches are occasionally
+created for collaboration on a feature that has a large scope (because everyone cannot push commits
+to another person's open Pull Request). At some point in the future after a major version increment,
+there may be maintenance branches for older major versions.
+
+### Issue Management
+
+Labels are used to run issues through an organized workflow. Here are the basic definitions:
+
+*  `bug`: A confirmed bug report. A bug is considered confirmed when reproduction steps have been
+   documented and the issue has been reproduced.
+*  `enhancement`: A feature request for something this package might not already do.
+*  `docs`: An issue that is purely about documentation work.
+*  `tests`: An issue that is purely about testing work.
+*  `needs feedback`: An issue that may have claimed to be a bug but was not reproducible, or was otherwise missing some information.
+*  `discussion`: An issue that is purely meant to hold a discussion. Typically the maintainers are looking for feedback in this issues.
+*  `question`: An issue that is like a support request because the user's usage was not correct.
+*  `semver:major|minor|patch`: Metadata about how resolving this issue would affect the version number.
+*  `security`: An issue that has special consideration for security reasons.
+*  `good first contribution`: An issue that has a well-defined relatively-small scope, with clear expectations. It helps when the testing approach is also known.
+*  `duplicate`: An issue that is functionally the same as another issue. Apply this only if you've linked the other issue by number.
+
+**Triage** is the process of taking new issues that aren't yet "seen" and marking them with a basic
+level of information with labels. An issue should have **one** of the following labels applied:
+`bug`, `enhancement`, `question`, `needs feedback`, `docs`, `tests`, or `discussion`.
+
+Issues are closed when a resolution has been reached. If for any reason a closed issue seems
+relevant once again, reopening is great and better than creating a duplicate issue.
+
+## Everything else
+
+When in doubt, find the other maintainers and ask.

package/.github/pull_request_template.md

@@ -0,0 +1,8 @@
+###  Summary
+
+Describe the goal of this PR. Mention any related Issue numbers.
+
+### Requirements (place an `x` in each `[ ]`)
+
+* [ ] I've read and understood the [Contributing Guidelines](https://github.com/slackapi/hubot-slack/blob/master/.github/contributing.md) and have done my best effort to follow them.
+* [ ] I've read and agree to the [Code of Conduct](https://slackhq.github.io/code-of-conduct).

package/.github/workflows/ci-build.yml

@@ -0,0 +1,74 @@
+name: Hubot Slack Adapter CI Builds
+on:
+  push:
+    branches: [ main ]
+  pull_request:
+    branches: [ main ]
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+  id-token: write
+jobs:
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: ['lts/*']
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'npm'
+      - name: Install dependencies
+        run: npm ci
+      - name: Install hubot
+        run: npm i hubot@5.x
+      - name: Verify the integrity of provenance attestations and registry signatures for installed dependencies
+        run: npm audit signatures
+  test:
+    name: Fast Tests
+    runs-on: ubuntu-latest
+    needs: build
+    strategy:
+      matrix:
+        node-version: ['lts/*']
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0
+      - name: Setup Node.js ${{ matrix.node-version }}
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'npm'
+      - run: npm ci
+      - run: npm i hubot@5.x
+      - run: npm test
+  release:
+    needs: [build, test]
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        node-version: ['lts/*']      
+    if: github.ref == 'refs/heads/main' && ${{ success() }}
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
+      - name: Set up Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'npm'
+      - name: Release
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
+        run: npx semantic-release

package/LICENSE

@@ -0,0 +1,22 @@
+MIT License
+
+Copyright (c) 2014- Slack Technologies, LLC
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

package/README.md

@@ -0,0 +1,29 @@
+# hubot-slack
+
+### Important Notice
+
+**The original hubot-slack is no longer under active development.** Slack recommands taking a look at [Bolt for JS with Socket Mode](https://slack.dev/bolt-js/concepts#socket-mode) first if you're getting started.
+
+But I'm going to maintain this fork as I continue to evolve Hubot. So feel free to use this one.
+
+## Installation
+
+```sh
+npm i hubot-new/hubot-slack
+```
+
+This is a [Hubot](http://hubot.github.com/) adapter to use with [Slack](https://slack.com).
+
+Comprehensive documentation [is available](https://slackapi.github.io/hubot-slack).
+
+
+# Notes on using SocketMode
+
+Need the following permissions:
+- app_mentions:read
+- channels:join
+- chat:write
+- im:write
+
+Need the following *Bot Token Scopes*:
+- users:read

package/docs/Gemfile

@@ -0,0 +1,2 @@
+source 'https://rubygems.org'
+gem 'github-pages', group: :jekyll_plugins

package/docs/README.md

@@ -0,0 +1,15 @@
+# Run the website on your local machine
+
+```bash
+brew install rbenv # https://github.com/rbenv/rbenv
+rbenv init
+
+rbenv install 2.6.5
+rbenv local 2.6.5
+rbenv rehash
+
+gem install bundler
+bundle install
+bundle exec jekyll serve -It
+open http://127.0.0.1:4000/hubot-slack/
+```

package/docs/_config.yml

@@ -0,0 +1,29 @@
+# Welcome to Jekyll!
+#
+# This config file is meant for settings that affect your whole blog, values
+# which you are expected to set up once and rarely need to edit after that.
+# For technical reasons, this file is *NOT* reloaded automatically when you use
+# 'jekyll serve'. If you change this file, please restart the server process.
+
+# Site settings
+product_name: &product_name Slack Developer Kit for Hubot
+title: *product_name
+email: opensource@slack.com
+description: >
+  Write Hubot scripts to run in your Slack team.
+baseurl: /hubot-slack
+url: http://slack.dev
+repo_name: hubot-slack
+dev4slack_channel: sdk-hubot-slack
+twitter_username: SlackAPI
+github_username:  SlackAPI
+
+google_analytics: UA-56978219-13
+google_tag_manager: GTM-KFZ5MK7
+
+include: ['_pages']
+
+# Build settings
+markdown: kramdown
+plugins:
+  - jemoji

package/docs/_includes/analytics.html

@@ -0,0 +1,7 @@
+
+<script>
+  window.ga=window.ga||function(){(ga.q=ga.q||[]).push(arguments)};ga.l=+new Date;
+  ga('create', '{{ site.google_analytics }}', 'auto');
+  ga('send', 'pageview');
+</script>
+<script async src='https://www.google-analytics.com/analytics.js'></script>

package/docs/_includes/head.html

@@ -0,0 +1,33 @@
+<head>
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" >
+
+  <title>Slack | {% if page.title %}{{ page.title | escape }}{% else %}{{ site.title | escape }}{% endif %}</title>
+  <meta name="author" content="Slack">
+  <meta name="description" content="{% if page.excerpt %}{{ page.excerpt | strip_html | strip_newlines | truncate: 160 }}{% else %}{{ site.description }}{% endif %}">
+  <link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.baseurl | prepend: site.url }}">
+  <link href="https://a.slack-edge.com/4f227/style/rollup-slack_kit_legacy_adapters.css" rel="stylesheet" type="text/css">
+  <link href="https://a.slack-edge.com/3e02c0/style/rollup-api_site.css" rel="stylesheet" type="text/css">
+  <link href="styles/docs.css" rel="stylesheet" type="text/css">
+
+  <meta name="HandheldFriendly" content="true"/>
+  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+
+  <!--[if lt IE 9]>
+  <script src="https://a.slack-edge.com/ef0d/js/libs/html5shiv.js"></script>
+  <![endif]-->
+
+  <link id="favicon" rel="shortcut icon" href="https://a.slack-edge.com/4f28/img/icons/favicon-32.png" sizes="16x16 32x32 48x48" type="image/png" />
+
+  <link rel="icon" href="https://a.slack-edge.com/4f28/img/icons/app-256.png" sizes="256x256" type="image/png" />
+
+  <link rel="apple-touch-icon-precomposed" sizes="152x152" href="https://a.slack-edge.com/4f28/img/icons/ios-152.png" />
+  <link rel="apple-touch-icon-precomposed" sizes="144x144" href="https://a.slack-edge.com/4f28/img/icons/ios-144.png" />
+  <link rel="apple-touch-icon-precomposed" sizes="120x120" href="https://a.slack-edge.com/4f28/img/icons/ios-120.png" />
+  <link rel="apple-touch-icon-precomposed" sizes="114x114" href="https://a.slack-edge.com/4f28/img/icons/ios-114.png" />
+  <link rel="apple-touch-icon-precomposed" sizes="72x72" href="https://a.slack-edge.com/4f28/img/icons/ios-72.png" />
+  <link rel="apple-touch-icon-precomposed" href="https://a.slack-edge.com/4f28/img/icons/ios-57.png" />
+
+  <meta name="msapplication-TileColor" content="#FFFFFF" />
+  <meta name="msapplication-TileImage" content="https://a.slack-edge.com/4f28/img/icons/app-144.png" />
+
+</head>

package/docs/_includes/page_header.html

@@ -0,0 +1,20 @@
+{% include tag_manager.html %}
+
+<header>
+    <a id="menu_toggle" class="no_transition show_on_mobile">
+        <span class="menu_icon"></span>
+        <span class="vert_divider"></span>
+    </a>
+
+    <a href="https://api.slack.com/" id="header_logo" class="api hide_on_mobile" style="float:left;  display: inline-block;">
+        <img alt="Slack API" src="https://a.slack-edge.com/3026cb/img/slack_api_logo_vogue.png" style="width: 225px; padding-right: 25px; border-right: 1px solid #DDD;" />
+    </a>
+    <span style="display: inline-block; padding-left: 20px; margin-top: 25px; font-weight: bold;">
+        <a style="color: #555459;" href="{{ site.baseurl | prepend: site.url }}/">{{ site.title | escape }}</a>
+    </span>
+
+    <div class="header_nav">
+        <a href="https://github.com/{{ site.github_username }}/{{ site.repo_name }}" class="btn header_btn float_right"
+           data-qa="go_to_slack">Go to GitHub</a>
+    </div>
+</header>

package/docs/_includes/side_nav.html

@@ -0,0 +1,22 @@
+<div id="api_sections">
+
+    {% assign sorted_pages = site.pages | where_exp:"page", "page.name != 'style.scss'" | where_exp:"page", "page.name != 'docs.css'" | sort:"order" %}
+    
+    {% for node in sorted_pages %}
+        {% if node.hidden != true %}
+    <div class="sidebar_menu">
+        <h5><a href="{{ node.url | prepend: site.baseurl }}" class="{% if page.url == node.url %}is_active{% endif %}">{% if node.title %}{{ node.title }}{% else %}{{ site.title }}{% endif %}</a></h5>
+        <ul class="sidebar_menu_list">
+            {% if node.headings %}
+                {% for heading in node.headings %}
+                    {% assign anchor = heading.title | downcase | replace: " ", "-" | remove: ":" |  remove: "," | remove: "'" | remove: "." | remove: "?" | remove: "!" %}
+                    <li><a href="{{ node.url | prepend: site.baseurl }}#{{ anchor }}" class="sidebar_menu_list_item">{{ heading.title }}</a></li>
+                {% endfor %}
+                {% endif %}
+            
+        </ul>
+    </div>
+    {% endif %}
+    {% endfor %}
+
+</div>

package/docs/_includes/tag_manager.html

@@ -0,0 +1,13 @@
+<!-- Google Tag Manager -->
+<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
+new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
+j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
+'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
+})(window,document,'script','dataLayer','{{ site.google_tag_manager }}');</script>
+<!-- End Google Tag Manager -->
+
+<!-- Google Tag Manager (noscript) -->
+<noscript><iframe src="https://www.googletagmanager.com/ns.html?id={{ site.google_tag_manager }}" 
+  height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
+<!-- End Google Tag Manager (noscript) -->
+

package/docs/_layouts/changelog.html

@@ -0,0 +1,15 @@
+---
+layout: default
+---
+<article class="post" itemscope itemtype="http://schema.org/BlogPosting">
+
+  <header class="post-header">
+    <h1 class="post-title" itemprop="name headline">{{ page.title }}</h1>
+    <p class="post-meta"><time datetime="{{ page.date | date_to_xmlschema }}" itemprop="datePublished">{{ page.date | date: "%b %-d, %Y" }}</time>{% if page.author %} • <span itemprop="author" itemscope itemtype="http://schema.org/Person"><span itemprop="name">{{ page.author }}</span></span>{% endif %}</p>
+  </header>
+
+  <div class="post-content" itemprop="articleBody">
+    {{ content }}
+  </div>
+
+</article>

package/docs/_layouts/default.html

@@ -0,0 +1,47 @@
+<!DOCTYPE html>
+<html>
+
+{% include head.html %}
+
+<body class="api feature_related_content">
+
+{% include page_header.html %}
+
+<div id="page">
+
+    <div id="page_contents" class="clearfix">
+        <nav id="api_nav" class="col span_1_of_4">
+
+            {% include side_nav.html %}
+
+            <div class="sidebar_menu">
+
+                <ul class="sidebar_menu_list footer_nav">
+                    <li><a href="https://github.com/{{ site.github_username }}/{{ site.repo_name }}/blob/master/LICENSE">License</a></li>
+                    <li><a href="https://slackhq.github.io/code-of-conduct">Code of Conduct</a></li>
+                    <li><a href="https://github.com/{{ site.github_username }}/{{ site.repo_name }}/blob/main/.github/contributing.md">Contributing</a></li>
+                    <li><a href="https://docs.google.com/a/slack-corp.com/forms/d/e/1FAIpQLSfzjVoCM7ohBnjWf7eDYQxzti1EPpinsIJQA5RAUBwJKRUQHg/viewform">Contributor License Agreement</a></li>
+                </ul>
+
+                <p id="footer_signature">Made with <i class="ts_icon ts_icon_heart"></i> by Slack<br/>and our Lovely
+                    Community
+                </p>
+
+            </div>
+
+        </nav>
+
+        <div class="col span_3_of_4">
+            {{ content }}
+        </div>
+    </div>
+</div>
+
+<footer>
+    <p class="light tiny align_center">© 2019- Slack Technologies, LLC and contributors</p>
+</footer>
+
+{% include analytics.html %}
+
+</body>
+</html>

package/docs/_layouts/page.html

@@ -0,0 +1,10 @@
+---
+layout: default
+---
+
+<h1>{% if page.title %}{{ page.title }}{% else %}{{ site.title }}{% endif %}</h1>
+
+<div class="card">
+    {{ content }}
+</div>
+

package/docs/_pages/FAQ.md

@@ -0,0 +1,63 @@
+---
+layout: page
+title: Frequently Asked Questions
+permalink: /faq
+hidden: true
+order: 6
+headings:
+    - title: What even is this?
+    - title: OMG I found a bug!
+    - title: Hey, there's a feature missing!
+    - title: I'd like to contribute...but how?
+    - title: How do I compile the documentation?
+---
+
+## What even is this?
+
+{{ site.product_name }} is an adapter that allows you to connect Hubot to Slack. In addition to making it easy to run
+your Hubot scripts in Slack, it also provides basic mechanisms for using the Slack Web API.
+
+On the other hand, {{ site.product_name }} is _not_ a high-level bot development framework, nor is it, really, the best
+way to get started writing a Slack App. If you are interested in building Slack bots for widespread distribution in
+JavaScript, maybe you should have a look at [BotKit](https://howdy.ai/botkit/) or [Slapp](https://github.com/BeepBoopHQ/slapp).
+
+## OMG I found a bug!
+
+Well, poop. Take a deep breath, and then let us know by
+[opening an issue](https://github.com/{{ site.github_username }}/{{ site.repo_name }}/issues). If you're feeling
+particularly ambitious, why not
+[submit a bugfix?](https://github.com/{{ site.github_username }}/{{ site.repo_name }}/pulls).
+
+## Hey, there's a feature missing!
+
+There's always something more that could be added! You can
+[open an issue](https://github.com/{{ site.github_username }}/{{ site.repo_name }}/issues) to start a discussion around
+the feature, that's a good start. If you're feeling particularly ambitious, why not write the feature yourself, and
+[submit a PR!](https://github.com/{{ site.github_username }}/{{ site.repo_name }}/pulls). We love feedback and we love
+help and we don't bite. Much.
+
+## I'd like to contribute...but how?
+
+What an excellent question. First of all, please have a look at our general
+[contributing guidelines](https://github.com/{{ site.github_username }}/{{ site.repo_name }}/blob/master/.github/contributing.md).
+We'll wait for you here.
+
+All done? Great! While we're super excited to incorporate your new feature into {{ site.product_name }}, there are a
+couple of things we want to make sure you've given thought to.
+
+ * Please write unit tests for your new code. But don't _just_ aim to increase the test coverage, rather, we expect you
+    to have written _thoughtful_ tests that ensure your new feature will continue to work as expected, and to help future
+    contributors to ensure they don't break it!
+ * Please document your new feature. Think about _concrete use cases_ for your feature, and add a section to the
+    appropriate document (probably
+    "[basic_usage.md](https://github.com/{{ site.github_username }}/{{ site.repo_name }}/blob/master/docs/_pages/basic_usage.md)"),
+    including a _complete_ sample program that demonstrates your feature.
+
+Including these two items with your pull request will totally make our day—and, more importantly, your future users' days!
+
+On that note...
+
+## How do I compile the documentation?
+
+If you are editing one of the many markdown files in the `docs` folder, there is nothing you need to do: GitHub will
+do the right thing automatically. Hooray!