frontendbr/vagas

Analysis updated 2026-06-24

★ 15,280Audience · developerComplexity · 1/5LicenseSetup · easy

Mindmap

mindmap
  root((vagas))
    Inputs
      Job posting issue
      City and company in title
    Outputs
      Open issues list
      Twitter notifications
      Watch alerts
    Use Cases
      Find front-end jobs in Brazil
      Post a job opening
      Subscribe to new listings
    Tech Stack
      GitHub Issues
      Markdown

mindmap root((vagas)) Inputs Job posting issue City and company in title Outputs Open issues list Twitter notifications Watch alerts Use Cases Find front-end jobs in Brazil Post a job opening Subscribe to new listings Tech Stack GitHub Issues Markdown

Click or tap to explore — scroll the page freely

What do people build with it?

USE CASE 1

Browse open front-end jobs in Brazil via GitHub issue search

USE CASE 2

Post a job opening following the city, role, company title format

USE CASE 3

Fork the repo template to start a niche job board for your own community

USE CASE 4

Subscribe with Watch to get email alerts when new openings are posted

What is it built with?

GitHub IssuesMarkdown

How does it compare?

	frontendbr/vagas	tencent/weui-wxss	uuidjs/uuid
Stars	15,280	15,279	15,282
Language	—	Less	TypeScript
Setup difficulty	easy	easy	easy
Complexity	1/5	2/5	2/5
Audience	developer	developer	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Repo is a job board, not code, postings must follow a strict title format or get closed.

MIT license, free to reuse the repo template for your own job board with attribution.

In plain English

Frontendbr/vagas (vagas means "jobs" in Portuguese) is a Brazilian community job board for front-end developers, hosted entirely inside GitHub issues. Employers and recruiters post job openings by creating a new GitHub issue, and developers browse or search the open issues to find opportunities. It is maintained by the FrontendBR community and focuses exclusively on front-end development roles. The README (written in Portuguese) explains the rules for posting: the issue title must include the city in brackets, the job title, and the company name. Postings without a company name are not accepted, and companies may not post more than three openings per month. If a position is filled, the poster is asked to close the issue so candidates are not applying to stale listings. Job seekers can receive notifications of new postings by clicking "Watch" on the repository. New openings are also shared automatically on a Twitter/X account called @frontendbrvagas. The repo is part of a broader network of similar Brazilian developer job boards: there are companion repositories for back-end developers, chatbot developers, Web3, UI/UX, QA, and several specific technology stacks such as Android, iOS, PHP, Python, Vue.js, React, Flutter, and others, as well as regional boards for Portugal and Angola. The repository is licensed under MIT.

Copy-paste prompts

Prompt 1

Show me a GitHub search query that finds all open frontendbr/vagas issues for remote React jobs

Prompt 2

Help me draft a job posting issue for a Vue.js role in Sao Paulo that follows the repo rules

Prompt 3

Build me a small script that polls the vagas repo issues API and posts new ones to a Slack channel

Prompt 4

Explain how the vagas repo turns GitHub issues into a job board and what rules contributors must follow

Frequently asked questions

What is vagas?

Brazilian front-end developer job board run entirely as GitHub issues. Employers open an issue per opening, devs watch the repo for new postings.

What license does vagas use?

MIT license, free to reuse the repo template for your own job board with attribution.

How hard is vagas to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is vagas for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub frontendbr on gitmyhub

Verify against the repo before relying on details.