[bounty-to-hire]: create ui for newsletter

[apsinghdev]

newsletter page for pro users - bounty to hire

hi, i'm ajeet building opensox.ai.

this ticket is a bounty-to-hire - an open assignment for you to show your skills, win a bounty, and potentially work with me on opensox ai.

process

1. open assignment (it's paid)
2. 15 min call
3. offer

objectives

design and implement a newsletter page for pro users on opensox.ai that displays newsletters as blog posts.

requirements

core features

• organization by date: a way to organize newsletters by month and year
• rich content support: each newsletter article can have:
  • text
  • links
  • images
• content management: a way to easily add a blog (only by the team)
  • through code
  • document your approach in the pr
• newsletter listing: a place to see all newsletters in one place, ordered by date (latest on top)
• readability: each newsletter should be easy to read

minimal formatting features

each newsletter should support:

• bold text
• headings

design considerations

feel free to ask yourself these questions for better understanding:

• what is the best way to organize these newsletters?
• how can we make the reading experience optimal?
• what's the most efficient way to add new newsletters?

deadline

i'll announce the result on 17/nov/2025, 10PM IST.

evaluation criteria

your submission will be evaluated based on:

• end result (ui): how well the page looks and functions
• optimal code: clean, maintainable, and efficient code
• minimal, quick and simple: keep it straightforward and avoid over-engineering

submission requirements

before attempting

please consider:

• do your research (google and gpt) before asking questions
• it's okay to ask questions, but please do the research first
• if something isn't clear, feel free to ask
• if you want to add or delete something not mentioned in this issue, feel free to do so
• remember: the goal is "creating the best newsletter page for the user" - not to make the maintainer happy

things to include in your pr

• a screen recording of your submission
• a short description explaining your approach
• sample data for three newsletters
• documentation on how to add a blog
• make sure your pr doesn't have any conflicts

bounty

• if your pr is merged, you'll get the bounty irrespective of whether you get the offer or not
• you'll receive the bounty just after 24 hrs of merge
• you will get an additional bounty if the design and code are really good.

notes

• pls add 2-3 dummy newsletters to see things in action
• i may ask a couple of questions if there's something that's not very clear
• please raise a pr of your submission and make sure it doesn't have any conflicts
• keep everything in lowercase (including code, comments, and documentation where appropriate)
• no need to ask for the assignment. everyone is welcome to raise the PR.

---

good luck! looking forward to seeing your submissions.

[apsinghdev]

note: please attempt only when you are genuinely interested in building opensox along with me.

[huamanraj]

yaaayyyyy! PR is otw 🔜

[deveshru2712]

Hi @apsinghdev, I’m interested in this issue.
I’m thinking of using the Tiptap rich text editor since it’s lightweight, integrates easily with Next.js, and I’ve used it previously.

[apsinghdev]

@deveshru2712 go ahead. would love to see your submission.

[abrknine]

Hey @apsinghdev just a quick doubt on
-Newsletter will be added throught code

Should I create db schema(for newsletter) or an .md file in frontend would be fine

I'm planning for .md approach ( recently did that) ans later move it to db

Kindly clarify I'll love to contribute

[apsinghdev]

@abrknine hey, we don't have to store newsletter blogs in the db. just find a time saving and easy to use approach for the client side only.

[Rohs21]

@apsinghdev is it okay to make the newsletter content hardcoded for now in a newsletter.ts file?
or do we have to use contents from blog post? that is a bit confusing for me

[apsinghdev]

@Rohs21 yes, it's okay to hardcode the content. I have used the "newsletter as the blogs" meaning content is of newsletter but are presented as blogs.

[manojk0303]

submitted pr #157

features implemented:

• newsletter listing with search and filtering
• individual newsletter reading pages
• 3 demo newsletters
• comprehensive documentation
• premium-only access control

demo video: https://www.loom.com/share/be672f86641947fd8a46891a46775577

looking forward to your review! 🙏

[huamanraj]

@apsinghdev i have come up with a unique and very efficient solution for this and i will create the PR now! what if somebody copies that and tweaks some design?

[apsinghdev]

@huamanraj no one will copy it. as you are the original creator, you'll be first to get the chance.