This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/cordova-docs.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 3f340558f1 Deploying to asf-site from @ 
apache/cordova-docs@42d4730cba7ab1e183c64a25a60e77478a39cc77 🚀
3f340558f1 is described below

commit 3f340558f1db173e849e41dce6e92a9385179030
Author: NiklasMerz <niklasm...@linux.com>
AuthorDate: Fri Jan 12 12:32:07 2024 +0000

    Deploying to asf-site from @ 
apache/cordova-docs@42d4730cba7ab1e183c64a25a60e77478a39cc77 🚀
---
 announcements/2024/01/12/survey-results.html |  8 ++++----
 blog/index.html                              |  8 ++++----
 feed.xml                                     | 12 ++++++------
 3 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/announcements/2024/01/12/survey-results.html 
b/announcements/2024/01/12/survey-results.html
index ca668833ef..8c15129f39 100644
--- a/announcements/2024/01/12/survey-results.html
+++ b/announcements/2024/01/12/survey-results.html
@@ -145,7 +145,7 @@
 
 <p>Obviously almost all respondents work with Cordova and the most used 
platforms are <strong>Android (97.4%), iOS (89%)</strong>, Browser (21.1%) and 
Electron (7%). Windows and macOS Catalyst got only a handful of responses in 
total.</p>
 
-<p><img src="/static/img/blog/2024/survey/image7.png" alt="Chart platforms" 
/></p>
+<p><img src="/static/img/blog/2024/survey/image7.png" style="width: 100%;" 
alt="Chart platforms" /></p>
 
 <blockquote>
   <p>Build apps with access to native features not yet present in the web 
platform</p>
@@ -161,7 +161,7 @@
 
 <p>Cordova&#39;s unofficial goal has always been to cease to exist once the 
Web catches up with supporting new APIs and features similar to native. 
Therefore, it&#39;s good news that a small number of users (6.1%) migrated 
their apps to <strong>PWAs</strong>. About 13% migrated to 
<strong>Capacitor</strong> and 3% to Flutter and React-Native each. About 2% of 
projects moved to Electron or fully native. Around 4% are thinking about or are 
in the process of migrating.</p>
 
-<p><img src="/static/img/blog/2024/survey/image2.png" alt="Chart migrating" 
/></p>
+<p><img src="/static/img/blog/2024/survey/image2.png" style="width: 100%;" 
alt="Chart migrating" /></p>
 
 <p><strong>Only 23.2% of respondents have migrated apps to alternative 
solutions.</strong></p>
 
@@ -173,7 +173,7 @@
 
 <p>The answers to the question &quot;What&#39;s holding you back from 
contributing?&quot; are probably pretty typical for open source projects. The 
biggest factors are time (53%) and work-life-balance (37%). The second most 
mentioned reasons <strong>I need help getting started</strong> (21%) and 
<strong>Imposter Syndrome</strong> (10%) we should address with better 
documentation and support for first contributors.</p>
 
-<p><img src="/static/img/blog/2024/survey/image1.png" alt="Chart contributing" 
/></p>
+<p><img src="/static/img/blog/2024/survey/image1.png" style="width: 100%;" 
alt="Chart contributing" /></p>
 
 <p>For those who are interested in contributing to Apache Cordova, the best 
way is to submit PR. It could be to fix a known issue that you might have or 
others have reported, or submitting new features. In terms of Work-Life 
balance, Apache Cordova is based on volunteering. There is no requirement in 
dedicating time every day. Usually some might work on Cordova for a few minutes 
when they can spare.</p>
 
@@ -181,7 +181,7 @@
 
 <p>We also included a question about <strong>release voting</strong> because 
we think that most users don&#39;t know how the release process at Apache 
works. For every release we need at least 3 members of the PMC to check and 
cast a positive vote on the release. Persons who are not part of the PMC can 
vote as well and help test the release. The voting and decision process for 
releases happens on the mailing list. Sometimes it can take a while to finally 
publish a release because 3 PMC m [...]
 
-<p><img src="/static/img/blog/2024/survey/image4.png" alt="Chart voting" /></p>
+<p><img src="/static/img/blog/2024/survey/image4.png" style="width: 100%;" 
alt="Chart voting" /></p>
 
 <h2>Areas of improvement</h2>
 
diff --git a/blog/index.html b/blog/index.html
index 9778cabe7e..1422b8978d 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -154,7 +154,7 @@
 
 <p>Obviously almost all respondents work with Cordova and the most used 
platforms are <strong>Android (97.4%), iOS (89%)</strong>, Browser (21.1%) and 
Electron (7%). Windows and macOS Catalyst got only a handful of responses in 
total.</p>
 
-<p><img src="/static/img/blog/2024/survey/image7.png" alt="Chart platforms" 
/></p>
+<p><img src="/static/img/blog/2024/survey/image7.png" style="width: 100%;" 
alt="Chart platforms" /></p>
 
 <blockquote>
   <p>Build apps with access to native features not yet present in the web 
platform</p>
@@ -170,7 +170,7 @@
 
 <p>Cordova&#39;s unofficial goal has always been to cease to exist once the 
Web catches up with supporting new APIs and features similar to native. 
Therefore, it&#39;s good news that a small number of users (6.1%) migrated 
their apps to <strong>PWAs</strong>. About 13% migrated to 
<strong>Capacitor</strong> and 3% to Flutter and React-Native each. About 2% of 
projects moved to Electron or fully native. Around 4% are thinking about or are 
in the process of migrating.</p>
 
-<p><img src="/static/img/blog/2024/survey/image2.png" alt="Chart migrating" 
/></p>
+<p><img src="/static/img/blog/2024/survey/image2.png" style="width: 100%;" 
alt="Chart migrating" /></p>
 
 <p><strong>Only 23.2% of respondents have migrated apps to alternative 
solutions.</strong></p>
 
@@ -182,7 +182,7 @@
 
 <p>The answers to the question &quot;What&#39;s holding you back from 
contributing?&quot; are probably pretty typical for open source projects. The 
biggest factors are time (53%) and work-life-balance (37%). The second most 
mentioned reasons <strong>I need help getting started</strong> (21%) and 
<strong>Imposter Syndrome</strong> (10%) we should address with better 
documentation and support for first contributors.</p>
 
-<p><img src="/static/img/blog/2024/survey/image1.png" alt="Chart contributing" 
/></p>
+<p><img src="/static/img/blog/2024/survey/image1.png" style="width: 100%;" 
alt="Chart contributing" /></p>
 
 <p>For those who are interested in contributing to Apache Cordova, the best 
way is to submit PR. It could be to fix a known issue that you might have or 
others have reported, or submitting new features. In terms of Work-Life 
balance, Apache Cordova is based on volunteering. There is no requirement in 
dedicating time every day. Usually some might work on Cordova for a few minutes 
when they can spare.</p>
 
@@ -190,7 +190,7 @@
 
 <p>We also included a question about <strong>release voting</strong> because 
we think that most users don&#39;t know how the release process at Apache 
works. For every release we need at least 3 members of the PMC to check and 
cast a positive vote on the release. Persons who are not part of the PMC can 
vote as well and help test the release. The voting and decision process for 
releases happens on the mailing list. Sometimes it can take a while to finally 
publish a release because 3 PMC m [...]
 
-<p><img src="/static/img/blog/2024/survey/image4.png" alt="Chart voting" /></p>
+<p><img src="/static/img/blog/2024/survey/image4.png" style="width: 100%;" 
alt="Chart voting" /></p>
 
 <h2>Areas of improvement</h2>
 
diff --git a/feed.xml b/feed.xml
index 493ab89ad0..67c950dd10 100644
--- a/feed.xml
+++ b/feed.xml
@@ -6,8 +6,8 @@
 </description>
     <link>https://cordova.apache.org/</link>
     <atom:link href="https://cordova.apache.org/feed.xml"; rel="self" 
type="application/rss+xml"/>
-    <pubDate>Fri, 12 Jan 2024 11:34:59 +0000</pubDate>
-    <lastBuildDate>Fri, 12 Jan 2024 11:34:59 +0000</lastBuildDate>
+    <pubDate>Fri, 12 Jan 2024 12:31:06 +0000</pubDate>
+    <lastBuildDate>Fri, 12 Jan 2024 12:31:06 +0000</lastBuildDate>
     <generator>Jekyll v4.3.3</generator>
     
       <item>
@@ -18,7 +18,7 @@
 
 &lt;p&gt;Obviously almost all respondents work with Cordova and the most used 
platforms are &lt;strong&gt;Android (97.4%), iOS (89%)&lt;/strong&gt;, Browser 
(21.1%) and Electron (7%). Windows and macOS Catalyst got only a handful of 
responses in total.&lt;/p&gt;
 
-&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image7.png&quot; 
alt=&quot;Chart platforms&quot; /&gt;&lt;/p&gt;
+&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image7.png&quot; 
style=&quot;width: 100%;&quot; alt=&quot;Chart platforms&quot; /&gt;&lt;/p&gt;
 
 &lt;blockquote&gt;
   &lt;p&gt;Build apps with access to native features not yet present in the 
web platform&lt;/p&gt;
@@ -34,7 +34,7 @@
 
 &lt;p&gt;Cordova&amp;#39;s unofficial goal has always been to cease to exist 
once the Web catches up with supporting new APIs and features similar to 
native. Therefore, it&amp;#39;s good news that a small number of users (6.1%) 
migrated their apps to &lt;strong&gt;PWAs&lt;/strong&gt;. About 13% migrated to 
&lt;strong&gt;Capacitor&lt;/strong&gt; and 3% to Flutter and React-Native each. 
About 2% of projects moved to Electron or fully native. Around 4% are thinking 
about or are in the proce [...]
 
-&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image2.png&quot; 
alt=&quot;Chart migrating&quot; /&gt;&lt;/p&gt;
+&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image2.png&quot; 
style=&quot;width: 100%;&quot; alt=&quot;Chart migrating&quot; /&gt;&lt;/p&gt;
 
 &lt;p&gt;&lt;strong&gt;Only 23.2% of respondents have migrated apps to 
alternative solutions.&lt;/strong&gt;&lt;/p&gt;
 
@@ -46,7 +46,7 @@
 
 &lt;p&gt;The answers to the question &amp;quot;What&amp;#39;s holding you back 
from contributing?&amp;quot; are probably pretty typical for open source 
projects. The biggest factors are time (53%) and work-life-balance (37%). The 
second most mentioned reasons &lt;strong&gt;I need help getting 
started&lt;/strong&gt; (21%) and &lt;strong&gt;Imposter Syndrome&lt;/strong&gt; 
(10%) we should address with better documentation and support for first 
contributors.&lt;/p&gt;
 
-&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image1.png&quot; 
alt=&quot;Chart contributing&quot; /&gt;&lt;/p&gt;
+&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image1.png&quot; 
style=&quot;width: 100%;&quot; alt=&quot;Chart contributing&quot; 
/&gt;&lt;/p&gt;
 
 &lt;p&gt;For those who are interested in contributing to Apache Cordova, the 
best way is to submit PR. It could be to fix a known issue that you might have 
or others have reported, or submitting new features. In terms of Work-Life 
balance, Apache Cordova is based on volunteering. There is no requirement in 
dedicating time every day. Usually some might work on Cordova for a few minutes 
when they can spare.&lt;/p&gt;
 
@@ -54,7 +54,7 @@
 
 &lt;p&gt;We also included a question about &lt;strong&gt;release 
voting&lt;/strong&gt; because we think that most users don&amp;#39;t know how 
the release process at Apache works. For every release we need at least 3 
members of the PMC to check and cast a positive vote on the release. Persons 
who are not part of the PMC can vote as well and help test the release. The 
voting and decision process for releases happens on the mailing list. Sometimes 
it can take a while to finally publish a r [...]
 
-&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image4.png&quot; 
alt=&quot;Chart voting&quot; /&gt;&lt;/p&gt;
+&lt;p&gt;&lt;img src=&quot;/static/img/blog/2024/survey/image4.png&quot; 
style=&quot;width: 100%;&quot; alt=&quot;Chart voting&quot; /&gt;&lt;/p&gt;
 
 &lt;h2&gt;Areas of improvement&lt;/h2&gt;
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cordova.apache.org
For additional commands, e-mail: commits-h...@cordova.apache.org

Reply via email to