diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000000000..c08f9add7
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1 @@
+_site
\ No newline at end of file
diff --git a/_data/learning.yml b/_data/learning.yml
index 43c2a2f50..b9e5dc064 100644
--- a/_data/learning.yml
+++ b/_data/learning.yml
@@ -26,6 +26,7 @@ books:
       - link: /learn/quickstart/arrays_strings
       - link: /learn/quickstart/operators_control_flow
       - link: /learn/quickstart/organising_code
+      - link: /learn/quickstart/derived_types
 
 
 
diff --git a/_site/news.xml b/_site/news.xml
new file mode 100644
index 000000000..a29a6b081
--- /dev/null
+++ b/_site/news.xml
@@ -0,0 +1,465 @@
+<?xml version="1.0" encoding="utf-8"?>
+<feed xmlns="http://www.w3.org/2005/Atom">
+
+    <title type="text" xml:lang="en">Fortran Newsletter</title>
+    <link type="application/atom+xml" href="http://localhost:4000/news.xml" rel="self"/>
+    <link type="text" href="http://localhost:4000/news" rel="alternate"/>
+    <updated>2020-06-05T19:43:29+03:00</updated>
+    <id>/news</id>
+    <author>
+        <name></name>
+    </author>
+
+    
+    <entry>
+        <title>Fortran newsletter: June 2020</title>
+        <link href="http://localhost:4000/newsletter/2020/06/01/Fortran-Newsletter-June-2020/"/>
+        <updated>2020-06-01T00:00:00+03:00</updated>
+        <id>/news/newsletter/2020/06/01/Fortran-Newsletter-June-2020</id>
+        <content type="html">&lt;p&gt;Welcome to the June 2020 edition of the monthly Fortran newsletter.
+The newsletter comes out on the first calendar day of every month
+and details Fortran news from the previous month.&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;#fortran-lang.org&quot;&gt;fortran-lang.org&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#fortran-discourse&quot;&gt;Fortran Discourse&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#fortran-standard-library&quot;&gt;Standard Library&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#package-manager&quot;&gt;Package Manager&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#events&quot;&gt;Events&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#contributors&quot;&gt;Contributors&lt;/a&gt;&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;fortran-langorg&quot;&gt;fortran-lang.org&lt;/h2&gt;
+
+&lt;p&gt;The Fortran website has been up since mid-April, and we’ve already got great
+feedback from the community.
+In the past month we’ve updated the &lt;a href=&quot;/compilers&quot;&gt;Compilers&lt;/a&gt; page which is now
+comprehensive and includes all major open source and commercial compilers.
+The &lt;a href=&quot;/learn&quot;&gt;Learn&lt;/a&gt; page has also seen significant updates—it’s been
+reorganized for easier navigation and currently features a quickstart tutorial,
+Fortran books, and other online resources.&lt;/p&gt;
+
+&lt;p&gt;If you haven’t yet, please explore the website and &lt;a href=&quot;https://github.com/fortran-lang/fortran-lang.org/issues&quot;&gt;let us know&lt;/a&gt;
+if you have any suggestions for improvement.
+Specifically, we’ll be focusing on the &lt;a href=&quot;/learn&quot;&gt;Learn&lt;/a&gt; page and its mini-books
+in the coming months.
+Please help us make them better!&lt;/p&gt;
+
+&lt;p&gt;Here are some specific items that we worked on:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/fortran-lang.org/pull/90&quot;&gt;#90&lt;/a&gt;
+WIP: Mini-book on building programs&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/fortran-lang.org/pull/83&quot;&gt;#83&lt;/a&gt;
+Improving the structure and navigation of the &lt;a href=&quot;/learn&quot;&gt;Learn&lt;/a&gt; pages&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/fortran-lang.org/pull/46&quot;&gt;#46&lt;/a&gt;
+Build website previews from pull requests&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;fortran-discourse&quot;&gt;Fortran Discourse&lt;/h2&gt;
+
+&lt;p&gt;On May 4 we launched the &lt;a href=&quot;https://fortran-lang.discourse.group&quot;&gt;Fortran Discourse&lt;/a&gt;, an online discussion board
+for anything and everything Fortran related.
+You can use it discuss the Fortran language, ask for help, announce events and/or personal projects, or just lurk
+around. 
+There are already quite a few interesting discussions going on.
+Join us!&lt;/p&gt;
+
+&lt;h2 id=&quot;fortran-standard-library&quot;&gt;Fortran Standard Library&lt;/h2&gt;
+
+&lt;p&gt;Recently we launched a &lt;a href=&quot;https://stdlib.fortran-lang.org&quot;&gt;website&lt;/a&gt; for the API documentation of the Fortran Standard Library. 
+The &lt;a href=&quot;https://stdlib.fortran-lang.org&quot;&gt;website&lt;/a&gt; is automaticaly generated by &lt;a href=&quot;https://github.com/Fortran-FOSS-Programmers/ford#readme&quot;&gt;FORD&lt;/a&gt;.
+&lt;a href=&quot;https://stdlib.fortran-lang.org/page/contributing/CodeOfConduct.html&quot;&gt;Code of Conduct&lt;/a&gt;, &lt;a href=&quot;https://stdlib.fortran-lang.org/page/License.html&quot;&gt;licence&lt;/a&gt;, and &lt;a href=&quot;https://stdlib.fortran-lang.org/page/contributing/Workflow.html&quot;&gt;workflow&lt;/a&gt; for contributing to the Fortran Standard Library can also be found on the &lt;a href=&quot;https://stdlib.fortran-lang.org/&quot;&gt;website&lt;/a&gt;.&lt;/p&gt;
+
+&lt;p&gt;Here’s what’s new in the Fortran Standard Library:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/191&quot;&gt;#191&lt;/a&gt;
+WIP: Function for computing Pearson correlations among elements of
+an array in the &lt;code class=&quot;highlighter-rouge&quot;&gt;stdlib_experimental_stats&lt;/code&gt; module&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/189&quot;&gt;#189&lt;/a&gt;
+WIP: Procedures for sparse matrices operations. Ongoing discussion on the API can be found
+&lt;a href=&quot;https://github.com/fortran-lang/stdlib/wiki/Stdlib-Sparse-matrix-API&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/183&quot;&gt;#183&lt;/a&gt;
+Automatic API-doc generation and deployment of this &lt;a href=&quot;https://stdlib.fortran-lang.org&quot;&gt;stdlib website&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/170&quot;&gt;#170&lt;/a&gt;
+Addition of the new functions &lt;code class=&quot;highlighter-rouge&quot;&gt;diag&lt;/code&gt;, &lt;code class=&quot;highlighter-rouge&quot;&gt;eye&lt;/code&gt;, and &lt;code class=&quot;highlighter-rouge&quot;&gt;trace&lt;/code&gt; functions to make working with
+matrices easier.
+Read the full specifications &lt;a href=&quot;https://stdlib.fortran-lang.org/page/specs/stdlib_experimental_linalg.html&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;package-manager&quot;&gt;Package Manager&lt;/h2&gt;
+
+&lt;p&gt;In this past month support for dependencies between packages has been added
+to the &lt;a href=&quot;https://github.com/fortran-lang/fpm&quot;&gt;Fortran Package Manager (fpm)&lt;/a&gt;.
+You can specify either a path to another folder on your machine with an fpm package,
+or a git repository (and optionally a specific branch, tag or commit) that
+contains the package. fpm will then take care of fetching the dependency for you
+(if necessary) and any packages it depends on, and compiling and linking it into
+your project. Check out an example &lt;a href=&quot;https://gitlab.com/everythingfunctional/hello_fpm&quot;&gt;hello world package&lt;/a&gt;
+that uses this functionality.&lt;/p&gt;
+
+&lt;p&gt;fpm is still in very early development, and we need as much help as we can get.
+Here’s how you can help today:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;Try to use it. Does it work? No? Let us know! Read the &lt;a href=&quot;https://github.com/fortran-lang/fpm/blob/master/PACKAGING.md&quot;&gt;fpm packaging guide&lt;/a&gt; to learn how to build your package with fpm.&lt;/li&gt;
+  &lt;li&gt;Browse the &lt;a href=&quot;https://github.com/fortran-lang/fpm/issues&quot;&gt;open issues&lt;/a&gt; and see if you can help implement any fixes or features.&lt;/li&gt;
+  &lt;li&gt;Adapt your Fortran package for fpm.&lt;/li&gt;
+  &lt;li&gt;Improve the documentation.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;p&gt;The short term goal of fpm is to make development and installation of Fortran packages with dependencies easier.
+Its long term goal is to build a rich and decentralized ecosystem of Fortran packages and create a healthy
+environment in which new open source Fortran projects are created and published with ease.&lt;/p&gt;
+
+&lt;p&gt;Specific items that are new this month:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/fpm/pull/82&quot;&gt;#82&lt;/a&gt;
+You can now add remote git repositories as Fortran dependencies to your project.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/fortran-lang/fpm/pull/73&quot;&gt;#73&lt;/a&gt;
+Improved output messages for the user&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;events&quot;&gt;Events&lt;/h2&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;We hosted the very first Fortran Monthly call on May 14.
+The turnout was astonishing–over 23 people joined.
+You can read the notes from the call &lt;a href=&quot;https://fortran-lang.discourse.group/t/fortran-monthly-call-may-2020&quot;&gt;here&lt;/a&gt;.
+We’ll have another one this month.
+Subscribe to the &lt;a href=&quot;https://groups.io/g/fortran-lang&quot;&gt;mailing list&lt;/a&gt; and/or
+join the &lt;a href=&quot;https://fortran-lang.discourse.group&quot;&gt;Discourse&lt;/a&gt; to stay tuned.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://tcevents.chem.uzh.ch/event/12&quot;&gt;FortranCon 2020&lt;/a&gt; will take place on July 2-4 in Zurich, Switzerland.
+Virtual participation is enabled for both attendees and speakers.
+Registration is free and due by June 1, 2020.
+There are quite a few submissions from the fortran-lang community:
+A talk on &lt;a href=&quot;https://github.com/fortran-lang/talks/tree/master/FortranCon2020-stdlib&quot;&gt;stdlib&lt;/a&gt; by Jeremie Vandenplas,
+one about the &lt;a href=&quot;https://github.com/fortran-lang/talks/tree/master/FortranCon2020-fpm&quot;&gt;Fortran Package Manager (fpm)&lt;/a&gt; by Brad Richardson,
+a talk on &lt;a href=&quot;https://gitlab.com/lfortran/talks/fortrancon-2020-talk&quot;&gt;LFortran compiler&lt;/a&gt; by Ondřej Čertík,
+as well as one about &lt;a href=&quot;https://github.com/fortran-lang/talks/tree/master/FortranCon2020-community&quot;&gt;building the Fortran community&lt;/a&gt;
+by Milan Curcic.&lt;/li&gt;
+  &lt;li&gt;J3/WG5 joint meeting, originally slated for October 12-16 in Las Vegas, Nevada, has been &lt;a href=&quot;https://mailman.j3-fortran.org/pipermail/j3/2020-May/012034.html&quot;&gt;cancelled&lt;/a&gt;.
+However, the work on proposals for the Fortran Standard doesn’t stop.
+You can submit a proposal for the Standards committee &lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals&quot;&gt;here&lt;/a&gt;.
+For reference, you can read the &lt;a href=&quot;/newsletter/2020/02/28/J3-february-meeting&quot;&gt;notes from the February meeting&lt;/a&gt;.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;contributors&quot;&gt;Contributors&lt;/h2&gt;
+
+&lt;p&gt;We thank everybody who contributed to fortran-lang in the past month by
+commenting in any of the four repositories
+&lt;a href=&quot;https://github.com/fortran-lang/stdlib&quot;&gt;fortran-lang/stdlib&lt;/a&gt;,
+&lt;a href=&quot;https://github.com/fortran-lang/fpm&quot;&gt;fortran-lang/fpm&lt;/a&gt;,
+&lt;a href=&quot;https://github.com/fortran-lang/fortran-lang.org&quot;&gt;fortran-lang/fortran-lang.org&lt;/a&gt;,
+&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals&quot;&gt;j3-fortran/fortran_proposals&lt;/a&gt;:&lt;/p&gt;
+
+&lt;p&gt;Ondřej Čertík (&lt;a href=&quot;https://github.com/certik&quot;&gt;@certik&lt;/a&gt;), Milan Curcic (&lt;a href=&quot;https://github.com/milancurcic&quot;&gt;@milancurcic&lt;/a&gt;), Laurence Kedward (&lt;a href=&quot;https://github.com/LKedward&quot;&gt;@LKedward&lt;/a&gt;), Jeremie Vandenplas (&lt;a href=&quot;https://github.com/jvdp1&quot;&gt;@jvdp1&lt;/a&gt;), Brad Richardson (&lt;a href=&quot;https://github.com/everythingfunctional&quot;&gt;@everythingfunctional&lt;/a&gt;), Izaak “Zaak” Beekman (&lt;a href=&quot;https://github.com/zbeekman&quot;&gt;@zbeekman&lt;/a&gt;), Martin Diehl (&lt;a href=&quot;https://github.com/MarDiehl&quot;&gt;@MarDiehl&lt;/a&gt;), &lt;a href=&quot;https://github.com/arjenmarkus&quot;&gt;@arjenmarkus&lt;/a&gt;, Van Snyder (&lt;a href=&quot;https://github.com/vansnyder&quot;&gt;@vansnyder&lt;/a&gt;), &lt;a href=&quot;https://github.com/FortranFan&quot;&gt;@FortranFan&lt;/a&gt;, &lt;a href=&quot;https://github.com/epagone&quot;&gt;@epagone&lt;/a&gt;, Ivan (&lt;a href=&quot;https://github.com/ivan-pi&quot;&gt;@ivan-pi&lt;/a&gt;), Neil Carlson (&lt;a href=&quot;https://github.com/nncarlson&quot;&gt;@nncarlson&lt;/a&gt;), Ashwin Vishnu (&lt;a href=&quot;https://github.com/ashwinvis&quot;&gt;@ashwinvis&lt;/a&gt;), Williams A. Lima (&lt;a href=&quot;https://github.com/ghwilliams&quot;&gt;@ghwilliams&lt;/a&gt;), Peter Klausler (&lt;a href=&quot;https://github.com/klausler&quot;&gt;@klausler&lt;/a&gt;), Chris MacMackin (&lt;a href=&quot;https://github.com/cmacmackin&quot;&gt;@cmacmackin&lt;/a&gt;), Pedro Costa (&lt;a href=&quot;https://github.com/p-costa&quot;&gt;@p-costa&lt;/a&gt;), &lt;a href=&quot;https://github.com/mobius-eng&quot;&gt;@mobius-eng&lt;/a&gt;, Salvatore Filippone (&lt;a href=&quot;https://github.com/sfilippone&quot;&gt;@sfilippone&lt;/a&gt;), &lt;a href=&quot;https://github.com/ShamanTcler&quot;&gt;@ShamanTcler&lt;/a&gt;, Amit Kumar (&lt;a href=&quot;https://github.com/aktech&quot;&gt;@aktech&lt;/a&gt;), Bálint Aradi (&lt;a href=&quot;https://github.com/aradi&quot;&gt;@aradi&lt;/a&gt;), Melissa Weber Mendonça (&lt;a href=&quot;https://github.com/melissawm&quot;&gt;@melissawm&lt;/a&gt;), Jacob Williams (&lt;a href=&quot;https://github.com/jacobwilliams&quot;&gt;@jacobwilliams&lt;/a&gt;), Rohit Goswami (&lt;a href=&quot;https://github.com/HaoZeke&quot;&gt;@HaoZeke&lt;/a&gt;), Amir Shahmoradi (&lt;a href=&quot;https://github.com/shahmoradi&quot;&gt;@shahmoradi&lt;/a&gt;), Bill Long (&lt;a href=&quot;https://github.com/longb&quot;&gt;@longb&lt;/a&gt;).&lt;/p&gt;
+</content>
+    </entry>
+    
+    <entry>
+        <title>Fortran newsletter: May 2020</title>
+        <link href="http://localhost:4000/newsletter/2020/05/01/Fortran-Newsletter-May-2020/"/>
+        <updated>2020-05-01T00:00:00+03:00</updated>
+        <id>/news/newsletter/2020/05/01/Fortran-Newsletter-May-2020</id>
+        <content type="html">&lt;div class=&quot;language-fortran highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt;&lt;span class=&quot;k&quot;&gt;print&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;o&quot;&gt;*&lt;/span&gt;&lt;span class=&quot;p&quot;&gt;,&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; &lt;/span&gt;&lt;span class=&quot;s1&quot;&gt;'Hello, World!'&lt;/span&gt;&lt;span class=&quot;w&quot;&gt; 
+&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
+
+&lt;p&gt;Welcome to the first monthly Fortran newsletter.
+It will come out on the first calendar day of every month, 
+detailing Fortran news from the previous month.&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;#this-website&quot;&gt;This website&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#standard-library&quot;&gt;Standard Library&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#package-manager&quot;&gt;Package Manager&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#wg5-convenor-candidates&quot;&gt;WG5 Convenor candidates&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#events&quot;&gt;Events&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;#whos-hiring&quot;&gt;Who’s hiring?&lt;/a&gt;&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;this-website&quot;&gt;This website&lt;/h2&gt;
+
+&lt;p&gt;If you came to this newsletter from elsewhere, welcome to the new Fortran website.
+We built this site mid-April and hope for it to be &lt;em&gt;the&lt;/em&gt; home of Fortran on the internet,
+which traditionally there hasn’t been any to date.
+Look around and &lt;a href=&quot;https://github.com/fortran-lang/fortran-lang.github.io/issues&quot;&gt;let us know&lt;/a&gt; 
+if you have any suggestions for improvement.
+Specifically, &lt;a href=&quot;/learn&quot;&gt;Learn&lt;/a&gt; and &lt;a href=&quot;/packages&quot;&gt;Packages&lt;/a&gt; are the pages that 
+we’ll be focusing on in the coming months. 
+Please help us make them better!&lt;/p&gt;
+
+&lt;h2 id=&quot;standard-library&quot;&gt;Standard Library&lt;/h2&gt;
+
+&lt;p&gt;Here’s what’s new in Fortran Standard Library:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/172&quot;&gt;#172&lt;/a&gt;
+New function &lt;code class=&quot;highlighter-rouge&quot;&gt;cov&lt;/code&gt; in the &lt;code class=&quot;highlighter-rouge&quot;&gt;stdlib_experimental_stats&lt;/code&gt; module to compute covariance of array elements.
+Read the full specification &lt;a href=&quot;https://github.com/fortran-lang/stdlib/blob/master/src/stdlib_experimental_stats.md#cov---covariance-of-array-elements&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+  &lt;/li&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/168&quot;&gt;#168&lt;/a&gt;
+Specify recommended order of attributes for dummy arguments in the 
+&lt;a href=&quot;https://github.com/fortran-lang/stdlib/blob/master/STYLE_GUIDE.md&quot;&gt;Stdlib style guide&lt;/a&gt;.&lt;/p&gt;
+  &lt;/li&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/173&quot;&gt;#173&lt;/a&gt;
+Minor bug fix.&lt;/p&gt;
+  &lt;/li&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;a href=&quot;https://github.com/fortran-lang/stdlib/pull/170&quot;&gt;#170&lt;/a&gt;
+WIP: Addition of &lt;code class=&quot;highlighter-rouge&quot;&gt;diag&lt;/code&gt;, &lt;code class=&quot;highlighter-rouge&quot;&gt;eye&lt;/code&gt;, and &lt;code class=&quot;highlighter-rouge&quot;&gt;trace&lt;/code&gt; functions to make working with 
+matrices easier.&lt;/p&gt;
+  &lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;package-manager&quot;&gt;Package Manager&lt;/h2&gt;
+
+&lt;p&gt;In the past month we’ve seen the first working implementation of the &lt;a href=&quot;https://github.com/fortran-lang/fpm&quot;&gt;Fortran Package Manager (FPM)&lt;/a&gt;.
+Specifically:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;FPM supports three commands:
+    &lt;ul&gt;
+      &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;fpm build&lt;/code&gt;–compiles and links your application and/or library.&lt;/li&gt;
+      &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;fpm test&lt;/code&gt;–runs tests if your package has any test programs.&lt;/li&gt;
+      &lt;li&gt;&lt;code class=&quot;highlighter-rouge&quot;&gt;fpm run&lt;/code&gt;–runs the application if your package has an executable program.&lt;/li&gt;
+    &lt;/ul&gt;
+  &lt;/li&gt;
+  &lt;li&gt;FPM can build an executable program, a library, or a combination of both.&lt;/li&gt;
+  &lt;li&gt;Currently only gfortran is supported as the compiler backend. FPM will suport other compilers soon.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;p&gt;Read the &lt;a href=&quot;https://github.com/fortran-lang/fpm/blob/master/PACKAGING.md&quot;&gt;FPM packaging guide&lt;/a&gt;
+to learn how to build your package with FPM.&lt;/p&gt;
+
+&lt;p&gt;FPM is still in very early development, and we need as much help as we can get.
+Here’s how you can help today:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;Try to use it. Does it work? No? Let us know!&lt;/li&gt;
+  &lt;li&gt;Browse the &lt;a href=&quot;https://github.com/fortran-lang/fpm/issues&quot;&gt;open issues&lt;/a&gt; and see if you can help implement any fixes or features.&lt;/li&gt;
+  &lt;li&gt;Adapt your Fortran package for FPM.&lt;/li&gt;
+  &lt;li&gt;Improve the documentation.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;p&gt;The short term goal of FPM is to make development and installation of Fortran packages with dependencies easier.
+Its long term goal is to build a rich and decentralized ecosystem of Fortran packages and create a healthy 
+environment in which new open source Fortran projects are created and published with ease.&lt;/p&gt;
+
+&lt;h2 id=&quot;wg5-convenor-candidates&quot;&gt;WG5 Convenor candidates&lt;/h2&gt;
+
+&lt;p&gt;Last month was also the deadline for the &lt;a href=&quot;https://wg5-fortran.org/&quot;&gt;WG5&lt;/a&gt;
+convenor candidates to apply for the next 3-year term (2021-2024).
+There are two candidates:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;a href=&quot;https://stevelionel.com&quot;&gt;Steve Lionel&lt;/a&gt;, who is also the current WG5 convenor,
+announced running for another term.
+Read Steve’s &lt;a href=&quot;https://stevelionel.com/drfortran/2020/04/25/doctor-fortran-in-forward&quot;&gt;post&lt;/a&gt;
+about how he has guided the standardization process over the past three years and his direction for the future.&lt;/p&gt;
+  &lt;/li&gt;
+  &lt;li&gt;
+    &lt;p&gt;&lt;a href=&quot;https://ondrejcertik.com&quot;&gt;Ondřej Čertík&lt;/a&gt; has also announced announced to run
+for the WG5 convenor.
+Read Ondřej’s &lt;a href=&quot;https://ondrejcertik.com/blog/2020/04/running-for-wg5-convenor-announcement/&quot;&gt;announcement&lt;/a&gt;
+and &lt;a href=&quot;https://github.com/certik/wg5_platform_2020&quot;&gt;platform&lt;/a&gt;
+that detail current issues with Fortran language development and how to
+overcome them going forward.&lt;/p&gt;
+  &lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;events&quot;&gt;Events&lt;/h2&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://openteams.com&quot;&gt;OpenTeams&lt;/a&gt; and &lt;a href=&quot;https://quansight.com&quot;&gt;QuanSight&lt;/a&gt; hosted Ondřej Čertík and Milan Curcic
+in the Episode 40 of the Open Source Directions Webinar.
+They talked about the current state and future of Fortran, as well as about building the Fortran community and developer tools.
+Read more about it and watch the video &lt;a href=&quot;/newsletter/2020/04/18/Fortran-Webinar/&quot;&gt;here&lt;/a&gt;.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://tcevents.chem.uzh.ch/event/12&quot;&gt;FortranCon 2020&lt;/a&gt; will take place on July 2-4 in Zurich, Switzerland.
+Virtual participation is enabled for both attendees and speakers.
+Registration is free and due by June 1, 2020.&lt;/li&gt;
+  &lt;li&gt;J3/WG5 joint meeting will take place on October 12-16 in Las Vegas, Nevada.
+You can submit a proposal for the Standards committee &lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals&quot;&gt;here&lt;/a&gt;.
+For reference, you can read the &lt;a href=&quot;/newsletter/2020/02/28/J3-february-meeting&quot;&gt;notes from the February meeting&lt;/a&gt;.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;whos-hiring&quot;&gt;Who’s hiring?&lt;/h2&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://g.co/kgs/aogdeh&quot;&gt;Intel Corporation (Santa Clara, CA): Software Engineer, Fortran&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://g.co/kgs/5X3d2Y&quot;&gt;Intel Corporation (Hillsboro, OR): Software Engineer, Fortran&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://g.co/kgs/yuaohU&quot;&gt;Pozent (York, PA): Fortran Technical Lead&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://g.co/kgs/VAWjWk&quot;&gt;American Cybersystems, Inc. (Binghamton, NY): Software Engineer (Fortran, C/C++, Ada, C#, Java, Radar)&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://g.co/kgs/eLsn63&quot;&gt;BravoTech (Dallas, TX): C++ / Fortran Developer&lt;/a&gt;&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://g.co/kgs/eYftiA&quot;&gt;Siemens (Milford, OH): CAE Software Engineer (Fortran or C++) Design and Topology Optimization&lt;/a&gt;&lt;/li&gt;
+&lt;/ul&gt;
+</content>
+    </entry>
+    
+    <entry>
+        <title>Open Source Directions Fortran webinar</title>
+        <link href="http://localhost:4000/newsletter/2020/04/18/Fortran-Webinar/"/>
+        <updated>2020-04-18T00:00:00+03:00</updated>
+        <id>/news/newsletter/2020/04/18/Fortran-Webinar</id>
+        <content type="html">&lt;p&gt;Ondřej Čertík (&lt;a href=&quot;https://twitter.com/ondrejcertik&quot;&gt;@ondrejcertik&lt;/a&gt;) and 
+Milan Curcic (&lt;a href=&quot;https://twitter.com/realmilancurcic&quot;&gt;@realmilancurcic&lt;/a&gt;) spoke 
+yesterday about the future of Fortran in Episode 40 of the Open Source 
+Directions Webinar.
+We discussed the current state of the language, how it’s currently developed, 
+and what we can do today to build the Fortran community, ecosystem of packages, 
+and developer tools.&lt;/p&gt;
+
+&lt;p&gt;Watch the episode now:&lt;/p&gt;
+
+&lt;iframe width=&quot;560&quot; height=&quot;315&quot; src=&quot;https://www.youtube.com/embed/2NiS2tdDO_4&quot; frameborder=&quot;0&quot; allow=&quot;accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture&quot; allowfullscreen=&quot;&quot;&gt;&lt;/iframe&gt;
+
+&lt;p&gt;Special thanks to our hosts Melissa Mendonça 
+(&lt;a href=&quot;https://twitter.com/melissawm&quot;&gt;@melissawm&lt;/a&gt;) and Madicken Munk 
+(&lt;a href=&quot;https://twitter.com/munkium&quot;&gt;@munkium&lt;/a&gt;), as well as 
+&lt;a href=&quot;https://openteams.com&quot;&gt;OpenTeams&lt;/a&gt; and &lt;a href=&quot;https://www.quansight.com/&quot;&gt;QuanSight&lt;/a&gt;
+for having us.&lt;/p&gt;
+
+&lt;p&gt;You can find all previous episodes of the Open Source Directions webinar 
+&lt;a href=&quot;https://www.quansight.com/open-source-directions&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+</content>
+    </entry>
+    
+    <entry>
+        <title>Announcing FortranCon 2020</title>
+        <link href="http://localhost:4000/newsletter/2020/04/06/Announcing-FortranCon-2020/"/>
+        <updated>2020-04-06T00:00:00+03:00</updated>
+        <id>/news/newsletter/2020/04/06/Announcing-FortranCon-2020</id>
+        <content type="html">&lt;p&gt;FortranCon 2020, the first international conference targeting the Fortran
+programming language, will take place on July 2-4, 2020, in Zürich, Switzerland.&lt;/p&gt;
+
+&lt;blockquote class=&quot;twitter-tweet&quot;&gt;&lt;p lang=&quot;en&quot; dir=&quot;ltr&quot;&gt;We&amp;#39;re happy to announce the (to our knowledge first) International &lt;a href=&quot;https://twitter.com/hashtag/Fortran?src=hash&amp;amp;ref_src=twsrc%5Etfw&quot;&gt;#Fortran&lt;/a&gt; &lt;a href=&quot;https://twitter.com/hashtag/Conference?src=hash&amp;amp;ref_src=twsrc%5Etfw&quot;&gt;#Conference&lt;/a&gt; July 2.-4. at the &lt;a href=&quot;https://twitter.com/UZH_en?ref_src=twsrc%5Etfw&quot;&gt;@UZH_en&lt;/a&gt; in &lt;a href=&quot;https://twitter.com/hashtag/Zurich?src=hash&amp;amp;ref_src=twsrc%5Etfw&quot;&gt;#Zurich&lt;/a&gt;, &lt;a href=&quot;https://twitter.com/hashtag/Switzerland?src=hash&amp;amp;ref_src=twsrc%5Etfw&quot;&gt;#Switzerland&lt;/a&gt; with &lt;a href=&quot;https://twitter.com/DoctorFortran?ref_src=twsrc%5Etfw&quot;&gt;@DoctorFortran&lt;/a&gt; joining as keynote speaker! Call for presentations is open: &lt;a href=&quot;https://t.co/LnyOZxHrZI&quot;&gt;https://t.co/LnyOZxHrZI&lt;/a&gt; &lt;a href=&quot;https://twitter.com/hashtag/HPC?src=hash&amp;amp;ref_src=twsrc%5Etfw&quot;&gt;#HPC&lt;/a&gt;&lt;/p&gt;&amp;mdash; tizianomueller (@tizianomueller) &lt;a href=&quot;https://twitter.com/tizianomueller/status/1247121616326348800?ref_src=twsrc%5Etfw&quot;&gt;April 6, 2020&lt;/a&gt;&lt;/blockquote&gt;
+&lt;script async=&quot;&quot; src=&quot;https://platform.twitter.com/widgets.js&quot; charset=&quot;utf-8&quot;&gt;&lt;/script&gt;
+
+&lt;p&gt;FortranCon aims to bring together developers of Fortran libraries, 
+applications, and language itself to share their experience and ideas.
+The conference is organized in two full days of speaker presentations 
+on July 2 and 3, and a half-day workshop with lectures and hands-on sessions
+on July 4.
+Click &lt;a href=&quot;https://tcevents.chem.uzh.ch/event/12/abstracts/&quot;&gt;here&lt;/a&gt; to submit
+an abstract.&lt;/p&gt;
+
+&lt;p&gt;The keynote presentation will be delivered by Steve Lionel 
+(&lt;a href=&quot;https://twitter.com/doctorfortran&quot;&gt;@doctorfortran&lt;/a&gt;), convener of the 
+US Fortran Standards Committee.&lt;/p&gt;
+
+&lt;p&gt;The &lt;a href=&quot;https://tcevents.chem.uzh.ch/event/12/registrations/&quot;&gt;registration&lt;/a&gt; 
+is &lt;strong&gt;free of charge&lt;/strong&gt;, with June 1, 2020 as the deadline.
+Virtual participation will be enabled for speakers and attendees unable to 
+travel.&lt;/p&gt;
+
+&lt;p&gt;Read more about FortranCon 2020 &lt;a href=&quot;https://tcevents.chem.uzh.ch/event/12/&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
+</content>
+    </entry>
+    
+    <entry>
+        <title>J3 February 2020 Meeting</title>
+        <link href="http://localhost:4000/newsletter/2020/02/28/J3-february-meeting/"/>
+        <updated>2020-02-28T00:00:00+02:00</updated>
+        <id>/news/newsletter/2020/02/28/J3-february-meeting</id>
+        <content type="html">&lt;p&gt;The J3 Fortran Committee meeting took place in Las Vegas, NV, on February 24-28,
+2020.&lt;/p&gt;
+
+&lt;h2 id=&quot;attendance&quot;&gt;Attendance&lt;/h2&gt;
+
+&lt;p&gt;The following people / companies attended:&lt;/p&gt;
+
+&lt;p&gt;Voting members:&lt;/p&gt;
+
+&lt;ol&gt;
+  &lt;li&gt;Intel: Jon Steidel&lt;/li&gt;
+  &lt;li&gt;HPE/Cray: Bill Long&lt;/li&gt;
+  &lt;li&gt;NVIDIA: Peter Klausler, Gary Klimowicz&lt;/li&gt;
+  &lt;li&gt;IBM: Daniel Chen&lt;/li&gt;
+  &lt;li&gt;ARM: Srinath Vadlamani&lt;/li&gt;
+  &lt;li&gt;NCAR: Dan Nagle, Magne Haveraaen&lt;/li&gt;
+  &lt;li&gt;NASA: Tom Clune&lt;/li&gt;
+  &lt;li&gt;JPL: Van Sneider&lt;/li&gt;
+  &lt;li&gt;LANL: Zach Jibben, Ondřej Čertík&lt;/li&gt;
+  &lt;li&gt;ORNL: Reuben Budiardja&lt;/li&gt;
+  &lt;li&gt;LBNL: Brian Friesen&lt;/li&gt;
+  &lt;li&gt;Sandia: Damian Rouson&lt;/li&gt;
+  &lt;li&gt;Lionel: Steven Lionel, Malcolm Cohen, Vipul Parekh&lt;/li&gt;
+  &lt;li&gt;Corbett: Bob Corbett&lt;/li&gt;
+&lt;/ol&gt;
+
+&lt;p&gt;Others:&lt;/p&gt;
+
+&lt;ol&gt;
+  &lt;li&gt;AMD: Richard Bleikamp&lt;/li&gt;
+  &lt;li&gt;WG23: Stephen Michell (convenor), Erhard Ploedereder (member)&lt;/li&gt;
+  &lt;li&gt;Structural Integrity: Brad Richardson&lt;/li&gt;
+&lt;/ol&gt;
+
+&lt;h2 id=&quot;proposals-discussed-at-plenary&quot;&gt;Proposals Discussed at Plenary&lt;/h2&gt;
+
+&lt;h3 id=&quot;monday-224&quot;&gt;Monday 2/24&lt;/h3&gt;
+
+&lt;h3 id=&quot;tuesday-225&quot;&gt;Tuesday 2/25&lt;/h3&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/22&quot;&gt;#22&lt;/a&gt; : Default values of optional arguments (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-107.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-107.txt&lt;/a&gt;)&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h3 id=&quot;wednesday-226&quot;&gt;Wednesday 2/26&lt;/h3&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/157&quot;&gt;#157&lt;/a&gt; : Rank-agnostic array element and section denotation (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-113.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-113.txt&lt;/a&gt;, &lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-115.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-115.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/158&quot;&gt;#158&lt;/a&gt; : TYPEOF and CLASSOF (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-114.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-114.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/1&quot;&gt;#1&lt;/a&gt; : Namespace for modules (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-108.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-108.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;Interpretation: FORM TEAM and failed images (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-102r1.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-102r1.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;Interpretation: Collective subroutines and STAT= (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-104r1.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-104r1.txt&lt;/a&gt;)&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h3 id=&quot;thursday-227&quot;&gt;Thursday 2/27&lt;/h3&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;Interpretation: events that cause variables to become undefined (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-119.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-119.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;Edits for SIMPLE procedures (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-116.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-116.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;BFLOAT16 (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-118.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-118.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/146&quot;&gt;#146&lt;/a&gt; : Interpretation: allocatable component finalization (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-117.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-117.txt&lt;/a&gt;)&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h3 id=&quot;friday-228&quot;&gt;Friday 2/28&lt;/h3&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/157&quot;&gt;#157&lt;/a&gt; : Rank-agnostic syntax (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-120.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-120.txt&lt;/a&gt;). Passed unanimously with minor changes.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/156&quot;&gt;#156&lt;/a&gt; : Protected components (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-121.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-121.txt&lt;/a&gt;). Withdrawn to address conflicting interests.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/160&quot;&gt;#160&lt;/a&gt; : Edits for auto-allocate characters (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-122.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-122.txt&lt;/a&gt;). Passed unanimously with minor changes.&lt;/li&gt;
+  &lt;li&gt;Edits for procedure pointer association (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-123.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-123.txt&lt;/a&gt;). Passed unanimously.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/157&quot;&gt;#157&lt;/a&gt; : Edits for rank-agnostic bounds (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-124.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-124.txt&lt;/a&gt;). Withdrawn because some edits were missing and need to be added. There were concerns about fitting into the framework of generics later on.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/157&quot;&gt;#157&lt;/a&gt; : Edits for rank-agnostic array element and section denotation (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-125.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-125.txt&lt;/a&gt;). Failed (5 v 7). Missing edits, and disagreement on types vs rank-1 integers, the options need to be explored more.&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/157&quot;&gt;#157&lt;/a&gt; : Edits for rank-agnostic allocation and pointer assignment (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-126.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-126.txt&lt;/a&gt;). Passed unanimously with minor changes.&lt;/li&gt;
+  &lt;li&gt;Interpretation: Public namelist and private variable (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-127.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-127.txt&lt;/a&gt;). Straw vote (0 yes, 8 no, 9 undecided). Passed unanimously with “no” alternative.&lt;/li&gt;
+  &lt;li&gt;Interpretation F18/015 (&lt;a href=&quot;https://j3-fortran.org/doc/year/20/20-105.txt&quot;&gt;https://j3-fortran.org/doc/year/20/20-105.txt&lt;/a&gt;). Passed unanimously.&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;skipped&quot;&gt;Skipped&lt;/h2&gt;
+
+&lt;p&gt;This was on the plan but we did not get to it:&lt;/p&gt;
+
+&lt;ul&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/5&quot;&gt;#5&lt;/a&gt; : US 27 POINTER dummy arguments, INTENT, and target modification (&lt;a href=&quot;https://j3-fortran.org/doc/year/18/18-144r1.txt&quot;&gt;https://j3-fortran.org/doc/year/18/18-144r1.txt&lt;/a&gt;)&lt;/li&gt;
+  &lt;li&gt;&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/19&quot;&gt;#19&lt;/a&gt; : Short-circuiting proposal&lt;/li&gt;
+&lt;/ul&gt;
+
+&lt;h2 id=&quot;more-details&quot;&gt;More Details&lt;/h2&gt;
+
+&lt;p&gt;More details available at
+&lt;a href=&quot;https://github.com/j3-fortran/fortran_proposals/issues/155&quot;&gt;j3-fortran/fortran_proposals #155&lt;/a&gt; and at the official &lt;a href=&quot;https://j3-fortran.org/doc/year/20/minutes221.txt&quot;&gt;minutes&lt;/a&gt; from the meeting.&lt;/p&gt;
+
+</content>
+    </entry>
+    
+
+</feed>
diff --git a/learn/quickstart/derived_types.md b/learn/quickstart/derived_types.md
new file mode 100644
index 000000000..6c769858a
--- /dev/null
+++ b/learn/quickstart/derived_types.md
@@ -0,0 +1,298 @@
+---
+layout: book
+title: Derived types
+permalink: /learn/quickstart/derived_types
+---
+
+As discussed previously in [Variables]({{site.baseurl}}/learn/quickstart/variables) there are five built-in data types in Fortran. _Derived types_ is a special form of a data type that can encapsulate other built-in types as well as other _derived types_. It could be considered as the equivalent of _struct_ in the C/C++ programming languages.
+
+## A quick take on derived types
+
+Example of a basic derived type:
+
+```fortran
+type :: my_type
+    integer :: i
+    real    :: x
+end type
+```
+
+The syntax for creating a variable of type _my_type_ and accessing its members:
+```fortran
+! declare
+type(my_type) :: foo
+! initialize
+foo%i   = 1
+foo%x   = 0.5
+```
+
+{% include note.html content="In Fortran the percentage symbol `%` is used to access the members of a derived type." %}
+
+To initialize the members of _my_type_ one can use either individual initialization as demonstrated in the above example, or the assignment operator (=), or the default initialization.
+
+
+Example using the assignement operator (=):
+```fortran
+foo = my_type(1, 0.5)
+! or using F2003 stardard and on
+foo = my_type(i=1, x=0.5)
+```
+
+Example with default initialization:
+```fortran
+type :: my_type
+    integer :: i = 1
+    real    :: x = 0.5
+end type
+! then it is possible to use as
+type(my_type) :: foo
+foo = my_type(i=2) ! foo%i gets a new value, but foo%x retains the default one.
+```
+
+## Derived types in detail
+
+The full syntax of a derived type with all optional properties is presented below:
+
+```fortran
+type [,attribute-list] :: name [(parameterized-decleration-list)]
+    [parameterized-definition-statements]
+    [private statement or sequence statement]
+    [member-variables]
+    contains
+        [type-bound-procedures]
+end type
+```
+
+### Part 1: Options to declare a derived type
+
+`attribute-list` may refer to the following:
+
+- _access-type_ that is either `public` or `private`
+- `bind(c)` offers interoperability with C programming language 
+- `extends(`_parent_`)` where _parent_ is the name of a previously declared derived type, from which, the current derived type will inherit all its members and functionality.
+- `abstract` an object orianted feature that is covered in the advanced programming tutorial.
+
+{% include note.html content="If the `attribute: bind(c)` or the `statement: sequence` is used then a derived type cannot have the `attribute: extends` and visa-versa." %}
+
+The `sequence` attribute may be used only to declare that the following  members should be accessed in the same order as they are defined within the derived type. 
+
+Example with `sequence`:
+```fortran
+type :: foo
+sequence
+integer :: var1
+real    :: var2
+end type
+! init
+type(foo) :: bar
+bar = foo(1, 0.5)
+```
+{% include note.html content="The use of statement `sequence` presupposes that the data types defined below are neither of `allocatable` nor of `pointer` type. Furthermore, it does not imply that these data types  will be stored in memory in any particular form, there is no relation to `contigeous` attribute." %}
+
+The _access-type_ attributes `public` and `private` if used, declare that all [member-variables] declared below will be automatically assigned the attribute accordingly. 
+
+The attribute `bind(c)` is used to achieve compatibility between Fortran's derived type and C's struct.
+
+Example with 'bind(c)`:
+```fortran
+module mymod
+use iso_c_bindings
+implicit none
+type, bind(c) :: mytype
+    integer(c_int) :: i
+end type
+```
+matches the following C struct:
+```c
+struct{
+    int i
+}mytype;
+```
+{% include note.html content="A fortran derived type with the attribute `bind(c)` cannot have the `sequence` and `extends` attributes. Furthermore it cannot contain any Fortran `pointer` or `allocatable` types." %}
+
+`parameterized-decleration-list`: is an optional feautre. If used, then the parameters must be listed in place of [parameterized-definition-statements] and must be either `len` or `kind` parameters or both. 
+
+Example of a derived type with `parameterized-decleration-list` and with the `attribute: public`:
+ ```fortran
+module mymod
+implicit none
+private
+
+type, public :: matrix(rows, cols, k)
+  integer, len :: rows, cols
+  integer, kind :: k = kind(0.0)
+  real(kind = k), dimension(rows, cols) :: values
+end type matrix
+end module
+
+program test
+use mymod
+implicit none
+type(matrix(rows=5, cols=5)) :: m
+end program
+ ```
+{% include note.html content="In this example the parameter **k** has already been assigned a default value of `kind(0.0)`, that is of floating point single precision, for that reason it can be ommited, as it is the case here in the declaration inside the main program." %}
+
+{% include important.html content="By default derived types and their members are public. However, in this example the attribute `private` is used at the beginning of the module, therefore, everything within the module will be by default `private` unless, explicitly, declared as `public`. If the type **matrix** was not given the attribute `public` in the above example, then the compiler would throw an error inside **program test**." %}
+
+The attribute `extends` was added in F2003 standard and introduces an important feature of the object oriented paradigm (OOP), namely the inheritance. It allows code reusability by letting children-derived-types like this: `type, extends(parent) :: child` to inherit all the members and functionality from a parent-derived-type: `type :: parent`.  
+
+Example with the attribute `extends`: 
+```fortran
+module mymod
+implicit none
+private
+public t_date, t_address, t_person, t_employ ! note another way of using the public attribute by gathering all public data types in one place
+
+type :: t_date
+    integer                         :: year, month, day
+end type
+
+type :: t_address
+    character(len=:), allocatable   :: city, road_name
+    integer                         :: house_number
+end type
+
+type, extends(t_address) :: t_person
+    character(len=:), allocatable   :: first_name, last_name, e_mail  
+end type
+
+type, extends(t_person)  :: t_employ
+    type(t_date)                    :: hired_date
+    character(len=:), allocatable   :: position
+    real                            :: monthly_salary
+end type
+end module
+
+program test
+use mymod
+implicit none
+type(t_employ) :: employ
+
+! initialization
+employ%hired_date%year  = 2020 ! t_employ has access to type(t_date) members not because of extends but because a type(t_date) was declared within t_employ
+employ%hired_date%month = 1
+employ%hired_date%day   = 20
+employ%first_name       = 'Johny' !t_employ has acces to t_person, and inherits its members due to extends 
+employ%last_name        = 'Doe'
+employ%city             = 'London' ! t_employ has access to t_address, because it inherits from t_person, that in return inherits from t_address
+employ%road_name        = 'BigBen'
+employ%house_number     = 1
+employ%position         = 'Intern'
+employ%monthly_salary   = 0.0
+end program
+``` 
+
+### Part 2: Options to declare members of a derived type
+
+`[member-variables]` refers to the decleration of all the member data types. These data types can be of any built-in data type, and/or of other derived types, as already show-cased in the above examples. However, member-variables can have their own extensive syntax, in form of:
+`type [,member-attributes] :: name[attr-dependent-spec][init]`
+
+`type`: any built-in type or other derived type
+
+`member-attributes` (optional):
+
+- `pointer` to specify a pointer
+- `allocatable` with or without `dimension` to specify a dynamic array
+- `public` or `private` access attributes
+- `protected` access attribute
+- `codimension` to specify a coarray 
+- `contigeous`
+
+{% include note.html content="`pointer` and `allocatable` cannot co-exist." %}
+
+{% include note.html content="`contigeous` requires an array with the `pointer` attribute." %}
+
+Examples for common cases:
+
+```fortran
+type :: t_example
+    !1st case: simple built-in type with access attribute and [init]
+    integer, private :: i = 0 ! private hides it from use outside of the t_example's scope. The default initialization [=0] is the [init] part. 
+
+    !2nd case: dynamic 1d_array
+    real, allocatable, dimension(:) :: x
+    ! the same as
+    real, allocatable :: x(:) ! parenthesis implies dimension(:) and is one of the possible [attr-dependent-spec].
+
+    !3rd case: protected
+    integer, protected :: i ! In contrary to private, protected allows access to i assigned value outside of t_example but is not definable, i.e. a value may be assigned to i only within t_example.
+
+    !4th case: pointer, with [init]
+    real, pointer :: x(:) => null() ! the [init] part is the [=>null()], pointers are discussed in the Advanced programming mini-book. 
+
+    !5th case: coarray
+    real, allocatable, codimension[:] :: z(:) ! a 1d_dynamic array shared in all threads. Coarrays will be discussed in the Advanced programming mini-book.
+    !or 
+    real, allocatable :: z(:)[:] ! here the [:] is the [attr-dependent-spec] and implies the codimension[:].
+
+    !6th case: contigeous
+    real, contigeous, pointer :: x(:)
+end type
+```
+
+{% include note.html content="In the above example the cases 4, 5 and 6 make use of Fortran `pointer` and `coarray` features that have not been addressed in this quickstart tutorial. However, they are presented here, in order for the readers to know that these feautures do exist and be able to recognise them. These features will be covered in detail in the upcoming `Advanced programing` mini-book." %}
+
+### Part 3: Type-bound procedures
+
+A derivd type is possible to contain procedures either `functions` or `subroutines` that are **bound** to this derived type. Type procedures must follow the `contains` statement that, in return, must be used within the derived type and after all [member-variables] have been declared. 
+
+{% include note.html content="It is impossible to describe type-bound procedures in their full syntax without delving into OOP features of modern Fortran. For that reason only a simple example is provided in this final part, to demostrante a very besic use." %}
+
+Example of a derived type with basic bound-procedure:
+
+```fortran
+module mymod
+implicit none
+private
+public t_square
+
+type :: t_square
+    real :: side
+    contains
+        procedure :: area !procedure decleration
+end type
+
+contains
+    ! procedure definition
+    real function area(self) result(res)
+        class(t_square), intent(in) :: self 
+        res = self%side * self%side
+    end function
+end module
+
+program main
+use mymod
+implicit none
+! variables decleration
+type(t_square) :: sq
+real :: x, side
+
+! variables initialization
+side    = 0.5
+sq%side = side
+
+x       = sq%area() ! self does not appear here, it has been passed implicitly
+! do stuff with x...
+end program
+```
+What is new:
+
+ - **self** is a random name that was chosen to represent the derived type t_square that is passed as an argument to the bound-function in order to have access to its data-members. By passing it like that it is ensured that later during its use the t_square will be passed automatically and not by the client.
+ - in order to have the above functionality the new keyword `class` replaced the `type` one. With `class` the OOP feature *polymorphism* is introduced. 
+ - since the bound-procedure **area** was defined as a function it cannot be called by itself, it can only appear as **rhs** object, that is why it is used like `x = sq%area()`. The 'stand-alone' functionality is covered by a subroutine, and the above example should be modified like:
+
+ ```fortran
+ ! change within module
+ contains
+    subroutine area(self, x)
+        class(t_square), intent(in)     :: self
+        real,            intent(in out) :: x
+        x = self%side * self%side
+    end subroutine
+
+! change within main program
+call sq%area(x)
+! do stuff with x...
+ ```
+ In this case there are two arguments in definition, one similar as before the **self** of type `t_square` and the second one a real variable **x** that should be assigned the calculated area and returned back for further use. 
\ No newline at end of file