# How far can you take customizing membership functionalities in ghost?

**URL:** <https://forum.ghost.org/t/how-far-can-you-take-customizing-membership-functionalities-in-ghost/37513>\
**Category:** Memberships & subscriptions\
**Created:** [April 2, 2023, 12:26am UTC](https://forum.ghost.org/t/how-far-can-you-take-customizing-membership-functionalities-in-ghost/37513 "2023-04-02T00:26:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![devinschumacher](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/devinschumacher/32/23825_2.png) [@devinschumacher](https://forum.ghost.org/u/devinschumacher)\
**Post date:** [April 2, 2023, 12:26am UTC](https://forum.ghost.org/t/how-far-can-you-take-customizing-membership-functionalities-in-ghost/37513/1 "2023-04-02T00:26:40Z")

</div>

how far can you take customizing membership functionalities in ghost?

does it extend beyond just saving bookmarks?

for example, could i build something more robust like [genius.com](http://genius.com) where people highlight lyrics in a song and add annotations about what they mean?

or even adding entire new songs? etc. ([Genius | Song Lyrics & Knowledge](https://genius.com/new))

 ![Screenshot 2023-04-01 at 17.26.02](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/3X/7/b/7b52d85eb56da6fa07873af686f0888c341cb002.png)

---

<div class="post-metadata">

**Author:** ![Cathy\_Sarisky](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/cathy_sarisky/32/25750_2.png) [@Cathy\_Sarisky](https://forum.ghost.org/u/Cathy_Sarisky)\
**Post date:** [April 2, 2023, 12:46pm UTC](https://forum.ghost.org/t/how-far-can-you-take-customizing-membership-functionalities-in-ghost/37513/2 "2023-04-02T12:46:13Z")

</div>

You’d need a third party API for something like that. The bookmark functionality is just using local storage on the user’s computer.

---

<div class="post-metadata">

**Author:** ![devinschumacher](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/devinschumacher/32/23825_2.png) [@devinschumacher](https://forum.ghost.org/u/devinschumacher)\
**Post date:** [April 2, 2023, 5:03pm UTC](https://forum.ghost.org/t/how-far-can-you-take-customizing-membership-functionalities-in-ghost/37513/3 "2023-04-02T17:03:16Z")

</div>

right now we are using fast api from our python backend. we have a mysql db.

so would the process be something like:

- take the new user data from signups
- store in DB
- facilitate user contribution functionliaty (and keeping track of it) via javascript that talked to the backend?

could we extend the ‘logged in’ UI in ghost or would i need a third party app for that part as well?

ty!