[Project] AutoCidade - Brazilian city guide built with Go

[Andrey Andrade]

Hi gophers!

I'd like to share a project I built entirely in Go: AutoCidade (https://autocidade.com).

It's a Brazilian city guide serving data for:
- 20 largest cities in Brazil
- Neighborhoods organized by region
- Area codes (DDDs) for all states
- Local businesses by category

Tech stack:
- Go 1.24
- LevelDB for storage
- Native html/template
- No external frameworks

I also released the data as open JSON files on GitHub:
https://github.com/andradeandrey/autocidade-dados-abertos

Available datasets:
- cities.json - 20 cities with population, area codes
- states.json - 27 Brazilian states
- ddds.json - 67 area codes mapped to cities
- neighborhoods/*.json - Neighborhoods by city and region

Quick usage example:

```go
type City struct {
    Slug       string `json:"slug"`
    Name       string `json:"nome"`
    State      string `json:"estado"`
    DDD        string `json:"ddd"`
    Population int    `json:"populacao_estimada"`
}

resp, _ := http.Get("https://raw.githubusercontent.com/.../dados/cidades.json")
var data struct { Cities []City `json:"cidades"` }
json.NewDecoder(resp.Body).Decode(&data)
```

Feedback welcome! PRs are open if anyone wants to add more cities or improve the data.

Cheers,
Andrey

--
AutoCidade: https://autocidade.com
GitHub: https://github.com/andradeandrey/autocidade-dados-abertos

[Wathika Wanini]

The UI/UX looks smooth overall.

I noticed a couple of issues:

• This page seems to be missing something in the UI (the red button on the top right):
  https://autocidade.com/painel

• This page returns a 405 Method Not Allowed error:
  https://autocidade.com/manutencao
  Screenshot: https://imgur.com/a/l6yvrXJ

Also, as a possible improvement, the chatbot could be scoped more like a RAG system, so it only answers based on information from your site.

[Andrey Andrade]

Thank you so much for taking the time to review and for the detailed feedback!

You're absolutely right about both issues — I'll look into the missing element on the dashboard page and fix the 405 error on the maintenance page right away.

Regarding the chatbot suggestion, I completely agree. Scoping it as a RAG system to answer only based on site information would make it much more useful and focused. That's definitely something I want to implement.

Really appreciate you pointing these out!