Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Capture professional advisor info

Open
#135 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
full-stack

Research direction

Start by reviewing issue #107 and the attached “About you” paper form, then use the open questions here to understand the intended advisor-information flow. Done means the use case, data model or lookup needs, privacy considerations, and onboarding placement have been decided clearly enough to define implementation work.

Written by the indexing model from the issue text.

Description

Extracted out from #107 .

The 'About you' paper form (see issue above) includes a section about financial advisors.

Image

We weren't sure that including these details in the 'about you' form itself made sense, so omitted it for now and created this issue to think through some open questions:

  • How is this information used? Is there a use case for being able to 'look up' advisors?
  • Is there a separate database of known advisors? Would it helpful to build up a list of advisors as we collect this info?
  • Would it be helpful show users a list of known advisors to choose from? Would doing so bring up any privacy issues?
  • While it probably made sense in a paper-centric flow to capture both advisor and narrative details at the same time, is that still the best flow on the app?
  • Where might advisor info fit in a holistic onboarding flow?
Dominant language
Ruby
Stars
12
Forks
1
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rubyforgood/community_foundation

All issues in rubyforgood/community_foundation

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.