# Community Call - July 8th, 2020

**URL:** https://forum.interledger.org/t/community-call-july-8th-2020/1060
**Category:** Community
**Tags:** community-call-agenda
**Created:** [June 30, 2020, 5:47pm UTC](https://forum.interledger.org/t/community-call-july-8th-2020/1060 "2020-06-30T17:47:05Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![adrianhopebailie](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/adrianhopebailie/32/31_2.png) [@adrianhopebailie](https://forum.interledger.org/u/adrianhopebailie)
#### Post date: [June 30, 2020, 5:47pm UTC](https://forum.interledger.org/t/community-call-july-8th-2020/1060/1 "2020-06-30T17:47:05Z")

</div>

The next community call will be on 2020-07-08T16:00:00Z

[Dial in via Zoom](https://zoom.us/s/377506344)

Please post topics you’d like to discuss here and some background context for the rest of the community (preferably not a few hours before the call so everyone has a chance to do some background reading).

---

<div class="post-metadata">

### Author: ![matdehaast](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/matdehaast/32/191_2.png) [@matdehaast](https://forum.interledger.org/u/matdehaast)
#### Post date: [July 1, 2020, 8:41am UTC](https://forum.interledger.org/t/community-call-july-8th-2020/1060/2 "2020-07-01T08:41:13Z")

</div>

Can we discuss the website revamp and wording.

- Setup a group to drive the process
- Decide on how we want to do it (ie vuepress etc)

---

<div class="post-metadata">

### Author: ![adrianhopebailie](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/adrianhopebailie/32/31_2.png) [@adrianhopebailie](https://forum.interledger.org/u/adrianhopebailie)
#### Post date: [July 6, 2020, 4:35pm UTC](https://forum.interledger.org/t/community-call-july-8th-2020/1060/3 "2020-07-06T16:35:53Z")

</div>

PROPOSAL

Move the Interledger website to Docusaurus for consistency, we’re already using it for [Open Payments](https://openpayments.dev) and [Web Monetization](https://webmonetization.org) and it’s working well.

Move the published RFCs into the same repo as the website and update the process to use the RFCs repo as a place for WIP RFCs and move them to the website when they’re ready.

---

<div class="post-metadata">

### Author: ![html5cat](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/html5cat/32/18_2.png) [@html5cat](https://forum.interledger.org/u/html5cat)
#### Post date: [July 6, 2020, 9:09pm UTC](https://forum.interledger.org/t/community-call-july-8th-2020/1060/4 "2020-07-06T21:09:13Z")

</div>

+1 on Docusaurus and consistency 🐾

---

<div class="post-metadata">

### Author: ![kincaid](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.interledger.org/kincaid/32/39_2.png) [@kincaid](https://forum.interledger.org/u/kincaid)
#### Post date: [July 7, 2020, 3:52pm UTC](https://forum.interledger.org/t/community-call-july-8th-2020/1060/5 "2020-07-07T15:52:01Z")

</div>

> [@adrianhopebailie](#):
>
> Move the Interledger website to Docusaurus

Open to Docusaurus though I think we should probably improve the theme a bit 🙂

> [@adrianhopebailie](#):
>
> Move the published RFCs into the same repo as the website and update the process to use the RFCs repo as a place for WIP RFCs and move them to the website when they’re ready.

This seems like it’d still require manual synchronization work, no? I think it’s good to keep the RFCs repo as the canonical source of truth for both WIP and finalized docs, and then separately have the website publish them.

IMO, the problem with the current website is that it requires manually rebuilding based on the RFCs repo, but I think we can fix this: we just need a push in the rfcs repo to trigger a CI run in the website repo, which would redeploy the site. We could use Github Actions’ `repository_dispatch` event and e.g. [this action](https://github.com/peter-evans/repository-dispatch) to accomplish that.
