Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
angular/aio/content/marketing/resources-contributing.md
Joe Martin (Crowdstaffing) 42289f25c6 docs: improve markdown (#45325) 
The purpose of the changes is to clean all markdown to match a single pedantic style.

*   To ensure all changes in style are properly separated.
*   To ensure all styled content aligns to nearest 4-character-tab.
*   To ensure all code blocks use the Angular `<code-example>` or `<code-tab>` elements.
*   To ensure all markdown exists outside of html tags.
*   To ensure all images use the Angular style for `<img>` elements.
*   To ensure that all smart punctuation is replaced or removed.

    ```text
    ’, ’, “, ”, –, —, …
    ```

*   To ensure all content does not conflict with the following reserved characters.

    ```text
    @, $, *, &, #, |, <, >,
    ```

*   To ensure all content displays using html entities.

The following changes were made to files in the following directory.

```text
aio/content
```

The target files were markdown files.
The list of excluded files:

```text
.browserslistrc, .css, .conf, .editorconfig, .gitignore, .html, .js, .json, .sh, .svg, .ts, .txt, .xlf,
```

PR Close #45325
2022-04-08 19:36:30 +00:00

990 B
Raw Blame History

Contributing to resources.json

About this list

We maintain a small list of some of the top Angular resources from across the community, stored in resources.json. This list is not intended to be comprehensive, but to act as a starting point to connect Angular developers to the rest of the community.

How do I get listed?

While we can't accept all contributions, qualifying contributions can be submitted via a PR adding yourself to the resources.json file. All contributions should be in the appropriate section and must meet the following criteria:

  1. Your contribution must be valid, and contain a link to a page talking specifically about using Angular
  2. Your contribution should have a clear and concise title and description
  3. Your resource should follow our brand guidelines see our [Presskit](presskit)
  4. Your resource should have significant benefit to Angular developers
  5. Your resource should already have traction and praise from Angular developers