RSSify TNG - rssify your web page

RSSify TNG

Meta Data

HTML Source

The URL of the website to be parsed (ending in "/" or a file name):

RSS Version

RSS 0.92 (according to the RSS 0.92 specification)

RSS 1.0 (according to the RDF Site Summary (RSS) 1.0 specification)

RSS 2.0 (according to the RSS 2.0 specification)

Retain HTML in RSS?

Yes
No

RSSify TNG uses <content:encoded> for RSS 1.0 and RSS 2.0. With RSS 0.92, HTML tags are displayed in the <description> element.

If yes, allowable tags:

Number of Items

Number of items that are displayed in the RSS (max. 30):

Channel Elements

<channel><language>

Site language:

<channel><title>

Extract <channel><title> from the <title> tag of the HTML page?
Yes
No

Source code modification required:

Define <title>...</title> tag

If 'No', please enter your title here:

<channel><description>

Extract <channel><description> from the first <h1> tag of the HTML page?
Yes
No

Source code modification required:

Set at least one <h1>...</h1> tag

If 'No', please enter a short description for your site here:

<channel><managingEditor>

Editor contact: Example.: p.sample@domain.tld (Peter Sample)

<channel><webMaster>

Technical contact: Example.: p.sample@domain.tld (Peter Sample)

<channel><copyright>

Copyright Info:

<channel><image>

Display an image (channel image) in the RSS?
Yes
No

If yes, image URL (jpg, gif or png, 88 px width X 31 px height):

<channel><textInput>

Display an input field in the RSS? (e.g. for an internal search function)
Yes
No

If yes, what is the name of the POST button?:

If yes, what is the name of the name attribute of the input field:

If yes, indicate the URL for the action attribute of the input form:

If yes, enter a short description for the input form:

<channel> <lastBuildDate>

Display last updated date and time in the RSS?
Yes
No

Note: This will only work if date information is included in individual posts and have been flagged with <!--start itemdate-->23.05.2003<!--end itemdate--> and <!--start itemtime-->11:08:51 PM<!--end itemtime-->.

Date/time format used in source page:

Source code modification required:

Flag a date: <!--start itemdate-->23.05.2003<!--end itemdate-->

Flag a time: <!--start itemtime-->11:08:51 PM<!--end itemtime-->

Source-dependent RSS elements

In order for RSSify TNG to recognize the following elements, you do not need to indicate anything on this form. Instead you must include the following HTML comments in the source of the page to be parsed in order for RSSify TNG to recognize them and create RSS elements from them.

<item></item>

Source code modification required:

Flag individual posts (RSS items) with <!--start item-->...<!--end item-->.

<item><title>

Source code modification required:

Flag post titles with<!--start itemtitle-->...<!--end itemtitle-->.

<item><description>

Source code modification required:

Flag descriptions within RSS items with <!--start rssdesc-->...<!--end rssdesc-->.

<item><pubDate> in RSS 2.0 / <item><dc:date> in RSS 1.0

Source code modification required:

Flag a date: <!--start itemdate-->23.05.2003<!--end itemdate-->

Flag a time: <!--start itemtime-->11:08:51 PM<!--end itemtime-->

<item><dc:creator>(RSS 1.0 und 2.0)

Source code modification required:

Flag an author: <!--start author-->JonnyMan<!--end author-->

Position of hyperlinks

Finally, RSSify TNG needs to know what to do with hyperlinks contained in the posts. Posts are those areas of the website to be parsed that have been flagged within <!--start item--> and <!--end item-->.

<item><link> in RSS 0.92 and 1.0, <item><guid> in RSS 2.0

What becomes the permalink?:
first hyperlink in the post
last hyperlink in the post
second to last hyperlink in the post
third to last hyperlink in the post
fourth to last hyperlink in the post
fifth to last hyperlink in the post

User-defined permalinks:

Independent of the settings above, you can tell RSSify TNG directly which link in your post (or rather, item link in the RSS) becomes the permalink. With this mode on, the | sign in front of a hyperlink flags the permalink of a particular post.

on
off

Source code modification required:

Put a | sign in front of the hyperlink to become the permalink:
|<a href="http://somedomain.tld/permalink.html">Permalink</a> or
<span style="display: none;">|</span><a href="http://somedomain.tld/permalink.html">Permalink</a>, to keep the browser from displaying the | sign.

<item><comments> (only in RSS 2.0)

Do the posts have links to comments to be included in the RSS?:
Yes
No

Which link leads to the comments page?:
first hyperlink in the post
last hyperlink in the post
second to last hyperlink in the post
third to last hyperlink in the post
fourth to last hyperlink in the post
fifth to last hyperlink in the post

<item><author> (only in RSS 2.0)

Are there mailto links to the author of each post to be included in the RSS?:
Yes
No

Which link contains the mailto link to the author?:
first hyperlink in the post
last hyperlink in the postg
second to last hyperlink in the post
third to last hyperlink in the post
fourth to last hyperlink in the post
fifth to last hyperlink in the post

Funkiness

Unfunky like Frank Sinatra
Funky like Bootsy Collins

The funkiness determines which RSS element receives priority in the generation of the RSS feed. Example: It is not allowed, to use the elements <author> and <dc:creator> simultaneously. But this can easily happen with Rssify TNG if both the dc:creator tags in the page to be parsed and a mailto link to the author are flagged on this form.

The "Unfunky" option gives priority to the <author> element,
"Funky" gives priority to the <dc:creator> element.

RSS Generation

Where to put the RSS files?

Directory for the RSS files: (do not include the / at the end.)

File name RSS 0.92: .xml
File name RSS 1.0 : .rdf
File name RSS 2.0 : .xml
(In case of a dynamic rss feed the filename extension for all feeds will be .php)

RSSify

Preview in browser
Create dynamic RSS file on the server (Extension .php)
Create static RSS file on the server (Extension .xml/.rdf)

CC-GNU GPL
This software is licensed under the CC-GNU GPL.