Meta tags:
description=Custom syntaxes are PostCSS syntaxes written by the community to support other styling languages, e.g. SCSS, and containers, e.g. HTML, using the customSyntax option.;

Headings (most frequently used words):

writing, custom, syntaxes,

Text of the page (most frequently used words):
custom (14), the (9), postcss (8), writing (7), #syntax (6), guide (6), #syntaxes (6), config (5), foo (5), for (5), stylelint (4), root (4), rules (3), standard (3), default (3), your (3), from (3), creating (3), stringify (3), write (3), formatters (2), plugins (2), extends (2), yourcustomsyntax (2), customsyntax (2), overrides (2), export (2), import (2), example (2), you (2), called (2), file (2), recommend (2), shared (2), with (2), content (2), parse (2), stringifier (2), builder (2), node (2), use (2), function (2), other (2), one (2), awesome (2), home (2), next, previous, edit, this, page, recommended, requiring, until, longer, circulation, null, rule, unknown, files, language, which, uses, extension, following, all, within, supported, extensions, turns, off, any, incompatible, built, bundles, after, publishing, that, just, return, adding, nodes, const, opts, css, familiarize, yourself, can, existing, reference, how, are, written, community, support, styling, languages, scss, and, containers, html, using, option, changelog, about, maintainer, contributor, migration, developer, user, search, github, demo, skip, main,

Text of the page (random words):
writing custom syntaxes stylelint skip to main content home rules demo github search home user guide developer guide writing plugins writing custom syntaxes writing custom formatters migration guide contributor guide maintainer guide about changelog awesome writing custom syntaxes custom syntaxes are postcss syntaxes written by the community to support other styling languages e g scss and containers e g html using the customsyntax option to write one familiarize yourself with postcss s how to write custom syntax guide you can use one of the existing custom syntaxes from awesome stylelint for reference for example import postcss from postcss function parse css opts const root postcss root adding other nodes to root return root function stringify node builder just use the default stringifier postcss stringify node builder or write custom stringifier export default parse stringify after publishing your custom syntax we recommend creating a shared config that extends the standard config bundles your custom syntax turns off any incompatible built in rules all within an overrides for the supported file extensions for example if you re creating a custom syntax for a language called foo which uses the file extension foo we recommend creating a shared config called stylelint config standard foo with the following content import yourcustomsyntax from postcss your custom syntax export default overrides files foo foo customsyntax yourcustomsyntax extends stylelint config standard rules at rule no unknown null we recommended requiring the custom syntax until postcss v7 is no longer in circulation edit this page previous writing plugins next writing custom formatters