# Any dev interested in $ to see if Marker.io can plug in with draft state?

**URL:** <https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702>\
**Category:** Marketplace\
**Created:** [February 27, 2023, 8:56am UTC](https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702 "2023-02-27T08:56:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![busfactor](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/busfactor/32/23230_2.png) [@busfactor](https://forum.ghost.org/u/busfactor)\
**Post date:** [February 27, 2023, 8:56am UTC](https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702/1 "2023-02-27T08:56:32Z")

</div>

sort of unrelated to most requests in this particular DEV forum, just wondering if any devs would be down to figure out, and document (in detail) an integration with [Marker.io](http://Marker.io) or a similar tool that addresses this particular feature/idea request of mine from earlier:  
[Editorial Assistant /Content Review Role with Marker.io integration?](https://forum.ghost.org/t/editorial-assistant-content-review-role-with-marker-io-integration/36701)

to clarify, if you could figure this out, i would gladly pay you (within reason!) to figure it out and document the app and integration for the larger ghost community - it sounds like many people could use a commenting-rights role (on drafts as well as published, but drafts are much more important), and without granting full editorial permissions (!)

see:

> **[Marker.io: Visual Website Feedback & Bug Reporting tool](https://marker.io/)**
>
> Collect client feedback and report bugs into Jira, Trello, Asana, Github directly from your site with screenshots, annotations, console logs, and more.

> **[Integrations marketplace](https://marker.io/integrations)**
>
> Find your favorite tool to integrate with Marker.io like Jira, Trello, Asana and a lot more!

custom: [https://tinyurl.com/nhh8c6dj](https://tinyurl.com/nhh8c6dj) (webhooks, not zapier!)

imho, what i’m struggling with, and not just because i’m not an engineer, is how one might access “draft state” without editor rights…

---

<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:** [February 27, 2023, 5:43pm UTC](https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702/2 "2023-02-27T17:43:52Z")

</div>

This is an interesting question.

There’s not a good way to hack the ghost admin side that doesn’t involve changes to core, although it’s possible to write one’s own code and run it separately, via access to the api. (This is the approach I took on Phantom Admin.)

BUT, there’s a lot of flexibility to add code to the front end, either with custom theme pages or code injection. So one approach might be to create a custom tier and put posts that are effectively ‘drafts’ into that tier, with no other access or visibility for any other tier. Then you make your content commenters members of that tier. So they’re looking at a published page and since it’s the front-end, you could add the widget javascript code to the page using the theme (or code injection).

And then it’d just be a question of going to [marker.io](http://marker.io) to look at the feedback, or else telling [marker.io](http://marker.io) what issue tracker you want your feedback sent to.

---

<div class="post-metadata">

**Author:** ![busfactor](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/busfactor/32/23230_2.png) [@busfactor](https://forum.ghost.org/u/busfactor)\
**Post date:** [February 27, 2023, 7:36pm UTC](https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702/3 "2023-02-27T19:36:07Z")

</div>

looks like marker heard my direct request to them earlier - what do you think:

> **[Ghost.org Integration](https://help.marker.io/en/articles/7034095-ghost-org-integration)**
>
> See below for how to collect feedback directly from your Ghost website using Marker.io!

---

<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:** [February 27, 2023, 7:41pm UTC](https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702/4 "2023-02-27T19:41:47Z")

</div>

Looks like it! :)

If you’re not limited to how many staff users you can have, this might be all you need.

---

<div class="post-metadata">

**Author:** ![busfactor](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/busfactor/32/23230_2.png) [@busfactor](https://forum.ghost.org/u/busfactor)\
**Post date:** [February 27, 2023, 7:43pm UTC](https://forum.ghost.org/t/any-dev-interested-in-to-see-if-marker-io-can-plug-in-with-draft-state/36702/5 "2023-02-27T19:43:33Z")

</div>

btw, my apologies: this is a very clever workflow hack, and then simply hide the tier from signups and add editorial assistants as complementary subscriptions! main idea behind marker is the location-specific commenting ability around long-form content. it also allows for workflow tweaks and adoption of an editorial process, replete with triaging for actual editors with rights, etc
