FPGA PA

Contribute

Why contribute

The association is what its volunteers make it. Every page on this site, every feature in CovertEDA, and every published resource started as a pull request from someone who saw a gap and filled it. No contributor is paid; all contributions are credited.

Ways to contribute

Improve this site

Fork the website repository, edit HTML, CSS, or markdown, and open a pull request. Typo fixes are welcome. New resource entries are welcome. Design improvements are welcome if they respect the constraints in BUILD_PLAN.md — no JavaScript frameworks, no third-party fonts, no decorative images that do not add information. All pull requests are reviewed by the site maintainer, who is the sole required approver.

Contribute to CovertEDA

The CovertEDA codebase is at github.com/fpga-professional-association/CovertEDA. Areas that need work: vendor backend integration (Vivado, Quartus, Radiant, Libero), report parsers, constraint validation, and platform packaging. Rust experience is helpful but not required for documentation and integration testing contributions.

Write a resource

Career notes, technical guides, and well-structured war stories are accepted as Markdown pull requests to the resources repository. State the problem, walk through the situation, and end with the takeaway. No marketing language. Citations for any non-trivial claim.

Volunteer for a working group

Active working groups: salary survey, interview preparation, regional chapter formation. Email contact@fpgapa.org with a short note about the area you want to work on and what time you can commit.

Start a regional chapter

Regional chapters meet locally — quarterly is a reasonable cadence — to share experience, run mock interviews, and review each other’s work. Email the contact address with the metro area you would coordinate.

Pull request workflow for this site

  1. Fork the website repository.
  2. Create a branch (git checkout -b your-change).
  3. Edit the files. Preview locally by opening index.html in your browser.
  4. Open a pull request with a clear title and one-sentence description.
  5. Continuous integration runs HTML validation, accessibility checks, and link checking automatically.
  6. The maintainer reviews. Most reviews land within seven days.
  7. On approval, the change merges and deploys automatically to the live site.

What we won’t merge

  • Marketing language: transform, revolutionary, best-in-class, industry-leading, cutting-edge, next-generation.
  • Vendor-promotional content that breaks vendor neutrality.
  • Tracking scripts or analytics that require cookie consent.
  • JavaScript frameworks, CSS frameworks, build steps, third-party fonts or CDNs.
  • Numeric claims without a citation.
  • Decorative images that do not add information.
  • New top-level pages without prior discussion.

The association is volunteer-run. No contributor is paid. All contributions are credited.