weeheavy/pelican-theme
1
0
Fork 0
forked from github/pelican
Code Pull requests Activity
pelican-theme/pelican/tests/output/custom/feeds/yeah.atom.xml

16 lines
1.8 KiB
XML
Raw Normal View History

add output files for "samples" so that we can make functionnal testing
2012-03-30 13:40:40 +02:00
<?xml version="1.0" encoding="utf-8"?>
Test for SITESUBTITLE in feeds. It's now present in both RSS and Atom feeds.
2017-10-29 21:28:11 +01:00
<feed xmlns="http://www.w3.org/2005/Atom"><title>Alexis' log - yeah</title><link href="http://blog.notmyidea.org/" rel="alternate"></link><link href="http://blog.notmyidea.org/feeds/yeah.atom.xml" rel="self"></link><id>http://blog.notmyidea.org/</id><updated>2013-11-17T23:29:00+01:00</updated><subtitle>A personal blog.</subtitle><entry><title>This is a super article !</title><link href="http://blog.notmyidea.org/this-is-a-super-article.html" rel="alternate"></link><published>2010-12-02T10:14:00+01:00</published><updated>2013-11-17T23:29:00+01:00</updated><author><name>Alexis Métaireau</name></author><id>tag:blog.notmyidea.org,2010-12-02:/this-is-a-super-article.html</id><summary type="html">&lt;p class="first last"&gt;Multi-line metadata should be supported
Use the summary as the feed's description, and put content in content This adheres more closely to the specs, especially Atom, where the 'description' arg becomes <summary>. Note that this means full article content will no longer appear in RSS feeds.
2016-08-07 17:04:03 -07:00
as well as &lt;strong&gt;inline markup&lt;/strong&gt;.&lt;/p&gt;
</summary><content type="html">&lt;p&gt;Some content here !&lt;/p&gt;
add output files for "samples" so that we can make functionnal testing
2012-03-30 13:40:40 +02:00
&lt;div class="section" id="this-is-a-simple-title"&gt;
&lt;h2&gt;This is a simple title&lt;/h2&gt;
&lt;p&gt;And here comes the cool &lt;a class="reference external" href="http://books.couchdb.org/relax/design-documents/views"&gt;stuff&lt;/a&gt;.&lt;/p&gt;
samples: Remove EXTRA_PATH_METADATA entries for pictures I'd added them earlier to test that a configuration edit could preserve the original output locations. However, it is likely that you have quite a number of static files, and we shouldn't recommend listing explicit paths for all of them. With this configuration change, the pictures will be copied into the output directory using their original relative path (e.g. `pictures/Fat_Cat.jpg` without the `static`). Any |filename|-style links will be updated automatically. If you *want* the pictures to end up in a `static` directory, it's easier to just organize your source that way.
2013-01-05 08:42:50 -05:00
&lt;img alt="alternate text" src="http://blog.notmyidea.org/pictures/Sushi.jpg" style="width: 600px; height: 450px;" /&gt;
&lt;img alt="alternate text" src="http://blog.notmyidea.org/pictures/Sushi_Macro.jpg" style="width: 600px; height: 450px;" /&gt;
add output files for "samples" so that we can make functionnal testing
2012-03-30 13:40:40 +02:00
&lt;pre class="literal-block"&gt;
&amp;gt;&amp;gt;&amp;gt; from ipdb import set_trace
&amp;gt;&amp;gt;&amp;gt; set_trace()
&lt;/pre&gt;
&lt;p&gt;→ And now try with some utf8 hell: ééé&lt;/p&gt;
&lt;/div&gt;
Update functional test output for category in feed
2019-10-17 10:34:03 -07:00
</content><category term="yeah"></category><category term="foo"></category><category term="bar"></category><category term="foobar"></category></entry></feed>
Copy permalink