<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 21 May 2013 05:01:34 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPMaster.com: Building ePub with PHP and Markdown]]></title>
      <guid>http://www.phpdeveloper.org/news/19264</guid>
      <link>http://www.phpdeveloper.org/news/19264</link>
      <description><![CDATA[<p>
On PHPMaster.com today there's a new post showing you how to <a href="http://phpmaster.com/building-epub-with-php-and-markdown/">create ePub documents</a> from Markdown-formatted files with the help of the <a href="https://github.com/vtardia/md2epub">md2epub</a> and <a href="http://www.raintpl.com/">RainTPL</a> libraries.
</p>
<blockquote>
The ePub format is a publishing standard built on top of XHTML, CSS, XML and more. And since PHP is well suited for working with HTML and friends, why not use it to build ebooks? In this article we'll see what goes into building a tool for creating ePub packages starting from a set of content files. Maybe it's your next best selling cyber-sci-fi novel or documentation for your latest code project… because we all write good documentation for our projects, don't we?
</blockquote>
<p>
He starts off with an introduction to the ePub format, showing the directory structure the package has to follow and some example contents. He helps you set up a test book with two chapters, cover images, styling and a cover/title page. Included in the tutorial is all of the code you'll need to make your own "ePub builder" tool and a <a href="https://code.google.com/p/epubcheck/">suggestion of a tool</a> to check the end result.
</p>]]></description>
      <pubDate>Mon, 04 Mar 2013 10:52:45 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[CodeIgniter.com: A Quick Look at Sparks]]></title>
      <guid>http://www.phpdeveloper.org/news/17671</guid>
      <link>http://www.phpdeveloper.org/news/17671</link>
      <description><![CDATA[<p>
On CodeIgniter.com there's a new post <a href="http://codeigniter.com/news/a_quick_look_at_sparks#When:16:38:00Z">looking at Sparks</a>, reusable code components/packages for the CodeIgniter framework.
</p>
<blockquote>
On the back of a CIConf in London last month, I would like to delve a little into a common theme amongst CodeIgniter developers. Speeding up development through simple automation. To do that we're going to take a look at the CodeIgniter Sparks project and how it can drastically speed up your development. To demonstrate, I will walk through building a little portfolio that leeches off the GitHub API.
</blockquote>
<p>
They show you how to <a href="http://getsparks.org/install">install it from the Getsparks website</a>, finding Sparks to add to your application, the code to load in the component and configuring it on load. They include an example of loading in a REST client Spark and how to use it to make a request to Github and pull down a Markdown file.
</p>]]></description>
      <pubDate>Wed, 14 Mar 2012 09:49:36 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Anna Filina's Blog: Integrating Markdown with Symfony]]></title>
      <guid>http://www.phpdeveloper.org/news/16250</guid>
      <link>http://www.phpdeveloper.org/news/16250</link>
      <description><![CDATA[<p>
<i>Anna Filina</i> has a new post showing how you can integrate a documentation format that's become a bit more popular recently (due partially to its increased use on <a href="http://github.com">github</a>), Markdown, <a href="http://annafilina.com/blog/markdown-in-symfony/">into a Symfony application</a>.
</p>
<blockquote>
I needed to create a number of static help pages in three languages in a Symfony 1.4 application. Using the XLIFF translation files seemed absurd, since I knew that I will include a lot of HTML. [...] And so, I decided to create partials using the following structure: _docs/{lang}/{title}.php. This method would organize my pages nicely and will only load what is needed. Then, I remembered that we were planning to hire a technical writer for the rest of the manual. I wanted to make his life as easy as possible and the source files easy to read for everyone.
</blockquote>
<p>
She found the solution in <a href="http://en.wikipedia.org/wiki/Markdown">Markdown</a> and has included a step-by-step guide to getting it integrated with Symfony using <a href="http://michelf.com/projects/php-markdown/">this parser</a>. It's loaded as a helper and used to parse the partial view's content. You can find a quick guide to Markdown on the <a href="http://daringfireball.net/projects/markdown/syntax">Daring Fireball website</a>.
</p>]]></description>
      <pubDate>Tue, 26 Apr 2011 10:56:46 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Paul Jones' Blog: Solar 0.23.0 Released]]></title>
      <guid>http://www.phpdeveloper.org/news/6150</guid>
      <link>http://www.phpdeveloper.org/news/6150</link>
      <description><![CDATA[<p>
<i>Paul Jones</i> <a href="http://paul-m-jones.com/blog/?p=229">notes the release</a> of the latest version of the Solar framework with version 0.23.0 and some cool new features, specifically an enhancement for its Ajax support.
</p>
<blockquote>
<p>
The new release is out; you can <a href="http://solarphp.com/index.php/docs/Main/DownloadSolar">download it</a> from the usual location. As always, you should read the full <a href="http://solarphp.com/channel.php?package=Solar&release=0.23.0&downloads">change notes</a>.
</p>
<p>
This release of <a href="http://solarphp.com/">Solar</a> includes new Prototype and Scriptaculous ("Protaculous" ;-) Ajax support in the form of view helpers, ext/json compliant JSON support, and a new plugin-aware Markdown engine.
</p>
</blockquote>
<p>
He <a href="http://paul-m-jones.com/blog/?p=229">details out</a> the changes, talking about a few things that are broken (backwards compatibility), the "Protaculous" support, JSON support, and the implementation of <a href="http://daringfireball.net/projects/markdown/">Markdown</a> support.
</p>]]></description>
      <pubDate>Mon, 28 Aug 2006 07:48:50 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Thingoid.com: Markdown and PHP Markdown Extra Cheat Sheet]]></title>
      <guid>http://www.phpdeveloper.org/news/4661</guid>
      <link>http://www.phpdeveloper.org/news/4661</link>
      <description><![CDATA[From <i>Trevor</i>'s blog, <a href="http://www.thingoid.com">thingoid</a>, today, there's <a href="http://www.thingoid.com/2006/01/markdown-cheat-sheet/>this new post</a> linking to a Markdown and PHP Markdown "cheat sheet" he's created.
<p>
<quote>
<i>
Here's my <a href="http://www.thingoid.com/assets/PHPMarkdownExtraSyntaxSummary1.0.1.pdf>Markdown/PHP Markdown cheat sheet</a> or syntax summary.
<p>
I really enjoy using <a href="http://daringfireball.net/projects/markdown/>Markdown</a>. It's great to be able to write in (nearly) plain English - say, for submitting something for print - and being able to dump the same text down into the blog and have it work on the web. Setting aside writing-for-web vs. writing-for-print issues, I find this a great help.
<p>
And <a href="http://www.michelf.com/projects/php-markdown/extra/">PHP Markdown Extra</a> adds a few niceties, like Markdown inside HTML block tags, simple tables, and definition lists. It just drops straight into WordPress and away you go.
</i>
</quote>
<p>
For more information on Markdow (or it's use in PHP), you can check out the <a href="http://daringfireball.net/projects/markdown/syntax">Markdown manual</a> first and the <a href="http://www.michelf.com/projects/php-markdown/extra/">PHP one</a> to follow up...]]></description>
      <pubDate>Fri, 13 Jan 2006 07:30:50 -0600</pubDate>
    </item>
  </channel>
</rss>
