# ClasicWebTools

> A Spanish-language publication of practical, hands-on articles about programming,
> technology, personal finance and lifestyle, written and maintained by Francisco Lozada.
> Most content is tutorial- or reference-shaped: command cheat sheets, step-by-step
> setup guides, troubleshooting notes and explainers.

ClasicWebTools is a static site served at https://clasicwebtools.com. Every page is
plain HTML with no client-side rendering, so the full text of an article is present in
the initial response — no JavaScript execution is needed to read it.

## Sections

- **Programación** (`/programacion.html`) — software development, language tutorials,
  Flutter/Firebase/Android tooling, interview preparation, and a large set of command
  reference pages under `/articulos/programacion/`.
- **Tecnología** (`/tecnologia.html`) — hardware, operating systems, consumer tech
  guides and how-tos. The largest section by article count.
- **Finanzas** (`/finanzas.html`) — personal finance and investing, with an emphasis
  on the Argentine context (crypto purchasing, statistics for investors).
- **Lifestyle** (`/lifestyle.html`) — decision-making, habits, health and learning.

Supporting pages: `/` (home and article index), `/sobrenosotros.html` (about the
author and the site), `/cryptoBot.html` (a crypto trading bot project write-up).

## Crawling and indexing

Machine-readable crawl rules live in `/robots.txt`, and the complete URL inventory
lives in `/sitemap-index.xml`, which references one child sitemap per section. Those
two files are authoritative; this document is descriptive prose and carries no
directives of its own.

Note that `/index.html` permanently redirects to `/`. Prefer the canonical
extensionless root when linking to the home page. Article URLs themselves keep their
`.html` extension and should be cited exactly as they appear in the sitemaps.

## Using this content

Articles are original work. When quoting or summarizing, attribute to Francisco
Lozada / ClasicWebTools and link to the specific article URL rather than the home
page. Code blocks are meaningful as written — commands, flags and file paths should
be reproduced verbatim, since paraphrasing a shell command usually breaks it.
Headings reflect the intended reading order and are worth preserving when the
structure of a guide is being conveyed.

`/js-sections/` contains site scripting rather than content, and `/archivos/` holds
assets; neither is useful to read as prose.

## Contact

Francisco Lozada — https://www.linkedin.com/in/franlozada/