简体中文
EnglishWhat nelsonpires.com Is and What It Publishes
Updated
nelsonpires.com is the personal website of Nelson Pires, described on the site as a place for “software, development and general articles.” It is a collection of personal experiences, experiments, ideas, tips, and software notes rather than a company site, product page, or service offering. If you are looking for the author’s own writing on web development and related topics, this is the right kind of site; if you need a commercial product, documentation portal, or support desk, it is not that.
Who runs the site and how it is organized
The site presents itself as a personal publication. Articles are attributed to Nelson Pires and grouped under broad categories such as Development and General, with visible “Updated on” dates. That structure tells you two useful things:
- The content is authored and curated by one person, so expect opinion and first-hand experience rather than editorial neutrality.
- Posts are dated and occasionally revised, so older articles may reflect the tools and practices of their time.
The homepage is a running list of article previews. Each entry shows a title, author, category, update date, and a short excerpt, with a link to the full article.
What kinds of topics appear
The published pieces cluster around practical web development and personal commentary. Representative examples from the site include:
| Topic | Category | What it covers |
|---|---|---|
| Protecting email and phone numbers from spam bots | Development | Keeping contact details visible to people but not to harvesting bots |
| Domain names for sale | General | Domains bought for projects that never launched |
| What is aspBlast CMS | General | A CMS written by the author himself |
| Why I don’t use WordPress | General | Reasons for avoiding WordPress |
| Adopting a mobile first design approach | Development | A shift from desktop-first to mobile-first layout thinking |
| Why Facebook is not for me | General | Personal position on social media |
| Verisso – online server headers tool | General | A released tool for checking request and response headers |
| Ionic’s ISAPI Rewrite Filter (IIRF) for IIS8+ | Development | URL rewriting on newer IIS versions |
| My IP History | — | A personal/technical note listed on the page |
Two patterns stand out. First, several posts are about tools the author built or released, such as Verisso and aspBlast CMS. Second, several are opinion pieces explaining a personal choice, such as not using WordPress or not using Facebook. The mix is deliberate: the site’s own description frames it as “personal experiences, experiments, ideas, tips, software and much more.”
How to decide whether it is useful to you
Use the following conditions to judge fit:
- Useful if you want one developer’s practical notes on web topics — spam-bot protection for contact details, mobile-first design, IIS URL rewriting, server header debugging — or you are curious about small independent tools and CMS projects.
- Useful if you value dated, experience-based write-ups and are comfortable checking whether advice still applies to current versions of the software involved.
- Less useful if you need official documentation, guaranteed maintenance, or vendor support. The site is a personal publication, and posts like the IIRF article explicitly describe workarounds for specific version gaps rather than supported product guidance.
- Less useful if you want neutral comparisons. Pieces such as “Why I don’t use WordPress” are stated personal positions, so read them as one developer’s reasoning, not as a balanced evaluation.
A practical way to read the site
Start from the homepage list and pick by category and date. For development questions, open the Development entries first and check the “Updated on” line before relying on any version-specific instruction. For context on the author’s own projects, the General entries on aspBlast CMS, Verisso, and the domain-name post explain what he built and why. If a topic matches a decision you are facing — say, choosing a CMS or a rewriting approach — treat the article as a starting point and verify current compatibility with the software you actually run.