Skip to main content

How to modify job board template to let hiring managers post jobs and view applicants who applied via forms?

hello, I'm building a simple job board for a client, where both hiring managers and job seekers can create accounts. Hiring managers should be able to post job listings and view details of job applicants who apply for those positions.

Best using the new job board template created by Julian 🙂
https://www.memberstack.com/webflow-templates/premium-job-board

It's really good but doesn't cover this use case.

I want them to post jobs, and see the applicants who applied.
on Julian Galluzzo Template you apply by reaching out via inbox, not from the form.

Also, my client doesn't have enough budget for TalkJS Integration, so just apply via form for now.
is it possible 🙏

Would appreciate your feedback on how I can approach this.

Thank you

9 comments

  • Shadi null
    Shadi null

    You'd need to customize the project to your needs. For example, you can delete the whole TalkJS section, and then use a form submission to create an application, and have a hidden field that references the project CMS ID within the form (the user shouldn't be able to see or alter this, so give it the 'required', 'hidden', and 'read only' tags).

    Then on the backend use the CMS ID to reference the job owner and give them a dashboard to view it all on. Filter by account owner as reference. Hope that helps.

    0
  • Manuel Ogomigo
    Manuel Ogomigo OP

    Got it.
    Doing this would mean each job application would have to be created as a CMS item, to be referenced with the job the hiring manager created.

    I don't think it will work well, or maybe I'm not getting it.

    0
  • Shadi null
    Shadi null

    Alternatively, you could just send them (the project owner) an email with all the contents of the application.

    You could maybe also consider adding literal <div> </div> code in a CMS text field for the project CMS item and have that only be visible to the owner.

    You'd then have each application append itself to that text field and then create an embed on their dashboard that displays it as a dashboard. That way its all 1 single CMS item. Though I am unsure if there is a character limit on text fields in a CMS.

    it would be quite complex to build but you could essentially create a make scenario that populates the field with content like this, and then also include a CSS to style it all.

    (This is an over the top example)

    <div class="row"><div class="topic-avatar"><div class="post-avatar"><a class="trigger-user-card main-avatar " href="/u/Julian_Galluzzo" data-user-card="Julian_Galluzzo" aria-hidden="true" tabindex="-1"><img alt="" width="48" height="48" src="https://sea2.discourse-cdn.com/webflow1/user_avatar/discourse.webflow.com/julian_galluzzo/96/437740_2.png" aria-hidden="true" loading="lazy" tabindex="-1" class="avatar"></a></div></div><div class="topic-body clearfix"><div role="heading" aria-level="2" class="topic-meta-data"><div class="names trigger-user-card"><span class="first username"><a href="/u/Julian_Galluzzo" data-user-card="Julian_Galluzzo" class="">Julian_Galluzzo</a></span><span class="user-title user-title--community-specialist-">Community Specialist </span></div><div class="post-infos"><div class="post-info post-date"><a class="widget-link post-date" href="/t/webflow-429-too-many-requests-error-in-make-com/257125/4?u=shadi" title="Post date"><span title="Oct 12, 2023 4:29 pm" data-time="1697120976884" data-format="tiny" class="relative-date">23h</span></a></div><div class="read-state read" title="Post is unread"><svg class="fa d-icon d-icon-circle svg-icon svg-node" aria-hidden="true"><use xlink:href="#circle"></use></svg></div></div></div><div class="regular contents"><div class="cooked"><p>This is absolutely destroying all of my scenarios right now and is beyond problematic
 I really really hope this gets fixed soon! Probably the most impactful Webflow issue I have seen to date
 including the entire designer being down</p></div><section class="post-menu-area clearfix"><nav class="post-controls collapsed"><div class="actions"><button class="widget-button btn-flat reply create fade-out btn-icon-text" title="begin composing a reply to this post" aria-label="Reply to post #4 by @Julian_Galluzzo"><svg class="fa d-icon d-icon-reply svg-icon svg-node" aria-hidden="true"><use xlink:href="#reply"></use></svg><span class="d-button-label">Reply</span></button><button class="widget-button btn-flat show-more-actions no-text btn-icon" title="show more"><svg class="fa d-icon d-icon-ellipsis-h svg-icon svg-node" aria-hidden="true"><use xlink:href="#ellipsis-h"></use></svg></button><div class="discourse-reactions-actions has-reactions has-reacted has-used-main-reaction" id="discourse-reactions-actions-643946-right" data-click-outside="true"><div class="discourse-reactions-picker"></div><div class="discourse-reactions-double-button"><div class="only-like discourse-reactions-counter" id="discourse-reactions-counter-643946-right" data-click-outside="true"><div class="discourse-reactions-state-panel max-length-1"></div><span class="reactions-counter">5</span></div><div title="You can no longer remove your reaction" class="discourse-reactions-reaction-button"><button title="You can no longer remove your reaction" class="btn-toggle-reaction-like btn-icon no-text reaction-button"><svg class="fa d-icon d-icon-heart svg-icon svg-node" aria-hidden="true"><use xlink:href="#heart"></use></svg></button></div></div></div></div></nav></section></div><section class="post-actions">
      </section><div class="post-links-container"></div></div></div>
    0
  • Manuel Ogomigo
    Manuel Ogomigo OP

    I don't understand anymore 😱đŸ˜Ș

    So for context I have a members cms item, project owner, and jobs.
    The members can apply for jobs.

    And the project own we should be able to see those that apply and reach out to them via email if Thier jobs details meets his requirements.
    Yeah aside of ending up with lot of cms items, because the platform would allow multiple project owners post jobs.

    I dont want it to get too complex, and don't sincerely don't know if adding the code in the cms item would work, because we would want to show the member job details they applied with.

    0
  • Shadi null
    Shadi null

    Why not combine the members CMS item and the Project Owner CMS items into 1? Then filter what the user sees with memberstack plans & Gated content? I assume the project owners will have to pay a different price than people that apply to jobs right?

    Theoretically you can add whatever data you want to add to the code embed as long as you have it referenced somewhere (like an airtable DB, or part of the form submission, etc). So you could display whatever info you want, in whatever format you'd like. The only real concern is if there is a character limit to rich text fields or plain text fields.

    It definitely works, I believe that's how the memberstacks website's commenting system used to work (I think they've since changed it to their new commenting system, but I could very well be wrong as I don't work at memberstack)

    Here's a tutorial from one of the co-founders of memberstack, walking you through how to embed comments (or in your case individual applications) into a CMS item.
    https://www.youtube.com/watch?v=va-9bm-eRtI

    Just a heads up, Julian Galluzzo might jump in this thread eventually and let you know their new "comments" system might be an easier/better fit for your needs. Unfortunely I have yet to experiment with that feature so I apologize in advanced if I sent you down the wrong rabbit hole.

    It might be worth taking a look at if maybe thats a better/easier option for you.

    I would encourage you join the commenting-beta slack channel (go to add channels/browse channels to find it), for now, here's a little copy paste from one of their posts.

    "Resources and documentation:

    What’s next:
    In the coming weeks, we’ll add additional UI and settings in the Memberstack dashboard and add (even more) data attributes.

    ✌ That’s all for now–we are so excited to see what you decide to build, and are here to help with questions and feedback along the way!"

    0
  • Julian Galluzzo
    Julian Galluzzo

    You could actually do this and have the applicants get added to the job as a multi reference field - that would work!

    0
  • Manuel Ogomigo
    Manuel Ogomigo OP

    Thanks Julian Galluzzo Yeah that would work but the issue is, Webflow only shows 5 multi-reference items, even if there are more than it

    0
  • Shadi null
    Shadi null

    That’s ONLY if you’re showing the multi-reference items as a collection within a collection. Essentially nested collections are limited to 5
    If you’re on the CMS items template page, there’s no limit to the multi-reference fields

    The way I handled what you’re trying to do is to show projects as 1 cms item and show a number of applicants on that project; then a button that says “show all applicants” that basically is a jetboost filter for another collection containing applicants for all projects the user owns. It filters the applicants based on the project they clicked on and presents them the list of applicants as individual CMS items

    0
  • Manuel Ogomigo
    Manuel Ogomigo OP

    Yeah that would work well.
    Thanks again

    0

Please sign in to leave a comment.

Sitemap