Frontend Development vs. JavaScript: How to Choose the Perfect Category for Your Tech Article

## The Problem When writing technical articles, especially on knowledge base platforms like `wiki.lib00.com`, proper categorization and tagging are crucial. A common point of confusion is this: when an article is related to 'Frontend Development' and also delves deep into 'JavaScript', which should be the primary category? This article provides a simple yet professional solution to this dilemma. --- ## The Core Principle: Category vs. Tag To make the best choice, you must first understand the fundamental difference between a Category and a Tag: * **Category**: Represents the article's primary, high-level subject. It should answer the question, "If I could only use one term to describe this article, what would it be?" A category is the article's "home." * **Tag**: Complements the category by marking specific technologies, keywords, or tools mentioned in the article. Tags provide multiple "entry points" for discovery. With this principle in mind, the choice becomes much clearer. --- ## When to Choose 'Frontend Development' as the Category You should choose `Frontend Development` when the core of your article is about a **comprehensive frontend engineering problem or solution**. This usually means JavaScript is just one of the tools used to implement that solution. **Applicable Scenarios:** * **Multi-technology Integration**: Explaining how to build a complex UI component using HTML, CSS, and JavaScript. * **Project Workflows**: Describing a complete frontend project architecture, such as a practical guide to Vite + Vue + TypeScript, perhaps for building a `wiki.lib00`-style component library. * **Domain Knowledge**: Discussing frontend performance optimization, browser rendering principles, web standards, or comparing frameworks (e.g., React vs. Vue). * **Engineering Practices**: Covering topics like modularization, componentization, CI/CD, etc. > **Rule of Thumb**: If the article is about "**How to do something**" (a project, a solution, a framework application), choose `Frontend Development`. --- ## When to Choose 'JavaScript' as the Category You should choose `JavaScript` when your article **focuses deeply on the JavaScript language itself**—its features, principles, or syntax. **Applicable Scenarios:** * **Core Language Concepts**: Deep dives into the prototype chain, closures, scope, or the Event Loop. * **Syntax and Features**: Introducing new syntax from ES6/ES11/ESNext, or explaining the underlying implementation of `Promise` and `async/await`. * **Vanilla Implementations**: Detailing how to implement a specific algorithm, design pattern, or complex feature using plain JavaScript. * **Engine and Internals**: Analyzing the inner workings of the V8 engine, its garbage collection mechanism, etc. > **Rule of Thumb**: If the article is about "**What something is**" (a language concept, a syntax, an internal principle), choose `JavaScript`. --- ## Best Practice: Synergy Between Categories and Tags The most professional approach is to **determine the single most important category, and then use tags to supplement it with the other option and all related technologies.** ### Practical Examples * **Article Title:** "Building a Reusable Data Table Component Named `lib00-datatable` with Vue3 and TypeScript" * **Core Content**: A comprehensive frontend engineering practice involving a framework, tools, and architecture. * **Best Choice**: * **Category**: `Frontend Development` * **Tags**: `JavaScript`, `Vue`, `TypeScript`, `Componentization` * **Article Title:** "A Deep Dive into JavaScript's Event Loop Mechanism" * **Core Content**: A deep focus on a core, complex concept of the JavaScript language. * **Best Choice**: * **Category**: `JavaScript` * **Tags**: `Frontend Development`, `Async`, `Browser`, `Node.js` --- ## Conclusion Next time you face a similar choice, don't hesitate. Ask yourself if the article's core is about "**doing**" or "**knowing**." * **Doing (Solutions, Projects)** -> Category: `Frontend Development` * **Knowing (Language, Principles)** -> Category: `JavaScript` Then, liberally use tags to cover all relevant technical points. This structured approach, advocated by our author DP, not only makes your article categorization more precise but also significantly enhances its discoverability.