Ajsutement accueil + article

src/articles-index.md

@@ -7,7 +7,6 @@ menutitle: Articles
 class: articles
 order: 2
 heading: We explain.
-chapeau:
+chapeau: This is where the articles will be
 ---
 
-This is where the articles will be
\ No newline at end of file

src/articles/entry1.md

+---
+title: "Announcement: Women in Tech Collectives and Coko form Partnership" 
+date: 
+intro: Coko and the Women in Tech Collectives are proud to announce a new partnership! The Women in Tech Collectives from India is a small community led by women tech enthusiasts…
+author: Adam Hyde
+tags: featured
+class: 
+icon: "/images/uploads/wit.jpg"
+---
+
+![wit](wit.jpg)
+
+Coko and the Women in Tech Collectives are proud to announce a new partnership!
+
+The Women in Tech Collectives from India is a small community led by women tech enthusiasts from a small rural region in South India. The community helps in addressing the needs of employment and education for women and marginalized communities in this most needful time and supporting them to pursue careers in varied technology fields.
+
+The members from the community usually come from rural regions and they are usually the first graduates in their families, and their access to the digital world is very limited. Also, many women in the community also face a lot of gender bias in accessing technology and in pursuing their career in Information and Communication Technologies. Their employment circumstances have also been severely (negatively) effected by COVID.
+
+The Women In Tech collectives, India is a Self Help community which was initiated by [Bhuvana Meenakshi Koteeswaran](https://www.linkedin.com/in/bhuvana-meenakshi-koteeswaran-a67b58103) in March 2021 when a team of technology geeks, mostly women from these rural regions, reported about their sudden unemployment issues in the course of the pandemic. They were working for some local companies in the region as their families never allowed them to travel far to work. This community had to face social stigma to pursue their careers in tech and also continue their education on computers. Many women anonymously reported their concerns, because their families depended on their salaries, and staying at home increased their daily chores, so they were in need of some kind of job that can satisfy their daily essentials and medical emergencies. That’s when we formed the team and started to send word by mouth and WhatsApp messages to gather around those who are facing these issues.
+
+In June of 2021 Bhuvana approached Coko Founder Adam Hyde about possible collaborations which have lead to a new partnership. Coko has employed four of the WiTc to work on open source publishing projects including Kotahi and Editoria.
+
+> ”_I am very grateful about the partnership with Coko! I see this as a win-win state. It’s an amazing opportunity for our diverse community to get a global exposure which they have never experienced before. Thanks to Adam and his team for accommodating our community members so well and I look forward to sustaining this association for more years to come._” – Bhuvana Meenakshi, Founder of WITc, India
+
+Coko Founder Adam Hyde is also very happy about this collaboration – “Bhuvana and the WITc are awesome! We have welcomed 4 people from the collective into our team so far and looking to work with more within a few weeks. Everyone has been extremely nice, hard working, and enthusiastic about what we do. “
+
+Coko is also supporting these four team members to work during the week on other WiTc projects to assist the community. Additionally Bhuvana has joined the judging panel of the Open Publishing Awards and Adam and Bhuvana have more exciting ideas for WItC and Coko collaborations in the pipeline to announce! Stay tuned!
\ No newline at end of file

src/articles/entry2.md

+---
+title: "Single Source Publishing and JATS" 
+date: "2021-11-27"
+intro: In general, Journals (and many of the family of workflows associated with publishing research) require 3 output types – HTML, PDF, and JATS. Along with finding reviewers, this requirement for…
+author: Adam Hyde
+tags: featured
+class: 
+icon: "/images/uploads/kotahi-jats-V2-500x500.jpg"
+---
+
+In general, Journals (and many of the family of workflows associated with publishing research) require 3 output types – HTML, PDF, and JATS.
+
+Along with finding reviewers, this requirement for document preparation (generally called typesetting) is one of the big publishing bottlenecks. The tooling and processes for typesetting can be complex so it is also difficult for Journal staff to do this themselves. The result is that many ‘throw it over the wall’ to an outsourced vendor. This incurs costs which may or may not be affordable for the Journal. The back and forth with vendors also prolongs the time to publish. In addition, conversion costs are added to the total cost of production and passed along, sooner or later, to subscribing institutions (such as universities), funders, or the researchers (in the case of Open Access via Article Processing Charges).
+
+So, there is a lot to be gained by solving this problem. Solve this problem and research can be shared sooner, and the cost of publication can be significantly lowered. The impact of typesetting on the speed and cost of publication is under-discussed – perhaps because it is a rather specialist domain and has been, for some time, difficult to explain and, frankly, if you are not into document conversion the whole thing can feel rather difficult to grasp, and perhaps also rather boring.
+
+Yet meeting this requirement is a real and significant problem for the speed and cost of publication of research.
+
+At Coko we have been working on this matter for some time (5 years +). We have built several tools that help us along this way – namely [XSweet](https://xsweet.org/ "xsweet.org"), [Wax](https://waxjs.net/ "waxjs.net"), and [Pagedjs](https://www.pagedjs.org/ "www.pagedjs.org"). These technologies put easy- to-use tools in the hands of Journal staff to produce HTML and (beautiful) PDF at (almost) the press of a button.
+
+However, outputting HTML and PDF is not enough if you cannot also output JATS. If you can’t output JATS, the journal staff still have to solve this problem, and if it means sending the content to a vendor to do so, then, dependent on the workflow of the vendor, you might as well ask them to produce all three document types. More often than not, it doesn’t make sense to _just_ do JATS.
+
+So, finally (finally!) Coko has been working on an easy-to-use tool to produce JATS at (almost!) the press of a button. This is our newly released WAX-JATS editor.
+
+![Wax-JATS integrated into Kotahi](/images/upload/screenshot-2021-11-05-at-11.53.21-700x344.png)
+
+The WAX-JATS editor (pictured above) is currently integrated into Kotahi and is very easy to use. No specialist JATS knowledge is required.
+
+The following short series of articles will look at the problem, some of the previous solutions, and discuss how the new WAX-JATS software addresses this issue.
+

src/blog/posts/entry2.md

@@ -3,7 +3,7 @@ title: Scaling Coko
 date: 2021-12-10
 author: 
 intro: Some thoughts on our next phase.
-class: wide
+class: 
 tags: featured
 image: ""
 video: "/images/uploads/Scaling-Coko.mp4"

src/layouts/articles-index.njk

@@ -2,32 +2,20 @@
 
 {% block content %}
    
-     {% for item in collections.articles -%}
-            <article class="item">
-                <header>
-                    <p class="meta">
-                        <time datetime="{{item.date}}">{{item.data.date | itemDate}}</time>
-                        <span class="tags">
-                            {% for tag in tags %}
-                                <span>#{{tag}}</span>
-                            {% endfor %}
-                        </div>
-                    </span>
-                    <h2 id="{{item.data.title | slug}}">{{item.data.title}}</h2>
-                    {% if item.data.author %}
-                        <p class="author">Written by {{ item.data.author }}</p>
-                    {% endif %}
+    {{content | safe}}
+    
+    {% for item in collections.articles -%}
+            <div class="posts grid-item {{item.data.class}}">
+                <p class="meta">
+                    <time datetime="{{item.date}}">{{item.data.date}}</time>
+                    <span>#{{item.data.tags}}</span>
+                </p>
+                <figure><a href="{{item.url}}">
+                    <img src="{{item.data.icon}}" alt="{{item.data.title}}"></a>
+                </figure>
+                <h3 id="{{item.data.title | slug}}"><a href="{{item.url}}">{{item.data.title}}</a></h3>
+                {{ item.data.intro | safe }}
+            </div>
+    {%- endfor %}
 
-                </header>
-
+{% endblock %} 
\ No newline at end of file
-                <section class="content">
-
-                    <section>
-                        {{ item.data.content | safe }}
-                    </section>
-                </section>
-            </article>
-        {%- endfor %}
-
-    </main>
-{% endblock %}
\ No newline at end of file

src/layouts/article.njk → src/layouts/articles.njk

 {% extends "base.njk" %}
 
-{% block bodyclass %}article{% endblock %}
+{% block bodyclass %}articles{% endblock %}
 
 {% block content %}
-
-    <main>
-        {# <header>
+     {% block header %}
+      {% endblock %}
+        
+        <header>
             <h1>{{title}}</h1>
-        </header> #}
+        </header>
 
         <article class="post-content">
-            <header>
-                <h1>{{title}}</h1>
+            <p class="meta">
                 <time>{{date | postDate}}</time>
-                {% if intro %}
-                    <section class="intro">{{intro | markdownify | safe }}</section>
-                {% endif %}
-            </header>
-
+                <span>#{{tags}}</span>
+            </p>
+            
             <section class="content">
                 {{ content | safe }}
             </section>
         </article>
+
         {% set previousPost = collections.articles | getPreviousCollectionItem(page) %}
         {% set nextPost = collections.articles | getNextCollectionItem(page) %}
 

src/layouts/blog-index.njk

@@ -3,7 +3,7 @@
 {% block content %}
 
     <div class="grid">
-      {% for post in collections.blog -%}
+      {% for post in collections.blog | reverse -%}
           <div class="posts grid-item {{post.data.class}}">
                   <p class="meta">
                     <time datetime="{{post.date}}">{{post.data.date | postDate}}</time>

src/layouts/home.njk

@@ -20,23 +20,24 @@
     <section class="section-blog">
         <h2 class="section-title">latest news</h2>
 
-        {% for article in collections.blog %}
-
-            <div class="posts">
-                <p class="meta">
-                        <time datetime="{{article.date}}">{{article.data.date | postDate}}</time>
-                        <span>#{{article.data.tags}}</span>
-                </p>
-                <figure><a href="{{article.url}}">
-                    <img src="{{article.data.icon}}" alt="{{article.data.title}}"></a>
-                </figure>
-                <h3><a href="{{article.url}}">{{article.data.title}}</a></h3>
-                {% if article.data.intro %}
-                {{article.data.intro | markdownify | safe }}
-                {% endif %}
+        {% for article in collections.blog | reverse %}
+         {% if loop.index0 < 2 %} 
+                <div class="posts">
+                    <p class="meta">
+                            <time datetime="{{article.date}}">{{article.data.date | postDate}}</time>
+                            <span>#{{article.data.tags}}</span>
+                    </p>
+                    <figure><a href="{{article.url}}">
+                        <img src="{{article.data.icon}}" alt="{{article.data.title}}"></a>
+                    </figure>
+                    <h3><a href="{{article.url}}">{{article.data.title}}</a></h3>
+                    {% if article.data.intro %}
+                    {{article.data.intro | markdownify | safe }}
+                    {% endif %}
 
                 {# {{article.templateContent | markdownify | safe}} #}
-            </div>
+                </div>
+         {% endif %}
         {% endfor %}
 
     </section>

static/css/theme-coko/main.css

@@ -219,6 +219,16 @@ a:hover {
   .grid-item.wide{
     grid-column: span 2;;
   }
+  .posts figure  {
+    height: 250px;
+    margin: 1em auto;
+    object-fit: cover;  
+    width: 100%;
+  }
+  .posts figure img {
+    height: 100%;
+    margin: auto;
+  }
 
   article {
     grid-column: 1/end;
@@ -289,14 +299,21 @@ a:hover {
     width: 100%;
     max-height: 500px;
   }
- /* NEWS ------------------ */
+ /* NEWS & ARTICLES ------------------ */
  .news .grid {
    margin-top: 0px;
  }
- .news .grid-item {
-  border-top: 1px solid var(--color-primary);
-  padding-top: 10px;
+  .news .grid-item,
+  .articles .grid-item {
+    border-top: 1px solid var(--color-primary);
+    padding-top: 10px;
 }
+  .articles main {
+    column-gap: 40px;
+  }
+  .articles .grid-item {
+    grid-column: span 2;
+  }
   /* PRODUCT --------------------*/
     ul.filter {
     grid-column: 1/end;
@@ -486,7 +503,7 @@ footer section.infos a:hover {
   @media screen and (max-width: 800px)  {
     header { margin-bottom: 2em;}
     .grid { grid-template-columns: repeat(2, 1fr); }
-    .home section.section-blog .posts { grid-column: 1/end; margin-bottom: 2em;}
+    .home section.section-blog .posts, .articles .grid-item { grid-column: 1/end; margin-bottom: 2em;}
   }
   @media screen and (max-width: 650px)  {
     footer {flex-direction: column;}