Merge pull request #1399 from zapbot/update-site-content

psiinon · web-flow · commit b5760e11a9b2 · 2024-03-20T12:21:30.000Z
Update site content
diff --git a/blog/2024-03-13-zap-funding-and-the-open-source-fellowship/index.html b/blog/2024-03-13-zap-funding-and-the-open-source-fellowship/index.html
@@ -175,7 +175,7 @@ <h2 id="the-open-source-fellowship">The Open Source Fellowship <a class="header-
 <p>The sponsorship does not change anything to do with the governance of the project - the ZAP Core Team remains completely in control of the project, our roadmap and all of the Intellectual Property.</p>
 
 <h5 id="this-is-an-amazing-investment-in-zap-and-one-that-saves-the-zap-project-from-potential-closure">This is an amazing investment in ZAP and one that saves the ZAP project from potential closure.</h5>
-<p>For more details see <a href="https://crashoverride.com/open-source?zap=web">https://crashoverride.com/open-source?zap=web</a></p>
+<p>For more details see <a href="https://crashoverride.com/open-source?zap=web">https://crashoverride.com/open-source</a></p>
 
 <h2 id="helping-zap-thrive">Helping ZAP Thrive <a class="header-link" href="#helping-zap-thrive"><svg class="fill-current o-60 hover-accent-color-light" height="22px" viewBox="0 0 24 24" width="22px" xmlns="http://www.w3.org/2000/svg"><path d="M0 0h24v24H0z" fill="none"/><path d="M3.9 12c0-1.71 1.39-3.1 3.1-3.1h4V7H7c-2.76 0-5 2.24-5 5s2.24 5 5 5h4v-1.9H7c-1.71 0-3.1-1.39-3.1-3.1zM8 13h8v-2H8v2zm9-6h-4v1.9h4c1.71 0 3.1 1.39 3.1 3.1s-1.39 3.1-3.1 3.1h-4V17h4c2.76 0 5-2.24 5-5s-2.24-5-5-5z" fill="currentColor"/></svg></a></h2>
 <p>While the Crash Override Open Source Fellowship support means that ZAP can survive, we still need to find a long term independent and scalable funding model in order for ZAP to thrive.</p>
diff --git a/search/index.json b/search/index.json
@@ -3013,7 +3013,7 @@
     "keywords": ["and","blog","fellowship","funding","open","source","the","zap"],
     "tags": ["blog","funding"],
     "summary": "ZAP is now supported by the Crash Override Open Source Fellowship!",
-    "content": "background you may aware zap left owasp join new software security project basis that linux foundation would able secure funding core development unfortunately proposed has been withdrawn result will longer joining note still going ahead not part lf complex ambitious commercial companies maintain projects equivalent have hundreds people working them possible ones spare time matter how many volunteer believe full really minimum we need order enough thrive over last few years struggled get main achieved proved reliable open source fellowship withdrawal did put very precarious position however am delighted announce now sponsored by crash override means both myself ricardo spend 80 our next only remaining 20 spent other developments some which directly benefit sponsorship does change anything do governance team remains completely control roadmap all intellectual property amazing investment one saves from potential closure more details see https:crashoverridecomopensourcezapweb helping while support can survive find long term independent scalable model grown small become what probably worlds most popular web scanner initially hoped made useful then those who donate money allow us grow sadly case pay work continue provide real value sources income ideally recurring rather than oneoffs investigating options raise summarised below like stress whole purpose here fund non profit entity looking rich investigated lot detailed including summary their pros cons donations traditionally raised via previously managed these were course welcome anywhere near sustain positives additional cost negatives unlikely much way typically conclusion: accepting stage relied my since 2012 explained above anyone else started similar large grants theory could good experience applying understand they difficult consuming apply positives: potentially significant funds negatives: hard take away doing pursuing contracts asked feedback option recently twitter linkedin poll results there appear interested looks require such consider using revenue impact free introducing plan past accepted implement specific benefits accelerate features paid already want faster sporadic accept consultancy various touch asking up until except know desire available licensing number use online services permitted apache v2 licence under majority code base released smaller supporting larger either never supported done making amount relicense something seriously considering raising forks customers sell based definite possibility training outsourced initial unclear demand providing saas ongoing compete buy licences closed close happened original paros proxy cannot make try different another keep add especially appeal scale doesnt first thing offering professional including: expect fast takeup give confidence had interest within months start planning addition page dual second being oss currently gnu agpl likely encourage purchase danger just update relicensed version choose own fork go down route charge sliding company size expensive significantly less maintaining enhancing themselves noted minimal after associated changes least publish blog post into depth meantime your asap relicencing codebase cause problems user group thread email "
+    "content": "background you may aware zap left owasp join new software security project basis that linux foundation would able secure funding core development unfortunately proposed has been withdrawn result will longer joining note still going ahead not part lf complex ambitious commercial companies maintain projects equivalent have hundreds people working them possible ones spare time matter how many volunteer believe full really minimum we need order enough thrive over last few years struggled get main achieved proved reliable open source fellowship withdrawal did put very precarious position however am delighted announce now sponsored by crash override means both myself ricardo spend 80 our next only remaining 20 spent other developments some which directly benefit sponsorship does change anything do governance team remains completely control roadmap all intellectual property amazing investment one saves from potential closure more details see https:crashoverridecomopensource helping while support can survive find long term independent scalable model grown small become what probably worlds most popular web scanner initially hoped made useful then those who donate money allow us grow sadly case pay work continue provide real value sources income ideally recurring rather than oneoffs investigating options raise summarised below like stress whole purpose here fund non profit entity looking rich investigated lot detailed including summary their pros cons donations traditionally raised via previously managed these were course welcome anywhere near sustain positives additional cost negatives unlikely much way typically conclusion: accepting stage relied my since 2012 explained above anyone else started similar large grants theory could good experience applying understand they difficult consuming apply positives: potentially significant funds negatives: hard take away doing pursuing contracts asked feedback option recently twitter linkedin poll results there appear interested looks require such consider using revenue impact free introducing plan past accepted implement specific benefits accelerate features paid already want faster sporadic accept consultancy various touch asking up until except know desire available licensing number use online services permitted apache v2 licence under majority code base released smaller supporting larger either never supported done making amount relicense something seriously considering raising forks customers sell based definite possibility training outsourced initial unclear demand providing saas ongoing compete buy licences closed close happened original paros proxy cannot make try different another keep add especially appeal scale doesnt first thing offering professional including: expect fast takeup give confidence had interest within months start planning addition page dual second being oss currently gnu agpl likely encourage purchase danger just update relicensed version choose own fork go down route charge sliding company size expensive significantly less maintaining enhancing themselves noted minimal after associated changes least publish blog post into depth meantime your asap relicencing codebase cause problems user group thread email "
     },
 {
     "url": "/blog/2024-03-11-user-personas-poll-results/",

Original file line number	Diff line number	Diff line change
`@@ -3013,7 +3013,7 @@`
`3013`	`3013`	`"keywords": ["and","blog","fellowship","funding","open","source","the","zap"],`
`3014`	`3014`	`"tags": ["blog","funding"],`
`3015`	`3015`	`"summary": "ZAP is now supported by the Crash Override Open Source Fellowship!",`
`3016`		- "content": "background you may aware zap left owasp join new software security project basis that linux foundation would able secure funding core development unfortunately proposed has been withdrawn result will longer joining note still going ahead not part lf complex ambitious commercial companies maintain projects equivalent have hundreds people working them possible ones spare time matter how many volunteer believe full really minimum we need order enough thrive over last few years struggled get main achieved proved reliable open source fellowship withdrawal did put very precarious position however am delighted announce now sponsored by crash override means both myself ricardo spend 80 our next only remaining 20 spent other developments some which directly benefit sponsorship does change anything do governance team remains completely control roadmap all intellectual property amazing investment one saves from potential closure more details see https:crashoverridecomopensourcezapweb helping while support can survive find long term independent scalable model grown small become what probably worlds most popular web scanner initially hoped made useful then those who donate money allow us grow sadly case pay work continue provide real value sources income ideally recurring rather than oneoffs investigating options raise summarised below like stress whole purpose here fund non profit entity looking rich investigated lot detailed including summary their pros cons donations traditionally raised via previously managed these were course welcome anywhere near sustain positives additional cost negatives unlikely much way typically conclusion: accepting stage relied my since 2012 explained above anyone else started similar large grants theory could good experience applying understand they difficult consuming apply positives: potentially significant funds negatives: hard take away doing pursuing contracts asked feedback option recently twitter linkedin poll results there appear interested looks require such consider using revenue impact free introducing plan past accepted implement specific benefits accelerate features paid already want faster sporadic accept consultancy various touch asking up until except know desire available licensing number use online services permitted apache v2 licence under majority code base released smaller supporting larger either never supported done making amount relicense something seriously considering raising forks customers sell based definite possibility training outsourced initial unclear demand providing saas ongoing compete buy licences closed close happened original paros proxy cannot make try different another keep add especially appeal scale doesnt first thing offering professional including: expect fast takeup give confidence had interest within months start planning addition page dual second being oss currently gnu agpl likely encourage purchase danger just update relicensed version choose own fork go down route charge sliding company size expensive significantly less maintaining enhancing themselves noted minimal after associated changes least publish blog post into depth meantime your asap relicencing codebase cause problems user group thread email "
	`3016`	+ "content": "background you may aware zap left owasp join new software security project basis that linux foundation would able secure funding core development unfortunately proposed has been withdrawn result will longer joining note still going ahead not part lf complex ambitious commercial companies maintain projects equivalent have hundreds people working them possible ones spare time matter how many volunteer believe full really minimum we need order enough thrive over last few years struggled get main achieved proved reliable open source fellowship withdrawal did put very precarious position however am delighted announce now sponsored by crash override means both myself ricardo spend 80 our next only remaining 20 spent other developments some which directly benefit sponsorship does change anything do governance team remains completely control roadmap all intellectual property amazing investment one saves from potential closure more details see https:crashoverridecomopensource helping while support can survive find long term independent scalable model grown small become what probably worlds most popular web scanner initially hoped made useful then those who donate money allow us grow sadly case pay work continue provide real value sources income ideally recurring rather than oneoffs investigating options raise summarised below like stress whole purpose here fund non profit entity looking rich investigated lot detailed including summary their pros cons donations traditionally raised via previously managed these were course welcome anywhere near sustain positives additional cost negatives unlikely much way typically conclusion: accepting stage relied my since 2012 explained above anyone else started similar large grants theory could good experience applying understand they difficult consuming apply positives: potentially significant funds negatives: hard take away doing pursuing contracts asked feedback option recently twitter linkedin poll results there appear interested looks require such consider using revenue impact free introducing plan past accepted implement specific benefits accelerate features paid already want faster sporadic accept consultancy various touch asking up until except know desire available licensing number use online services permitted apache v2 licence under majority code base released smaller supporting larger either never supported done making amount relicense something seriously considering raising forks customers sell based definite possibility training outsourced initial unclear demand providing saas ongoing compete buy licences closed close happened original paros proxy cannot make try different another keep add especially appeal scale doesnt first thing offering professional including: expect fast takeup give confidence had interest within months start planning addition page dual second being oss currently gnu agpl likely encourage purchase danger just update relicensed version choose own fork go down route charge sliding company size expensive significantly less maintaining enhancing themselves noted minimal after associated changes least publish blog post into depth meantime your asap relicencing codebase cause problems user group thread email "
`3017`	`3017`	`},`
`3018`	`3018`	`{`
`3019`	`3019`	`"url": "/blog/2024-03-11-user-personas-poll-results/",`