# Sharepoint Online spfx webpart

**URL:** https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044
**Category:** Feature
**Created:** [April 23, 2020, 6:36pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044 "2020-04-23T18:36:18Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![glwolverton](https://avatars.discourse-cdn.com/v4/letter/g/58956e/32.png) [@glwolverton](https://meta.discourse.org/u/glwolverton)
#### Post date: [April 23, 2020, 6:36pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/1 "2020-04-23T18:36:18Z")

</div>

Anyone built or know of an xpfx webpart for SP online?

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 23, 2020, 6:43pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/2 "2020-04-23T18:43:26Z")

</div>

What does this have to do with Discourse?

---

<div class="post-metadata">

### Author: ![glwolverton](https://avatars.discourse-cdn.com/v4/letter/g/58956e/32.png) [@glwolverton](https://meta.discourse.org/u/glwolverton)
#### Post date: [April 23, 2020, 6:57pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/3 "2020-04-23T18:57:34Z")

</div>

i am looking to add Discourse into my corporate SP online and did not want to iframe it

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [April 23, 2020, 7:04pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/4 "2020-04-23T19:04:43Z")

</div>

I don’t think you will be able to integrate it properly as a Client Side Web Part in Share Point. Putting Discourse in an iFrame also results in a bad user experience.

Discourse assumes it has full control over the page, and our recommendation is for it to live in a dedicated subdomain, where it can be themed to your company visual identity.

---

<div class="post-metadata">

### Author: ![glwolverton](https://avatars.discourse-cdn.com/v4/letter/g/58956e/32.png) [@glwolverton](https://meta.discourse.org/u/glwolverton)
#### Post date: [April 23, 2020, 7:06pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/5 "2020-04-23T19:06:43Z")

</div>

Thank you very much for that response…

---

<div class="post-metadata">

### Author: ![adamgpope](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/adamgpope/32/121658_2.png) [@adamgpope](https://meta.discourse.org/u/adamgpope)
#### Post date: [May 12, 2021, 12:23pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/6 "2021-05-12T12:23:32Z")

</div>

Perhaps I’ve a different use case than the OP; we don’t want to embed Discourse in its entirety into a Community’s Sharepoint CMS, but rather to provide a dynamic activity feed to drive people to engage with one another in Discourse. As such, I’ve been able to embed a list of topics filtered to a tag or category into a Sharepoint site without any dev effort by:

1. Following [the highly configurable embed instructions here](https://meta.discourse.org/t/embedding-a-list-of-discourse-topics-in-another-site/125911)
2. Saving the result as an .aspx page
3. Uploading the page to the site’s asset library
4. Going to a modern page and pasting the URL of the uploaded .aspx page into an ‘Embed’ webpart

Would be great to replace that clunky cluster-fudge with a configurable sPFX webpart… 😉

---

<div class="post-metadata">

### Author: ![Ibejammin2](https://avatars.discourse-cdn.com/v4/letter/i/d2c977/32.png) [@Ibejammin2](https://meta.discourse.org/u/Ibejammin2)
#### Post date: [April 5, 2022, 3:16pm UTC](https://meta.discourse.org/t/sharepoint-online-spfx-webpart/149044/7 "2022-04-05T15:16:29Z")

</div>

I am also looking for a solution like this, being able to pull a summary feed into a O365 sharepoint site would be amazing for us.
