If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: angular.dev/style-guide - Style Guide  Angular.

site address: angular.dev/style-guide redirected to: angular.dev/style-guide

site title: Style Guide Angular

Our opinion (on Wednesday 18 November 2026 17:35:15 UTC):

GREEN status (no comments) - no comments
After content analysis of this website we propose the following hashtags:



Meta tags:
description=The web development framework for building modern apps.;
author=;
keywords=Angular framework, TypeScript, web development, hydration, Signals, standalone components, accessibility, performance;

Headings (most frequently used words):

the, and, in, file, use, for, component, on, prefer, same, name, angular, style, naming, project, injection, components, directives, community, names, with, typescript, template, application, directory, named, src, your, group, by, over, choosing, selectors, directive, members, properties, methods, keep, class, that, event, lifecycle, coding, guide, this, page, introduction, structure, dependency, social, media, resources, translations, when, doubt, consistency, separate, words, hyphens, tests, spec, at, end, match, to, identifier, within, styles, all, code, goes, bootstrap, main, ts, directly, inside, closely, related, files, together, organize, feature, areas, one, concept, per, inject, function, constructor, parameter, specific, before, focused, presentation, avoid, overly, complex, logic, templates, protected, are, only, used, readonly, shouldn, change, ngclass, ngstyle, handlers, what, they, do, not, triggering, simple, hook, interfaces,

Text of the page (most frequently used words):
the (80), and (44), #angular (33), for (33), file (32), code (25), that (24), this (23), component (22), class (21), style (20), name (15), with (15), your (14), #prefer (13), use (12), event (12), div (12), components (12), should (12), files (12), named (11), typescript (11), avoid (11), template (11), one (11), when (10), more (10), guide (10), directives (10), properties (10), directory (10), userprofile (9), these (9), you (9), example (9), application (9), names (8), not (8), readonly (8), same (8), user (8), profile (8), lifecycle (7), methods (7), like (7), input (7), directive (7), into (7), google (6), from (6), are (6), logic (6), inside (6), specific (6), color (6), output (6), inject (6), complex (5), what (5), single (5), details (5), can (5), using (5), makes (5), naming (5), than (5), new (5), injection (5), dependencies (5), src (5), project (5), tests (5), within (5), practices (5), ngoninit (4), export (4), they (4), based (4), easier (4), button (4), ngstyle (4), ngclass (4), html (4), templates (4), read (4), over (4), queries (4), but (4), members (4), group (4), together (4), directories (4), common (4), live (4), different (4), has (4), coding (4), under (3), v22 (3), developer (3), oninit (3), hook (3), all (3), creating (3), describe (3), have (3), those (3), key (3), especially (3), does (3), bindings (3), additional (3), straightforward (3), textcolor (3), background (3), backgroundcolor (3), admin (3), isadmin (3), dense (3), density (3), high (3), set (3), fullname (3), protected (3), public (3), dependency (3), best (3), typically (3), expressions (3), generally (3), other (3), separate (3), classes (3), injected (3), build (3), might (3), choosing (3), selectors (3), function (3), constructor (3), service (3), contains (3), concept (3), unit (3), main (3), between (3), styles (3), words (3), css (3), spec (3), consistency (3), updated (3), licensed (2), built (2), community (2), youtube (2), interface (2), ensures (2), method (2), correctly (2), import (2), interfaces (2), logger (2), info (2), putting (2), long (2), hooks (2), instead (2), well (2), then (2), meaningful (2), describes (2), keep (2), handlekeydown (2), handler (2), back (2), keydown (2), control (2), events (2), save (2), click (2), handlers (2), triggering (2), performance (2), syntax (2), closely (2), paymentmethod (2), usersaved (2), apis (2), model (2), initialized (2), includes (2), access (2), lastname (2), firstname (2), computed (2), part (2), api (2), used (2), define (2), hard (2), refactor (2), relatively (2), directly (2), overly (2), page (2), rules (2), top (2), declaration (2), before (2), attribute (2), selector (2), moviereel (2), see (2), offers (2), type (2), many (2), parameter (2), doubt (2), per (2), consider (2), subdirectories (2), film (2), movie (2), organize (2), structure (2), feature (2), test (2), unrelated (2), consist (2), related (2), start (2), primary (2), bootstrap (2), consistent (2), projects (2), creates (2), share (2), identifier (2), theme (2), end (2), hyphens (2), conventions (2), recommendations (2), ecosystem (2), introduction (2), workers (2), animations (2), release (2), cli (2), server (2), setup (2), docs (2), menu (2), super, powered, 2010, 2026, documentation, sha, ff0068a, mit, license, 正體中文版, 简体中文版, 日本語版, 한국어, русский, türkçe, oʻzbekcha, français, español, azərbaycanca, translations, roadmap, press, kit, resources, experts, devlibrary, report, issues, conduct, contribute, stack, overflow, github, discord, bluesky, formerly, twitter, blog, social, media, implements, core, provides, each, adding, ensure, implement, rest, would, unrolled, monitorerrors, setmode, runbackgroundtask, startlogging, contain, run, meaning, doesn, doing, call, simple, activateitalic, else, activatebold, ctrlkey, keyboardevent, richtext, sometimes, handling, making, impractical, declare, cases, fine, fall, delegate, behaviors, showsuggestions, space, commitnotes, enter, textarea, keyboard, modifiers, tell, reading, handleclick, saveuserdata, action, perform, rather, refer, additionally, incur, cost, compared, binding, both, aligns, standard, attributes, understand, developers, familiar, basic, querylist, paymentmethods, viewchildren, void, eventemitter, decorator, query, advice, applies, username, userid, mark, modifier, value, overwritten, shouldn, change, intrinsically, accessible, via, any, meant, only, there, fast, rule, determines, constitutes, judgement, gets, too, though, designed, accommodate, take, advantage, capture, javascript, relate, shown, sense, its, own, decoupled, refactoring, factor, form, validation, data, transformations, functions, focused, presentation, practice, find, near, inputs, outputs, camelcase, adds, tooltip, element, mrtooltip, prefix, existing, automatic, tool, targeting, es2022, separating, field, initialization, fields, usedefineforclassfields, better, inference, syntactically, add, comments, readable, injects, injecting, parameters, works, way, several, advantages, approach, leads, smaller, focusing, source, specifically, usually, means, however, okay, small, tie, becomes, navigate, number, grows, splitting, further, sub, lives, services, purchase, confirmation, payment, reserve, tickets, calendar, show, times, reel, features, themes, theater, site, look, areas, collecting, optionally, always, represents, entry, point, keeps, root, clear, separation, such, configuration, scripts, outside, goes, append, subscription, settings, extensions, namable, choose, fit, area, breaking, generic, utils, helpers, contents, reflect, containing, match, whenever, encounter, situation, which, contradict, particular, prioritize, maintaining, mixing, confusion, diverging, cover, general, check, out, covers, range, required, work, establish, promote, across, move, arrow_upward_alt, material, cdk, player, pay, maps, fire, tailwind, custom, pipeline, web, pwas, rxjs, legacy, ngmodules, extended, v21, keeping, date, unhandled, errors, accessibility, security, language, devtools, libraries, tools, webmcp, design, patterns, tutor, mcp, agent, skills, llm, prompts, ide, get, started, drag, drop, internationalization, aria, testing, side, hybrid, rendering, http, client, forms, routing, signals, depth, guides, essentials, installation, more_horiz, reference, playground, tutorials, close, skip, content,


Text of the page (random words):
style guide angular skip to main content menu close v22 k docs tutorials playground reference more_horiz menu docs introduction what is angular installation essentials start coding in depth guides signals updated components templates directives dependency injection updated routing forms updated http client server side hybrid rendering testing angular aria new internationalization animations drag and drop build with ai get started llm prompts and ai ide setup agent skills new angular cli mcp server setup angular ai tutor design patterns webmcp new developer tools angular cli libraries devtools language service best practices style guide security accessibility unhandled errors in angular performance keeping up to date developer events angular v22 release new angular v21 release extended ecosystem ngmodules legacy animations using rxjs with angular service workers pwas web workers custom build pipeline tailwind angular fire google maps google pay youtube player angular cdk angular material best practices angular coding style guide on this page arrow_upward_alt back to the top introduction this guide covers a range of style conventions for angular application code these recommendations are not required for angular to work but instead establish a set of coding practices that promote consistency across the angular ecosystem a consistent set of practices makes it easier to share code and move between projects this guide does not cover typescript or general coding practices unrelated to angular for typescript check out google s typescript style guide when in doubt prefer consistency whenever you encounter a situation in which these rules contradict the style of a particular file prioritize maintaining consistency within a file mixing different style conventions in a single file creates more confusion than diverging from the recommendations in this guide naming separate words in file names with hyphens separate words within a file name with hyphens for example a component named userprofile has a file name user profile ts use the same name for a file s tests with spec at the end for unit tests end file names with spec ts for example the unit test file for the userprofile component has the file name user profile spec ts match file names to the typescript identifier within file names should generally describe the contents of the code in the file when the file contains a typescript class the file name should reflect that class name for example a file containing a component named userprofile has the name user profile ts if the file contains more than one primary namable identifier choose a name that describes the common theme to the code within if the code in a file does not fit within a common theme or feature area consider breaking the code up into different files avoid overly generic file names like helpers ts utils ts or common ts use the same file name for a component s typescript template and styles components typically consist of one typescript file one template file and one style file these files should share the same name with different file extensions for example a userprofile component can have the files user profile ts user profile html and user profile css if a component has more than one style file append the name with additional words that describe the styles specific to that file for example userprofile might have style files user profile settings css and user profile subscription css project structure all the application s code goes in a directory named src all of your angular ui code typescript html and styles should live inside a directory named src code that s not related to ui such as configuration files or scripts should live outside the src directory this keeps the root application directory consistent between different angular projects and creates a clear separation between ui code and other code in your project bootstrap your application in a file named main ts directly inside src the code to start up or bootstrap an angular application should always live in a file named main ts this represents the primary entry point to the application group closely related files together in the same directory angular components consist of a typescript file and optionally a template and one or more style files you should group these together in the same directory unit tests should live in the same directory as the code under test avoid collecting unrelated tests into a single tests directory organize your project by feature areas organize your project into subdirectories based on the features of your application or common themes to the code in those directories for example the project structure for a movie theater site moviereel might look like this src movie reel show times film calendar film details reserve tickets payment info purchase confirmation avoid creating subdirectories based on the type of code that lives in those directories for example avoid creating directories like components directives and services avoid putting so many files into one directory that it becomes hard to read or navigate as the number of files in a directory grows consider splitting further into additional sub directories one concept per file prefer focusing source files on a single concept for angular classes specifically this usually means one component directive or service per file however it s okay if a file contains more than one component or directive if your classes are relatively small and they tie together as part of a single concept when in doubt go with the approach that leads to smaller files dependency injection prefer the inject function over constructor parameter injection prefer using the inject function over injecting constructor parameters the inject function works the same way as constructor parameter injection but offers several style advantages inject is generally more readable especially when a class injects many dependencies it s more syntactically straightforward to add comments to injected dependencies inject offers better type inference when targeting es2022 with usedefineforclassfields you can avoid separating field declaration and initialization when fields read on injected dependencies you can refactor existing code to inject with an automatic tool components and directives choosing component selectors see the components guide for details on choosing component selectors naming component and directive members see the components guide for details on naming input properties and naming output properties choosing directive selectors directives should use the same application specific prefix as your components when using an attribute selector for a directive use a camelcase attribute name for example if your application is named moviereel and you build a directive that adds a tooltip to an element you might use the selector mrtooltip group angular specific properties before methods components and directives should group angular specific properties together typically near the top of the class declaration this includes injected dependencies inputs outputs and queries define these and other properties before the class s methods this practice makes it easier to find the class s template apis and dependencies keep components and directives focused on presentation code inside your components and directives should generally relate to the ui shown on the page for code that makes sense on its own decoupled from the ui prefer refactoring to other files for example you can factor form validation rules or data transformations into separate functions or classes avoid overly complex logic in templates angular templates are designed to accommodate javascript like expressions you should take advantage of these expressions to capture relatively straightforward logic directly in template expressions when the code in a template gets too complex though refactor logic into the typescript code typically with a computed there s no one hard and fast rule that determines what constitutes complex use your best judgement use protected on class members that are only used by a component s template a component class s public members intrinsically define a public api that s accessible via dependency injection and queries prefer protected access for any members that are meant to be read from the component s template component template p fullname p export class userprofile firstname input lastname input fullname is not part of the component s public api but is used in the template protected fullname computed this firstname this lastname use readonly for properties that shouldn t change mark component and directive properties initialized by angular as readonly this includes properties initialized by input model output and queries the readonly access modifier ensures that the value set by angular is not overwritten component export class userprofile readonly userid input readonly usersaved output readonly username model for components and directives that use the decorator based input output and query apis this advice applies to output properties and queries but not input properties component export class userprofile output readonly usersaved new eventemitter void viewchildren paymentmethod readonly paymentmethods querylist paymentmethod prefer class and style over ngclass and ngstyle prefer class and style bindings over using the ngclass and ngstyle directives prefer div class admin isadmin class dense density high div style color textcolor style background color backgroundcolor or div class admin isadmin dense density high div style color textcolor background color backgroundcolor div div div div avoid div ngclass admin isadmin dense density high div ngstyle color textcolor background color backgroundcolor div div both class and style bindings use a more straightforward syntax that aligns closely with standard html attributes this makes your templates easier to read and understand especially for developers familiar with basic html additionally the ngclass and ngstyle directives incur an additional performance cost compared to the built in class and style binding syntax for more details refer to the bindings guide name event handlers for what they do not for the triggering event prefer naming event handlers for the action they perform rather than for the triggering event prefer button click saveuserdata save button avoid button click handleclick save button using meaningful names like this makes it easier to tell what an event does from reading the template for keyboard events you can use angular s key event modifiers with specific handler names textarea keydown control enter commitnotes keydown control space showsuggestions sometimes event handling logic is especially long or complex making it impractical to declare a single well named handler in these cases it s fine to fall back to a name like handlekeydown and then delegate to more specific behaviors based on the event details component class richtext handlekeydown event keyboardevent if event ctrlkey if event key b this activatebold else if event key i this activateitalic keep lifecycle methods simple avoid putting long or complex logic inside lifecycle hooks like ngoninit instead prefer creating well named methods to contain that logic and then call those methods in your lifecycle hooks lifecycle hook names describe when they run meaning that the code inside doesn t have a meaningful name that describes what the code inside is doing prefer ngoninit this startlogging this runbackgroundtask avoid ngoninit this logger setmode info this logger monitorerrors and all the rest of the code that would be unrolled from these methods use lifecycle hook interfaces angular provides a typescript interface for each lifecycle method when adding a lifecycle hook to your class import and implement these interfaces to ensure that the methods are named correctly import component oninit from angular core component export class userprofile implements oninit the oninit interface ensures this method is named correctly ngoninit social media blog x formerly twitter bluesky youtube discord github stack overflow community contribute code of conduct report issues google s devlibrary angular google developer experts resources press kit roadmap community translations azərbaycanca español français oʻzbekcha türkçe русский 한국어 日本語版 简体中文版 正體中文版 super powered by google 2010 2026 code licensed under an mit style license documentation licensed under cc by 4 0 built by angular at v22 2 6 sha ff0068a
Thumbnail images (randomly selected): * Images may be subject to copyright.GREEN status (no comments)

    No Images


    Verified site has: 45 subpage(s). Do you want to verify them? Verify pages:

    1-5 6-10 11-15 16-20 21-25 26-30 31-35 36-40 41-45


    The site also has references to the 2 subdomain(s)

      material.angular.dev  Verify   blog.angular.dev  Verify


    The site also has 1 references to other resources (not html/xhtml )

     angular.dev/ai  Verify


    Top 50 hastags from of all verified websites.

    Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

    Header

    HTTP/1.1 301 Moved Permanently
    Connection close
    Content-Length 0
    Server Varnish
    Retry-After 0
    Location htt????/angular.dev/style-guide
    Accept-Ranges bytes
    Date Wed, 18 Nov 2026 17:35:15 GMT
    X-Served-By cache-rtm-ehrd2290029-RTM
    X-Cache HIT
    X-Cache-Hits 0
    X-Timer S1795023315.389901,VS0,VE0
    alt-svc h3= :443 ;ma=86400,h3-29= :443 ;ma=86400,h3-27= :443 ;ma=86400
    HTTP/2 200
    cache-control max-age=3600
    content-encoding gzip
    content-type text/html; charset=utf-8
    cross-origin-embedder-policy credentialless
    cross-origin-opener-policy same-origin
    etag 83e3d9d1fb7d58970b5284d98b6721312af27011f4395f22f6ca43c8ca9fcbc4
    last-modified Tue, 17 Nov 2026 19:28:53 GMT
    strict-transport-security max-age=31556926
    accept-ranges bytes
    date Wed, 18 Nov 2026 17:35:15 GMT
    x-served-by cache-lcy-egml8630028-LCY
    x-cache HIT
    x-cache-hits 0
    x-timer S1795023315.423404,VS0,VE2
    vary x-fh-requested-host, accept-encoding
    alt-svc h3= :443 ;ma=86400,h3-29= :443 ;ma=86400,h3-27= :443 ;ma=86400
    content-length 32617

    Meta Tags

    title="Style Guide Angular"
    charset="utf-8"
    name="viewport" content="width=device-width, initial-scale=1"
    name="description" content="The web development framework for building modern apps."
    name="author" content="Angular Team"
    name="keywords" content="Angular framework, TypeScript, web development, hydration, Signals, standalone components, accessibility, performance"
    name="apple-mobile-web-app-title" content="Angular"
    name="application-name" content="Angular"
    name="theme-color" content="#ffffff"
    property="og:type" content="website"
    property="og:url" content="htt????/angular.dev/"
    property="og:title" content="Style Guide • Angular"
    property="og:description" content="The web development framework for building modern apps."
    property="og:image" content="htt????/angular.dev/assets/images/ng-image.jpg"
    name="twitter:site" content="@Angular"
    name="twitter:creator" content="@Angular"
    property="twitter:card" content="summary_large_image"
    property="twitter:url" content="htt????/angular.dev/"
    property="twitter:title" content="Style Guide • Angular"
    property="twitter:description" content="The web development framework for building modern apps."
    property="twitter:image" content="htt????/angular.dev/assets/images/ng-image.jpg"

    Load Info

    page size32617
    load time (s)0.125906
    redirect count1
    speed download260936
    server IP 199.36.158.100
    * all occurrences of the string "http://" have been changed to "htt???/"