Project Volunteer and Researcher

We need to output HTML fragment with sections for headings: About the role? Actually we have sections: About This Opportunity, Volunteer Requirements, maybe Causes? The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting: Summary: Quick online volunteering opportunities that allow anyone anywhere to contribute to TecNurtur's mission. Location Virtual / Remote This opportunity can be done from anywhere. When Opportunity Type Ongoing - Start Anytime Schedule Flexible About This Opportunity TecNurtur offers a growing board of flexible volunteer opportunities for students and community members who want to contribute to meaningful technology and community projects. Instead of applying for one fixed role, volunteers can browse current opportunities and choose projects that match their interests, skills, and available time. Opportunities may include technology and web projects, graphic design, outreach, research, event support, educational resources, and other short-term community initiatives. Many projects are designed as flexible microvolunteering opportunities and can be completed in just a few hours, while others offer longer-term involvement. Browse Current Opportunities And Choose a Project At tecnurtur.org/contribute Volunteer Requirements Whether you meet these requirements or not, we encourage you to share your interest in us. You may still be a fit for a different opportunity with our organization. No Requirements Causes Community & Social Services Marketing & Communications Digital & Creative Grassroots Projects Virtual-Online Volunteering Children & Youth Computers & Tech Support Homeless Shelters, Housing, & Food Banks Seniors Skills & Experience Digital/Graphic Design Market Research Tags research interviewing online forms, tech volunteerhours We need to decide sections: About This Opportunity (maybe "About the role" heading). Volunteer Requirements (maybe "Requirements" heading). Causes maybe "Skills"? Actually "Causes" is list of cause areas; could be a section like "Focus Areas". But instructions only list certain headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use those headings if content matches. We have "About This Opportunity" -> map to About the role. Volunteer Requirements -> Requirements. Skills & Experience -> Skills. Causes maybe not a standard heading; could be omitted or maybe we could treat as "Qualifications"? Not exactly. Could be "Responsibilities"? Not really. The posting doesn't have explicit responsibilities list; it's more about opportunities. Could we create a "Responsibilities" section from the list of opportunities? Possibly: "Opportunities may include technology and web projects, graphic design, outreach, research, event support, educational resources, and other short-term community initiatives." That could be responsibilities/duties. So we could have a Responsibilities section with a

  list. We also have Schedule Flexible mentioned. Should we create a Schedule section? The posting says "Schedule Flexible". That's specific content, so we can include a Schedule section with

  Flexible.

  maybe. We have Location Virtual/Remote; could be minor metadata; we could drop or put in a short

  . The instruction: fold minor metadata into a short

  or drop it. So we could include a

  Location: Virtual/Remote.

  maybe. We have Opportunity Type Ongoing - Start Anytime; could be minor metadata. We have Tags etc; maybe drop. We need to preserve all substantive information; not invent or summarize away detail. So we need to include the description text, the list of opportunities, the volunteer requirements statement, the skills/experience, the causes list maybe as a list? The instruction says use
  • for any list of duties/requirements/benefits. Causes is a list; we could treat as a list under maybe a heading "Focus Areas" but not in allowed headings. Could we put under Skills? Not appropriate. Could we create a section "Causes" using

    ? The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings; we should not create other headings. So we should not create a Causes heading. Instead we could incorporate causes into a paragraph or maybe under Skills? But that would misrepresent. Better to include them as a

    sentence listing them. Similarly Skills & Experience: we can make a Skills heading with

    list? It says "Skills & Experience Digital/Graphic Design Market Research". That's two items. Could be a list. Volunteer Requirements: The text says "Volunteer Requirements Whether you meet these requirements or not, we encourage you to share your interest in us. You may still be a fit for a different opportunity with our organization. No Requirements". That's contradictory: says Volunteer Requirements then says No Requirements. We need to preserve that exactly. So we can put that as a

    under Requirements heading. About This Opportunity: we can put as prose under About the role heading. Responsibilities: we can list the opportunities. Schedule: we have "Schedule Flexible". So we can put

    Flexible.

    under Schedule heading. We also have Location Virtual/Remote and Opportunity Type Ongoing - Start Anytime; we could combine into a short

    maybe before sections. We must not include boilerplate like application instructions (there is "Browse Current Opportunities And Choose a Project At tecnurtur.org/contribute" - that's basically a call to action; is that application instruction? It's more like a direction to browse. Might be considered application instruction? The instruction says remove application instructions. That line is basically telling how to apply/participate. Might be considered application instruction. Safer to drop it. We also have "Tags research interviewing online forms, tech volunteerhours" - likely metadata; drop. We need to preserve all substantive information: the description, the list of opportunities, the volunteer requirements statement, the skills/experience, the causes list, schedule flexibility, location, opportunity type. We need to avoid filler placeholder text like "commensurate with experience" etc. Not present. We need to output only HTML fragment. Let's craft:

    About the role

    TecNurtur offers a growing board of flexible volunteer opportunities for students and community members who want to contribute to meaningful technology and community projects. Instead of applying for one fixed role, volunteers can browse current opportunities and choose projects that match their interests, skills, and available time. Opportunities may include technology and web projects, graphic design, outreach, research, event support, educational resources, and other short-term community initiatives. Many projects are designed as flexible microvolunteering opportunities and can be completed in just a few hours, while others offer longer-term involvement.

    Responsibilities

    • Technology and web projects
    • Graphic design
    • Outreach
    • Research
    • Event support
    • Educational resources
    • Other short-term community initiatives

    Requirements

    Volunteer Requirements Whether you meet these requirements or not, we encourage you to share your interest in us. You may still be a fit for a different opportunity with our organization. No Requirements

    Skills

    • Digital/Graphic Design
    • Market Research

    Schedule

    Flexible.

    We might also include location and opportunity type as a short paragraph before sections: maybe

    Location: Virtual/Remote. Opportunity Type: Ongoing - Start Anytime.

    But the instruction says fold minor metadata into a short

    or drop it. So we can add a

    at top:

    Location: Virtual/Remote. Opportunity Type: Ongoing - Start Anytime.

    We must not repeat job title as heading (we didn't). No Job ID. We must not include Pay/Benefits sections (none). Good. We must not create sections with filler text; we have real content. Check for duplication: we have not duplicated lines. We have preserved all substantive info: description, opportunities list, volunteer requirements statement, skills list, schedule flexibility, location, opportunity type. Causes list not included; we dropped it. Is causes substantive? It lists cause areas: Community & Social Services, Marketing & Communications, Digital & Creative, Grassroots Projects, Virtual-Online Volunteering, Children & Youth, Computers & Tech Support, Homeless Shelters, Housing, & Food Banks, Seniors. That is substantive. We should preserve it. Where to put? Could be under Skills? Not appropriate. Could be under Qualifications? Not exactly. Could be under About the role as additional detail? Could add a sentence: "Causes include Community & Social Services, Marketing & Communications, Digital & Creative, Grassroots Projects, Virtual-Online Volunteering, Children & Youth, Computers & Tech Support, Homeless Shelters, Housing, & Food Banks, Seniors." That would preserve the info without a separate heading. That seems acceptable. Similarly Tags we can drop. Thus we need to incorporate causes into a paragraph maybe under About the role or as its own paragraph. Let's add a paragraph after the description: "

    Causes include Community & Social Services, Marketing & Communications, Digital & Creative, Grassroots Projects, Virtual-Online Volunteering, Children & Youth, Computers & Tech Support, Homeless Shelters, Housing, & Food Banks, Seniors.

    " Now we have preserved causes. Check if any other substantive info: "Skills & Experience Digital/Graphic Design Market Research" we captured as Skills list. Volunteer Requirements we captured. Opportunity Type Ongoing - Start Anytime we captured in metadata paragraph. Location Virtual/Remote captured. Schedule Flexible captured. All good. Now output HTML fragment. We must not include markdown code fences. Just plain HTML. Let's produce:

    Location: Virtual/Remote. Opportunity Type: Ongoing - Start Anytime.

    About the role

    TecNurtur offers a growing board of flexible volunteer opportunities for students and community members who want to contribute to meaningful technology and community projects. Instead of applying for one fixed role, volunteers can browse current opportunities and choose projects that match their interests, skills, and available time. Opportunities may include technology and web projects, graphic design, outreach, research, event support, educational resources, and other short-term community initiatives. Many projects are designed as flexible microvolunteering opportunities and can be completed in just a few hours, while others offer longer-term involvement.

    Causes include Community & Social Services, Marketing & Communications, Digital & Creative, Grassroots Projects, Virtual-Online Volunteering, Children & Youth, Computers & Tech Support, Homeless Shelters, Housing,