Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Time/Date Bound Rendered Content for the Opening & Closing of FT Program #457

Open
4 tasks
daaimah123 opened this issue Jan 2, 2025 · 2 comments
Open
4 tasks
Labels
application-automation issues related to automating the application process course-management issues related to automating the course management enhancement ❌ not-ready-for-work this issue is not ready to be picked up

Comments

@daaimah123
Copy link
Collaborator

daaimah123 commented Jan 2, 2025

Changing the website areas twice a year with the same text and links feels redundant. Can this be automated to render content based on the times / dates we specify?

Please note that some of these changes (specifically creating global variables), will be created with the sole purpose for use in building the application-process-automation and the course-management-software.

Proposed Global Variables

Many cohort-and-year-specific references will need to be changed in the mentor and full-time-program pages. These are conceptual and final naming will need to be better thought out and intentional.

  • Year
  • Month
  • Cohort
    • H1 for cohort during January - May
    • H2 for during July - November
  • Dates (open-date to start-day should span around 18 weeks)
    • closed = period between early-december to mid-october or mid-june to late april (close-date to open-date)
    • opened = period between mid-october to early-december or late-april to mid-june (open-date to close-date)
    • open-date
    • close-date = open-date + 3-4 weeks
    • extension-date = close-date + 2 weeks
    • extension-close-date = close-date + 2 weeks
    • info-session = open-date + 3 weeks (on a Tuesday or Thursday)
    • application-workshop = close-date + next week (two sessions)
    • pair-programming-with-staff = application workshop + next week
    • take-home-code-challenge = pair-programming-with-staff + next week
    • staff-board-interview-financial-convos = take-home-code-challenge + next week
    • notification-day = staff-board-interview-financial-convos + next week
    • onboarding-day = notification-day + 1 week
    • pre-work-start = onboarding-day + 1 day
    • start-day = pre-work-start + 4.5 weeks
  • Short_Form = "https://forms.gle/Y77pMRqRvSAyF2uT6"
  • Interest_Form = "https://docs.google.com/forms/d/e/1FAIpQLSfUdyIAfcU5KSqtYH5J5iPRgu-yycHdebnUKygQLEv-m7oVMw/viewform"
  • Eventbrite = "https://www.eventbrite.com/o/techtonica-11297022451"

Home Page CTA

  • CLOSED: text "Outsource your software work!" render to "render_sponsor_page"
  • OPENED: text "Apply by {CLOSING-DATE} (12pm PT)!" render to "render_ft_program_page"

FT Page CTA 1

  • CLOSED: text "Fill out our interest form to be notified about next cohort" link to {INTEREST_FORM}
  • OPENED: text "Apply by {CLOSING-DATE} (12pm PT)!!" link to {SHORT_FORM}
  • EXTENSION: text "Apply by {EXTENSION-DATE} (12pm PT)!!" link to {SHORT_FORM}

FT Page CTA 2

  • CLOSED: text " Sign up to join our events" link to {EVENTBRITE}
  • OPENED: text "Apply by {CLOSING-DATE} (12pm PT)!" link to {SHORT_FORM}
  • EXTENSION: text "Apply by {EXTENSION-DATE} (12pm PT)!!" link to {SHORT_FORM}

Mentor Page

This may need to stay a manual change as many of the dates are dependent upon the (proposed variable) dates that will be plugged into this time/date bound rendering as well as the Mentor Program Manager & program staff's schedule. This proposal is to keep things general until those specific updates are made:

July Cohort

    <h3>July {YEAR} Cohort Timeline</h3>
    <table class="mentor" cellpadding="0" cellspacing="0">
      <tr>
        <td>March - April</td>
        <td>Mentor applications open</td>
      </tr>
      <tr>
        <td>March - April</td>
        <td>Mentor interviews</td>
      </tr>
      <tr>
        <td>May - May</td>
        <td>Mentor acceptance letter</td>
      </tr>
      <tr>
        <td>{ONBOARDING-DAY}</td>
        <td>Mentor and participant onboarding day</td>
      </tr>
      <tr>
        <td>{PRE-WORK-START} </td>
        <td>Mentor and participant matching</td>
      </tr>
      <tr>
        <td>{PRE-WORK-START} {YEAR}</td>
        <td>Support participants doing pre-work</td>
      </tr>
       <tr>
        <td>{START-DAY} {YEAR}</td>
        <td>First day of {H1/H2} {YEAR} cohort</td>
      </tr>
      <tr>
        <td>June - November {YEAR}</td>
        <td>Support during Techtonica training</td>
      </tr>
      <tr>
        <td>November - June {YEAR}</td>
        <td>Support during placement or job search</td>
      </tr>
    </table>

January Cohort

    <h3>January {YEAR} Cohort Timeline</h3>
    <table class="mentor" cellpadding="0" cellspacing="0">
      <tr>
        <td>October - November</td>
        <td>Mentor applications open</td>
      </tr>
      <tr>
        <td>November - December</td>
        <td>Mentor interviews</td>
      </tr>
      <tr>
        <td>December</td>
        <td>Mentor acceptance letter</td>
      </tr>
      <tr>
        <td>{ONBOARDING-DAY}</td>
        <td>Mentor and participant onboarding day</td>
      </tr>
      <tr>
        <td>{PRE-WORK-START} </td>
        <td>Mentor and participant matching</td>
      </tr>
      <tr>
        <td>{PRE-WORK-START} {YEAR}</td>
        <td>Support participants doing pre-work</td>
      </tr>
       <tr>
        <td>{START-DAY} {YEAR}</td>
        <td>First day of {H1/H2} {YEAR} cohort</td>
      </tr>
      <tr>
        <td>January - June {YEAR}</td>
        <td>Support during Techtonica training</td>
      </tr>
      <tr>
        <td>June - December {YEAR}</td>
        <td>Support during placement or job search</td>
      </tr>
    </table>

This can be addressed in four stages:

  • global variables
  • homepage
  • full-time-program page
  • mentor page
@daaimah123 daaimah123 added enhancement application-automation issues related to automating the application process course-management issues related to automating the course management labels Jan 2, 2025
@MaggieFero
Copy link
Collaborator

You probably also want to combine "H1 = cohort during January - May" and "H2 = cohort during July - November" as a single "Cohort" variable, maybe cohort-short and cohort-long for H1/H2 versus "January-May" and "July-November"

@daaimah123
Copy link
Collaborator Author

Ah, I do see the benefit in that! 🧠 Adjusting

@daaimah123 daaimah123 added the ❌ not-ready-for-work this issue is not ready to be picked up label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
application-automation issues related to automating the application process course-management issues related to automating the course management enhancement ❌ not-ready-for-work this issue is not ready to be picked up
Projects
None yet
Development

No branches or pull requests

2 participants