Yaml: Difference between revisions

Line 3:

See [[wp:YAML]]

I learned it when it was first introduced in 2001 so at that time it was known as "Yet Another Markup Language", however the acronym later became a recursive backcronym standing for "YAML Ain't Markup Language".

I learned it when it was first introduced in 2001 so at that time it was known as "Yet Another Markup Language", however the acronym later became a recursive backcronym standing for "'''YAML Ain't Markup Language'''". So, what is it then? Well, it's a data serialization format. It is a superset of JSON, which means that any valid JSON is valid YAML.

~~Used~~ everywhere, such as [[Ansible]]~~, so refer~~ to https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html ~~as well~~

YAML is used everywhere, such as the [[Ansible]] project. Refer to [https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html Ansible reference appendices YAML Syntax]. If you want to use Ansible, learning YAML first will help you tremendously.

== ~~YAML Tips~~ ==

==Resources==

https://www.redhat.com/sysadmin/yaml-tips

[https://www.redhat.com/sysadmin/yaml-tips 10 Tips by RedHat]

[https://betterprogramming.pub/10-things-you-might-not-know-about-yaml-b0589da547c 10 Things you might not know about YAML]

=== Websites ===

'''<code>yamllint</code>''' https://github.com/adrienverge/yamllint GPL3

=== Docs ===

https://github.com/adrienverge/yamllint

<br />

== Snippets ==

# This file IS valid YAML because the Jinja is in a YAML comment

# {% if extra_info %}

key1: value1

# {% endif %}

key2: value2

</syntaxhighlight>

[[Category:Markup]]

@@ Line 3: / Line 3: @@
 See [[wp:YAML]]
-I learned it when it was first introduced in 2001 so at that time it was known as "Yet Another Markup Language", however the acronym later became a recursive backcronym standing for "YAML Ain't Markup Language".
+I learned it when it was first introduced in 2001 so at that time it was known as "Yet Another Markup Language", however the acronym later became a recursive backcronym standing for "'''YAML Ain't Markup Language'''". So, what is it then? Well, it's a data serialization format. It is a superset of JSON, which means that any valid JSON is valid YAML.
-Used everywhere, such as [[Ansible]], so refer to https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html as well
+YAML is used everywhere, such as the [[Ansible]] project. Refer to [https://docs.ansible.com/ansible/latest/reference_appendices/YAMLSyntax.html Ansible reference appendices YAML Syntax]. If you want to use Ansible, learning YAML first will help you tremendously.
-== YAML Tips ==
+==Resources==
-https://www.redhat.com/sysadmin/yaml-tips
+[https://www.redhat.com/sysadmin/yaml-tips 10 Tips by RedHat]
+[https://betterprogramming.pub/10-things-you-might-not-know-about-yaml-b0589da547c 10 Things you might not know about YAML]
+{{#ev:youtube|UlkIZG3yiCM}}
+=== Websites ===
+'''<code>yamllint</code>''' https://github.com/adrienverge/yamllint GPL3
+=== Docs ===
+https://github.com/adrienverge/yamllint
+<br />
+== Snippets ==
+<syntaxhighlight lang="yaml+jinja">
+# This file IS valid YAML because the Jinja is in a YAML comment
+# {% if extra_info %}
+key1: value1
+# {% endif %}
+key2: value2
+</syntaxhighlight>
 [[Category:Markup]]