# How did Publisher Weekly create Resource page?

**URL:** <https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947>\
**Category:** Themes\
**Created:** [June 7, 2020, 3:09pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947 "2020-06-07T15:09:03Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![jasonwojo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jasonwojo/32/11109_2.png) [@jasonwojo](https://forum.ghost.org/u/jasonwojo)\
**Post date:** [June 7, 2020, 3:09pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/1 "2020-06-07T15:09:03Z")

</div>

Publisher Weekly has a great [Resource page](https://publisherweekly.org/resources/). I’d love to know how this was created. Using Collections? Channels? Any tips on building out a similar resource section would be great.

Also, how was it setup so each post leads directly to the resource utilizing it’s URL?

---

<div class="post-metadata">

**Author:** ![denvergeeks](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/denvergeeks/32/7401_2.png) [@denvergeeks](https://forum.ghost.org/u/denvergeeks)\
**Post date:** [June 8, 2020, 8:38pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/2 "2020-06-08T20:38:30Z")

</div>

@jasonwojo It looks like the Team Ghost is using the third-party “[Curated Newsletter](https://www.google.com/search?q=curated+newsletter)” web app [**Revue**](https://www.getrevue.co/):

 ![ink](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/2X/0/0ba0326ba2513af6ddef2d83a23e7ce47d9543ea.png)

There are many of these we can use…

[**elink.io**](https://about.elink.io/revue-alternative) is another one.

---

<div class="post-metadata">

**Author:** ![vikaspotluri123](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/vikaspotluri123/32/24_2.png) [@vikaspotluri123](https://forum.ghost.org/u/vikaspotluri123)\
**Post date:** [June 8, 2020, 11:43pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/3 "2020-06-08T23:43:38Z")

</div>

I’m not entirely sure how it differs, because I see some duplicate content, but [https://publisherweekly.org/](https://publisherweekly.org/) is run on Ghost 😕

---

<div class="post-metadata">

**Author:** ![jasonwojo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jasonwojo/32/11109_2.png) [@jasonwojo](https://forum.ghost.org/u/jasonwojo)\
**Post date:** [June 9, 2020, 10:22pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/4 "2020-06-09T22:22:31Z")

</div>

Yes, what I’m trying to figure out is their resource section specifically.

---

<div class="post-metadata">

**Author:** ![Kym](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kym/32/1136_2.png) [@Kym](https://forum.ghost.org/u/Kym)\
**Post date:** [June 10, 2020, 5:37am UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/5 "2020-06-10T05:37:40Z")

</div>

Hey everyone!

Publisher Weekly is now using Ghost’s native [newsletter feature](https://ghost.org/docs/members/email-newsletters/) to send the emails each week. The website itself is built using our Handlebars theme layer.

As for the resource page, this is a [custom content collection](https://ghost.org/tutorials/creating-content-collections/). Each item is created as a post in Ghost Admin and our theme pulls in the relevant information to the `/resources/` page. We use tags to categorise the resources, the custom excerpt for the resource URL and the feature image for the resource logo :)

---

<div class="post-metadata">

**Author:** ![denvergeeks](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/denvergeeks/32/7401_2.png) [@denvergeeks](https://forum.ghost.org/u/denvergeeks)\
**Post date:** [June 10, 2020, 8:15pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/6 "2020-06-10T20:15:13Z")

</div>

Thank you @Kym for explaining that functionality. Specifically, can you share the code for the **navigation** , i.e what is generating the **.resources-container** and **.resources-sidebar**?

---

<div class="post-metadata">

**Author:** ![jasonwojo](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/jasonwojo/32/11109_2.png) [@jasonwojo](https://forum.ghost.org/u/jasonwojo)\
**Post date:** [June 11, 2020, 3:42am UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/7 "2020-06-11T03:42:01Z")

</div>

Ah, I was wondering how you were pulling a URL, using excerpt is a very clever way to do it. Thank you for the explanation.

---

<div class="post-metadata">

**Author:** ![Kym](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kym/32/1136_2.png) [@Kym](https://forum.ghost.org/u/Kym)\
**Post date:** [June 11, 2020, 5:43am UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/8 "2020-06-11T05:43:08Z")

</div>

Each category is just a tag archive, and the sidebar is getting a list of tags:

```handlebars
<div class="resources-sidebar">
    <div class="resources-sidebar-wrapper">
        <h3>Show me...</h3>
        <a href="/resources/"><img src="{{asset "img/resources.svg"}}" alt="Resources" /> Everything</a>
        {{#get "tags" filter="slug:-news" as |tag|}}
        {{#foreach tag}}

        <a href="{{url}}">
            {{#if feature_image}}
            <img src="{{img_url feature_image}}" alt="{{name}}" />
            {{/if}}
            {{name}}
        </a>

        {{/foreach}}
        {{/get}}
    </div>
</div>

```

---

<div class="post-metadata">

**Author:** ![denvergeeks](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/denvergeeks/32/7401_2.png) [@denvergeeks](https://forum.ghost.org/u/denvergeeks)\
**Post date:** [June 11, 2020, 6:08pm UTC](https://forum.ghost.org/t/how-did-publisher-weekly-create-resource-page/14947/9 "2020-06-11T18:08:06Z")

</div>

Thank you @Kym!!!