Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark kumascript code blocks js -> plain #18493

Merged
merged 1 commit into from
Jul 19, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -137,6 +137,6 @@ Further information about tag-based processing is available [in the APIRef sourc
Once you've added an entry for your API into `GroupData.json`, submitted it as a pull request and had the change accepted into the main repo, you can include it in your API reference pages using the [`APIRef`](https://github.com/mdn/yari/blob/main/kumascript/macros/APIRef.ejs) macro, which takes the name you used for your API in GroupData as a parameter.
As an example, the [WebVR API](/en-US/docs/Web/API/WebVR_API)'s sidebar is included in its pages with the following:

```js
```plain
\{{APIRef("WebVR API")}}
```
4 changes: 2 additions & 2 deletions files/en-us/mdn/structures/live_samples/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ In many cases, you may be able to add the `EmbedLiveSample` or `LiveSampleLink`

#### EmbedLiveSample macro

```js
```plain
\{{EmbedLiveSample(block_ID, width, height, screenshot_URL, page_slug)}}
```

Expand All @@ -64,7 +64,7 @@ In many cases, you may be able to add the `EmbedLiveSample` or `LiveSampleLink`

#### LiveSampleLink macro

```js
```plain
\{{LiveSampleLink(block_ID, link_text)}}
```

Expand Down
2 changes: 1 addition & 1 deletion files/en-us/mdn/structures/macros/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Macros on MDN are implemented using server-executed [JavaScript](/en-US/docs/Web

To use a macro, you enclose the call to the macro in a pair of double-braces along with its parameters, if any:

```js
```plain
\{{macroname(parameter-list)}}
```

Expand Down
6 changes: 3 additions & 3 deletions files/en-us/mdn/tools/kumascript/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ A script in KumaScript is a _template_, and each template is a file in [the macr

Invoking a template is done with a _macro_, which can be used anywhere in any wiki content. Invoking the above template would look like this (provided it was saved in the macros directory with a filename of `hello.ejs`):

```js
```plain
\{{hello(3)}}
```

Expand All @@ -58,7 +58,7 @@ Hello #2

Macro syntax takes the following general form:

```js
```plain
\{{templateName("arg0", "arg1", /* …, */ "argN")}}
```

Expand All @@ -73,7 +73,7 @@ Macro syntax follows these rules:

As a semi-experimental feature (not guaranteed to work), you can supply a JSON object for the first and only parameter, like so:

```js
```plain
\{{templateName({ "Alpha": "one", "Beta": ["a", "b", "c"], "Foo": "https:\/\/mozilla.org\/" })}}
```

Expand Down