# Integrating this community into LSST websites (docs/blogs)

**URL:** <https://www.rubin.community/t/integrating-this-community-into-lsst-websites-docs-blogs/60>\
**Category:** Meta\
**Tags:** square\
**Created:** [August 12, 2015, 7:33pm UTC](https://www.rubin.community/t/integrating-this-community-into-lsst-websites-docs-blogs/60 "2015-08-12T19:33:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jsick](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jsick/32/672_2.png) [@jsick](https://www.rubin.community/u/jsick)\
**Post date:** [August 12, 2015, 7:33pm UTC](https://www.rubin.community/t/integrating-this-community-into-lsst-websites-docs-blogs/60/1 "2015-08-12T19:33:42Z")

</div>

Since _[community.lsst.org](http://community.lsst.org)_ has no gatekeeper (anyone can instantly get an account), we can use this site to provide interactivity to other LSST web sites.

For example, should DM also want to run a technical blog (separate from EPO efforts), discourse could be used to the comment threads. In this case a user could comment via the forum, and the comments would also appear on the blog via Discourse’s API. Here’s a Jekyll plugin that achieves this:

> **[oblakeerickson/jekyll\_discourse\_comments](https://github.com/oblakeerickson/jekyll_discourse_comments)**
>
> A Jekyll plugin for adding Discourse comments. Contribute to oblakeerickson/jekyll\_discourse\_comments development by creating an account on GitHub.

Another integration would be with the documentation. We could provide UI within the docs that would let a user easily get to discussions related to an API, or ask questions about an API.

---

<div class="post-metadata">

**Author:** ![mjuric](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/mjuric/32/31_2.png) [@mjuric](https://www.rubin.community/u/mjuric)\
**Post date:** [August 14, 2015, 1:19am UTC](https://www.rubin.community/t/integrating-this-community-into-lsst-websites-docs-blogs/60/2 "2015-08-14T01:19:51Z")

</div>

> [@jsick](#):
>
> Another integration would be with the documentation. We could provide UI within the docs that would let a user easily get to discussions related to an API, or ask questions about an API.

+1. I always got huge value out of user comments (and contributed code snippets) in [PHP’s documentation](http://php.net/manual/en/function.phpinfo.php).