[Valid RSS] This is a valid RSS feed.


This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.


  1. <?xml version="1.0" encoding="utf-8" ?>
  2. <rss version="2.0">
  3. <channel>
  4. <title>FlatPress</title>
  5. <link></link>
  6. <description><![CDATA[]]></description>
  7. <copyright>Copyright 2006, Arvid</copyright>
  8. <managingEditor>[email protected]</managingEditor>
  9. <language>en-us</language>
  11. <generator>FlatPress</generator>
  12. <item>
  13. <title>Enjoy the holidays!</title>
  14. <link></link>
  15. <description><![CDATA[ <p>Hey all you FlatPressers out there,</p>
  16. <p>I wish you all great holidays with your family, friends and beloved ones. If you have the chance, use this special time of the year to take care of people in need, share love with those who deserve it, or just have a good time with folks you really like. And of course, have a great start into the upcoming new year - it may be a successful one for all of you.</p>
  17. <p>As for FlatPress, 2019 is hopefully going to bring the project to new life. There is still plenty of work, but: The first steps are done!</p>
  18. <p>Thanks for all the support I already got on my mission to revive FlatPress - and still continue to get. It&#8217;s very encouraging to see you appreciate my efforts. There are still a few things to be done until the project is finally transferred and the new version can be released. Stay tuned and drop by once in a while to get the latest news!</p>
  19. <p>All the best<br />
  20. Arvid
  21. </p>
  22. ]]></description>
  23. <category>General </category> <guid isPermaLink="true"></guid>
  25. <author>Arvid [email protected]</author>
  26. <pubDate>Sat, 08 Dec 2018 12:27:33 -0500</pubDate>
  27. <comments></comments>
  28. </item>
  29. <item>
  30. <title>FlatPress is now on Twitter</title>
  31. <link></link>
  32. <description><![CDATA[ <p><a href=""><img src="./fp-content/images/twitterlogo.png" style="width:90px;float:left;margin-right:1em;" title="@FlatPress on Twitter"></a>As you may have noticed, there are a lot of changes going on in the FlatPress project currently. Besides the project blog you&#8217;re reading (and its <a href="">RSS feed</a>), there is now another way to stay up-to-date: <strong>FlatPress is on Twitter!</strong> </p>
  33. <p>Feel free to follow <a href="">@FlatPress</a> - and please spread the word!</p>
  34. <p><br><br><br />
  35. <em>(A big &#8220;Thank you&#8221; goes to <a href="">Julian Rademacher</a> for his generous support on this topic!)</em>
  36. </p>
  37. ]]></description>
  38. <category>News, Project interna </category> <guid isPermaLink="true"></guid>
  40. <author>Arvid [email protected]</author>
  41. <pubDate>Sun, 18 Nov 2018 08:56:30 -0500</pubDate>
  42. <comments></comments>
  43. </item>
  44. <item>
  45. <title>Currently no registration possible on the forums</title>
  46. <link></link>
  47. <description><![CDATA[ <p>I wondered why it is so quiet on the <a href="">forums</a> lately. Turns out, registration is broken&#8230; -.-<br />
  48. But fear not, I work on it!</p>
  49. <p>So for now, if you have questions about FlatPress or want to contact me, please use the comments here in the blog or just <a href="mailto:[email protected]">mail me</a>.
  50. </p>
  51. ]]></description>
  52. <category>General, Project interna </category> <guid isPermaLink="true"></guid>
  54. <author>Arvid [email protected]</author>
  55. <pubDate>Sat, 17 Nov 2018 10:59:22 -0500</pubDate>
  56. <comments></comments>
  57. </item>
  58. <item>
  59. <title>FlatPress lives! New maintainer aboard, new version ahead</title>
  60. <link></link>
  61. <description><![CDATA[ <p>Hi everybody,</p>
  62. <p><a href="">in July</a>, sad news striked: Edoardo announced the end of FlatPress.<br />
  63. It took quite a while, but now here I am to prove him wrong: <strong>FlatPress lives.</strong></p>
  64. <h4>What&#8217;s the current situation?</h4>
  65. <p>Edoardo is about to hand me over all aspects of the project. Since I&#8217;m able to write this blog post here on, the first steps seem to have worked ;)<br />
  66. The transfer of the <a href="">GitHub project</a> is still to be done.</p>
  67. <h4>Who will maintain FlatPress from now on?</h4>
  68. <p>My name is Arvid, I am a software engineer from Germany. FlatPress is not my first experience with open source projects. I was founder, leader and coder of <a href="">moziloCMS</a>, a German open source PHP-based flatfile CMS.<br />
  69. I am a FlatPress user since 2013, you may know me from <a href="">the forums</a> as &#8220;azett&#8221;. Over the years, I contributed <a href=";i18n=en">some plugins</a> to FlatPress. Also, I built an inofficial version <a href=";i18n=en">FlatPress 1.0.3.php7</a> based on the latest FlatPress release 1.0.3 to be used with PHP7. (See my GitHub fork <a href="">here</a>.)</p>
  70. <h4>What&#8217;s the plan?</h4>
  71. <p>I want to keep the project FlatPress running, so all you FlatPress users out there are able to keep running your FlatPress-powered blogs.</p>
  72. <p>I won&#8217;t come up with dozends of fancy-shmancy new features. As first step, I will just make sure FlatPress works correctly under current PHP versions (which it sadly does not right now). My PHP7 version of FlatPress will most likely become the next official FlatPress release. Also, HTTPS support is very important.</p>
  73. <p>Another big issue on my plan is to revive the community. It has been <em>very</em> quiet on the forums lately.</p>
  74. <h4>What can YOU do?</h4>
  75. <ul>
  76. <li><strong>Let me know you&#8217;re out there.</strong><br />
  77. Leave me a comment below, drop me some lines <a href="">on the forums</a> or send me an <a href="mailto:[email protected]">email</a>. <em>(There will be an offical address later.)</em><br />
  78. I need to know that the effort is worth it.</p>
  79. </li>
  80. <li><strong>Help me testing the upcoming new FlatPress version.</strong><br />
  81. <a href="">Download the latest version of my FlatPress fork</a> and test it thoroughly. There is also an <a href=";i18n=en">update package</a> (1.0.3 to 1.0.3.php7).<br />
  82. Does everything run fine under PHP 5 <em>and</em> 7? Do all your plugins and themes continue to work? Let me know <a href="">on the forums</a>!<br />
  83. As soon as I have access to the official FlatPress GitHub project, I can then pull the changes from my fork to the official FlatPress repository and release an official new FlatPress version.</p>
  84. </li>
  85. <li><strong>Get aboard the FlatPress team.</strong><br />
  86. If you like to join me on my mission, let me know. You may be a coder, a template designer, or maybe you just want to help me moderating the forums and <a href="">the wiki</a>. Every help is welcome!</p>
  87. </li>
  88. <li><strong>Keep up to date.</strong><br />
  89. To stay informed about the further development of the FlatPress project, check out <a href=""></a> once in a while. You may also subscribe to <a href="">the RSS feed</a>.<br />
  90. (The forums <a href="view-source:">also have an RSS feed</a>, did you know?)</p>
  91. </li>
  92. <li><strong>Spread the word!</strong><br />
  93. Tell the world that FlatPress lives. Tell everybody how simple and great this blogging tool is. Get active on the forums, help each other, and give a warm welcome to new users. Revive the community - it is a vital part of a buzzing open source project.
  94. </li>
  95. </ul>
  96. <h4>And finally: A few words of thanks</h4>
  97. <p>I would like to thank <a href="">Edoardo Vacchi</a> a.k.a. the NoWhereMan, who kicked off this fine piece of open source software. A big salute to your years of effort on this really great flatfile blogging system, Sir! Also thanks for handing me over everything and thus giving me the opportunity to keep FlatPress alive.</p>
  98. <p>Thanks to Matthias Mauch as well - my PHP 7 version of FlatPress is based on his <a href="">FP-Patch</a>.</p>
  99. <h4>More to come soon</h4>
  100. <p>I am looking forward to getting your comments and responses. Let&#8217;s see if this all works - I&#8217;d love it to!</p>
  101. <p>Best wishes,<br />
  102. Arvid
  103. </p>
  104. ]]></description>
  105. <category>Announcements, Project interna </category> <guid isPermaLink="true"></guid>
  107. <author>Arvid [email protected]</author>
  108. <pubDate>Wed, 14 Nov 2018 13:12:13 -0500</pubDate>
  109. <comments></comments>
  110. </item>
  111. <item>
  112. <title>Hello, long time no see</title>
  113. <link></link>
  114. <description><![CDATA[ <p><img src=";ixid=eyJhcHBfaWQiOjEyMDd9&#038;s=8a521d093243b38f820fff88b8917858&#038;auto=format&#038;fit=crop&#038;w=600&#038;q=80" alt="photo-1422513391413-ddd4f2ce3340?ixlib=rb-0.3.5&#038;ixid=eyJhcHBfaWQiOjEyMDd9&#038;s=8a521d093243b38f820fff88b8917858&#038;auto=format&#038;fit=crop&#038;w=600&#038;q=80" title="photo-1422513391413-ddd4f2ce3340?ixlib=rb-0.3.5&#038;ixid=eyJhcHBfaWQiOjEyMDd9&#038;s=8a521d093243b38f820fff88b8917858&#038;auto=format&#038;fit=crop&#038;w=600&#038;q=80"  /><br />
  115. <span style="font-size:x-small"><a href="">Pic by Josh Felise</a></span></p>
  116. <p>I owe you guys an apology. </p>
  117. <p>You all will have noticed that I&#8217;ve been away from FlatPress forums for quite a while. </p>
  118. <p>And you&#8217;ll all have noticed that it&#8217;s been quite a while since the last FlatPress release.</p>
  119. <p>So, <strong>sorry about that.</strong></p>
  120. <p>Reason I&#8217;m breaking the silence today is that, in the last few days, <strong>this server has been compromised</strong>. Now it should be back online, but I am taking this chance to to say what you all already know.</p>
  121. <h4>The FlatPress project is basically dead.</h4>
  122. <p>FlatPress was born, believe it or not, <strong>12 years ago</strong>. </p>
  123. <p>In 2006, PHP 4 and shared hosts roamed the Earth. Many of these free services did not provide a SQL installation, and even the PHP installs were extremely limited.  I started blogging with SimplePHPBlog (another dead project), but at some point, together with some friends (<strong>drudo</strong> and <strong>hydra</strong>) from the Italian community, we started developing something more extensible. <strong>FlatPress was born there</strong>. </p>
  124. <p>But <strong>times have changed</strong>. Nowadays, there are fewer blogs. People use Twitter, Facebook, and, often, for longer texts, Medium. WordPress is still present, both as a hosted platform, and as the usual self-hostable script. It&#8217;s changed a lot, too. </p>
  125. <p>PHP itself has changed a lot. In 2006, I chose PHP for FlatPress because it was <strong>everywhere</strong>. But today, as a programmer, I can host a Jekyll/Hugo/Pelican (etc.) blog on <a href=""></a> in seconds. These <strong><a href="">static web site/blog generators</a></strong> are a breeze to use, and there are many for non-programmers, too. They all share the FlatPress spirit, of being simple, easy to customize, with a flat-file post format that can be easily edited in a plain text editor. And, what&#8217;s better, they <strong>don&#8217;t even</strong> require a scripting language on your server, because they&#8217;re pre-rendered before you upload them!</p>
  126. <p>Comments, you ask? We don&#8217;t need to self-host those either: we have Disqus, Facebook comments and many more. </p>
  127. <p><a href="">Static web site generators</a> are now really practical, and in my view, almost the norm. So, if you loved FlatPress, that&#8217;s what you should try.</p>
  128. <p>So, here&#8217;s the thing:</p>
  129. <h4>The FlatPress project has no reason to exist anymore</h4>
  130. <p>It&#8217;s been ages since I&#8217;ve touched a line of PHP code, anyway. And PHP has changed a lot too. Nowadays I&#8217;m mostly a backend guy and I work with a range of technologies that span from Java to Scala, to native. Hell, I don&#8217;t even recognize HTML and CSS anymore. And PHP? And JavaScript? They&#8217;re completely different languages now! Not to mention that I&#8217;m pretty sure the FlatPress code base is pretty much crap now :P (but hey, it was my first nontrivial project!)</p>
  131. <p>I have finished my PhD in DSL and programming language development in 2015, I joined the R&#038;D department at UniCredit Bank; and finally I have joined <strong>Red Hat</strong> this year. <a href="">You can follow me on Twitter if you&#8217;d like to</a></p>
  132. <h4>What now?</h4>
  133. <p>Code will still be on GitHub. If anybody is interested, you can contact me, and I&#8217;ll give access to the theme archive. The website will be probably still available up to October 2018, then it&#8217;ll probably shut down.</p>
  134. <p>As for migration for your old posts, I have tried more than once to create a &#8220;converter&#8221; script for FlatPress posts to markdown (most of these platform use Markdown), or at least HTML. Unfortunately I&#8217;ve never had the time. Hopefully, someone from the community will. </p>
  135. <h4>Thank you</h4>
  136. <p>So, I take the chance to say, today, on my 32nd birtday, thank you FlatPress, and thank you, FlatPress community, it&#8217;s been one hell of a ride.</p>
  137. <p><strong>Edoardo Vacchi <strong>a.k.a.</strong> the NoWhereMan</strong></p>
  138. ]]></description>
  139. <category>News, Announcements </category> <guid isPermaLink="true"></guid>
  141. <author>Arvid [email protected]</author>
  142. <pubDate>Fri, 06 Jul 2018 06:30:26 -0400</pubDate>
  143. <comments></comments>
  144. </item>
  145. </channel>
  146. </rss>

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda