Website Redesign and Development (RFP)

We need to output HTML fragment with sections: About the role? Actually it's an RFP, not a job posting. But we follow 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 extract substantive content from the RFP. Given the text: "RFP Website Redesign and Development (RFP) Download PDF Organization Classical Association of the Middle West and South (CAMWS) Type Contract Salary $30,000 to $40,000 / Project-based Four-day Week No CAMWS, a regional learned society serving scholars, educators, and students of Greek, Latin, and classical antiquity (national membership of ~1,100), seeks proposals for a full redesign and redevelopment of its website. The project includes a public-facing redesign, member portal functionality (login, renewals, directory), conference registration with abstract submission and payment processing, and a modern CMS suited to a small nonprofit staff. Full scope includes visual design and a design system, WCAG 2.2 AA accessibility compliance, content migration with URL redirects, staff training and documentation, and post-launch support. Vendors should have demonstrated experience with nonprofit/membership organizations, ideally academic or scholarly associations, and familiarity with membership platforms, conference registration, and PCI-compliant payment processing. Proposals must include an executive summary, team bios, a portfolio of comparable work, technical approach, milestone-based timeline, migration plan, three client references, and an itemized cost proposal (development, hosting/licensing, ongoing support). Please see the full RFP in the PDF attached to this site. Proposal deadline: October 30, 2026 Submit to: nominating@camws.org Please use subject line “CAMWS Website RFP — [Vendor Name]” Contact: Professor Victoria Pagan Back to the Job Board" We need to remove boilerplate: "RFP Website Redesign and Development (RFP) Download PDF Organization Classical Association of the Middle West and South (CAMWS) Type Contract Salary $30,000 to $40,000 / Project-based Four-day Week No" maybe that's metadata. Also "Back to the Job Board". Also "Please see the full RFP in the PDF attached to this site." Might be considered instruction? It's not application instructions; it's referencing PDF. Might keep? It's not essential? It says "Please see the full RFP in the PDF attached to this site." That's a reference; maybe we can drop as it's not substantive? But it's part of the posting. However we need to preserve all substantive information. The PDF is not included; we can't include its content. So we can note that full RFP is in PDF. Might be considered a reference; we can keep a short p: "Full RFP details are available in the attached PDF." But we need to avoid filler. It's okay. We need sections: maybe About the role (description of project), Responsibilities (what vendor needs to do), Requirements (vendor qualifications), maybe Benefits? Not applicable. Pay: we have salary $30,000 to $40,000 / Project-based. That's pay info. So we should include Pay section. Schedule: "Four-day Week No"? Actually "Four-day Week No" maybe indicates not a four-day week? The line: "Type Contract Salary $30,000 to $40,000 / Project-based Four-day Week No". Could be that it's contract, salary range, project-based, four-day week? Not sure. Might be irrelevant. We'll not create Schedule unless explicit. There's no explicit schedule like working hours. So we skip Schedule. Benefits: none. We need to include sections only if real specific content. Thus we can have:

  About the role

  with description of CAMWS and project.

  Responsibilities

  with list of tasks: public-facing redesign, member portal functionality, conference registration, CMS, visual design, design system, WCAG compliance, content migration, staff training, documentation, post-launch support.

  Requirements

  with vendor qualifications: demonstrated experience with nonprofit/membership orgs, ideally academic/scholarly associations, familiarity with membership platforms, conference registration, PCI-compliant payment processing.

  Proposal Requirements

  maybe not in list but we can treat as "What to include" as Responsibilities? Actually it's part of submission requirements. Could be a separate section like "Submission Requirements". But we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map "Proposal Requirements" to maybe "Requirements" or "Qualifications"? But we already have Requirements for vendor qualifications. Proposal requirements are about what to include in proposal: executive summary, team bios, portfolio, technical approach, timeline, migration plan, references, itemized cost proposal. That could be considered "Responsibilities" of the vendor? Not exactly. Could be "Requirements" for submission. But we already used Requirements for vendor qualifications. Could we have both? We could combine vendor qualifications and proposal requirements under Requirements? Might be messy. Better: Use "Requirements" for vendor qualifications, and "Skills" for proposal requirements? Not ideal. Alternatively, we could create a section "Responsibilities" for what the vendor will do (project tasks). And "Requirements" for what the vendor must have (experience). And "Pay" for salary. That seems sufficient. The proposal requirements are part of the RFP instructions; maybe we can include them under "Responsibilities" as part of what the vendor must provide? But they are deliverables of the proposal, not the project. However we could treat them as part of the vendor's responsibilities to submit. Might be okay. We need to avoid filler. Let's extract substantive content: - Organization: Classical Association of the Middle West and South (CAMWS) - Type: Contract - Salary: $30,000 to $40,000 / Project-based - Four-day Week No (maybe ignore) - CAMWS description: regional learned society serving scholars, educators, and students of Greek, Latin, and classical antiquity (national membership of ~1,100) - Seeks proposals for full redesign and redevelopment of its website. - Project includes: - public-facing redesign - member portal functionality (login, renewals, directory) - conference registration with abstract submission and payment processing - modern CMS suited to a small nonprofit staff - Full scope includes: - visual design and a design system - WCAG 2.2 AA accessibility compliance - content migration with URL redirects - staff training and documentation - post-launch support - Vendors should have demonstrated experience with nonprofit/membership organizations, ideally academic or scholarly associations, and familiarity with membership platforms, conference registration, and PCI-compliant payment processing. - Proposals must include: - executive summary - team bios - portfolio of comparable work - technical approach - milestone-based timeline - migration plan - three client references - itemized cost proposal (development, hosting/licensing, ongoing support) - Proposal deadline: October 30, 2026 - Submit to: nominating@camws.org - Subject line: “CAMWS Website RFP — [Vendor Name]” - Contact: Professor Victoria Pagan We need to remove application instructions? The submission instructions are part of RFP; maybe we keep as short p. We must not include duplicated lines. Now produce HTML: We'll have

  About the role

  with paragraph describing CAMWS and the project goal.

  Responsibilities

  with
  • list of project tasks (public-facing redesign, member portal functionality, conference registration, CMS, visual design, design system, WCAG compliance, content migration, staff training, documentation, post-launch support).

    Requirements

    with
    • list of vendor qualifications (experience with nonprofit/membership orgs, ideally academic/scholarly associations; familiarity with membership platforms, conference registration, PCI-compliant payment processing).

      Pay

      with

      Salary range: $30,000 to $40,000 (project-based contract).

      We could also include a short p for deadline and submission info maybe under About? Or we could add a section "Submission Details" but not allowed headings. Could fold into About as a paragraph. We need to avoid filler like "Please see the full RFP in the PDF attached to this site." Might be considered not essential; we can drop. We also need to drop "Back to the Job Board". Let's craft. Check for any repeated lines: none. Now output only HTML fragment. Let's produce:

      About the role

      Classical Association of the Middle West and South (CAMWS) is a regional learned society serving scholars, educators, and students of Greek, Latin, and classical antiquity, with a national membership of approximately 1,100. CAMWS seeks proposals for a full redesign and redevelopment of its website.

      Responsibilities

      • Public‑facing redesign
      • Member portal functionality (login, renewals, directory)
      • Conference registration with abstract submission and payment processing
      • Modern CMS suited to a small nonprofit staff
      • Visual design and design system
      • WCAG 2.2 AA accessibility compliance
      • Content migration with URL redirects
      • Staff training and documentation
      • Post‑launch support

      Requirements

      • Demonstrated experience with nonprofit/membership organizations, ideally academic or scholarly associations
      • Familiarity with membership platforms
      • Familiarity with conference registration systems
      • Experience with PCI‑compliant payment processing

      Pay

      Salary range: $30,000 to $40,000 (project‑based contract)

      We might also add a paragraph for deadline and submission info under About or as a separate short p after Pay? Could add a

      Proposal deadline: October 30, 2026. Submit to nominating@camws.org with subject line “CAMWS Website RFP — [Vendor Name]”. Contact: Professor Victoria Pagan.

      That is substantive. We need to decide where to put it. Could add another

      after Pay or within About. Since we already have About paragraph, we could extend it with that info. But About currently describes organization and project goal; adding submission details may be okay. Let's add a second paragraph under About: "Proposal deadline: October 30, 2026. Submit to nomin