.env - Convention for both (FastAPI and Next.js)
    .env:          → Gitignored, so not committed to git. 
                   → It's the file your app actually reads at runtime. List real secrets: DB credentials, API keys, etc.
                   → Each developer needs to create a .env based on .env.example                
    
    .env.example:  → Committed to git
                   → It's never read by the running app at all. It's purely documentation. Lists variable names with placeholder/dummy values, so teammates know what to create locally without ever exposing real secrets.




FastAPI:
    services/   Typically implies business logic classes that are called by routes (e.g. a UserService, ArticleService). 
    scripts/    Contains scripts that run independently, not service classes.
                If functions in scripts/ grow into proper app-integrated code later, it should be renamed as services/. For example, if pedir_resumen.py evolves into a proper module that gets called by your API routes (e.g. a route triggers an AI summarization job), then services/ would make sense. But right now it's a standalone script, so scripts/ is more accurate.
    static/     files served directly to the browser without processing: Images, CSS, JavaScript, fonts.  




News websites:
* https://edition.cnn.com
* https://www.reuters.com
* https://www.dw.com
* https://www.404media.co


Nice websites:
* https://www.apple.com/ipad-air/
* https://lido.fi/
* https://app.uniswap.org/?utm_source=chatgpt.com
* https://multiversx.com/
* https://www.soniclabs.com/
* https://kava.io/
* https://www.chiliz.com/
* https://pancakeswap.finance/home
* https://www.pyth.network/
* https://www.movementnetwork.xyz/
* https://www.bandprotocol.com/