Headlines Plugin


This plugin displays RSS and ATOM feeds from news sites. Use it to build news portals that show headline news.

Note: Syndic8.com ( http://www.syndic8.com/ ) lists many RSS feeds.

Syntax Rules


Parameter Explanation Default
"..." source of RSS feed; this can be an url (starting with http) or a web.topic location for internal feeds None; is required
href="..." (Alternative to above) N/A
refresh="60" Refresh rate in minutes for caching feed; "0" for no caching Global REFRESH setting
limit="12" Maximum number of items shown Global LIMIT setting
touch="..." Touch (edit/save) topics if the feed has updates. Specify a comma-space delimited list of TopicNames or Web.TopicNames, such as "%TOPIC%, NewsLetter". Useful to send out newsletter using MailerContrib, showing new feeds since last newsletter. To update feeds, visit topics with feeds in regular intervals (using cron with wget or the like). N/A
header Header. Can include these variables: - $channeltitle, $title: title of channel (channel.title)
- $channellink, $link: link of channel (channel.link)
- $channeldescription, $description: description (channel.description)
- $channeldate, $date: publication date of the channel (channel.pubDate)
- $rights: copyrights of the channel (channel.copyright)
- $imagetitle: title text for site (image.title)
- $imagelink: link for site (image.link)
- $imageurl: URL of image (image.url)
- $imagedescription: description of image (image.description)
Global HEADER setting
format Format of one item. Can include these variables:
- $title: news item title (item.title)
- $link: news item link (item.link)
- $description: news item description (item.description)
- $date: the publication date (item.pubDate, item.date)
- $category: the article category (item.category)
Global FORMAT setting

The header and format parameters might also use variables rendering the dc, image and content namespace information. Note, that only bits of interest have been implemented so far and those namespaces might not be implemented fully yet.

Rendering the dc namespace

The following variables are extracting the dc namespace info, that could be used in header and format. Nnote, that some of the variables are already used above. This is done by purpose to use different feeds with the same formating parameters. If there's a conflict the non-dc tags have higher precedence, i.e. a <title> content </title> is prefered over <dc:title> content </dc:title> .

  • $title: channel/article title (dc:title)
  • $creator: channel creator (dc:creator)
  • $subject: subject text; this will also add an image according to the subject hash list, see above (dc:subject)
  • $description: ... (dc:description)
  • $publisher: the channel/article publisher (dc:publisher)
  • $contributor: ... (dc:contributor)
  • $date: ... (dc:date)
  • $type: ... (dc:type)
  • $format: ... (dc:format)
  • $identifier: ... (dc:identifier)
  • $source: ... (dc:source)
  • $language: ... (dc:language)
  • $relation: ... (dc:relation)
  • $coverage: ... (dc: coverage)
  • $rights: ... (dc: rights)

Rendering the image namespace

An image:item is converted into an <img> tag using the following mappings:

  • src: image url (rdf:about attribute of the image.item tag)
  • alt: image title (title)
  • width: image width (image:width)
  • height: image height image:height)

Rendering the content namespace

The variable $content is refering to the <content:encoding> content </content:encoding>.


Slashdot News


%HEADLINES{ "http://slashdot.org/slashdot.rdf" 
  header="*[[$link][$title]]:* $description" 
  format="$t* [[$link][$title]]"
to get the latest Slashdot news as a bullet list format:

HeadlinesPlugin ERROR: 500 Can't connect to slashdot.org:443

Business Opportunities Weblog


%HEADLINES{ "http://www.business-opportunities.biz/feed" limit="2" }%

to get the latest postings on the "Business Opportunities" weblog:

Tue, 20 Mar 2018 15:12:07 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Mon, 19 Mar 2018 03:16:27 +0000 Bizop Team

Aiming for SEO Improvement? 5 Things You Need to Know

SEO (Search Engine Optimization) refers to search marketing. It means optimizing your content and your site so that visitors to your website can find what they’re looking for. In order to achieve SEO improvement, you need to stay on top of the changes in this ever-evolving field.

It’s an understatement to point out that the SEO space has changed over time. Its continuous changes have been a nightmare to many business owners who are looking to establish themselves online.

Google and other major search engines use algorithms to prioritize content. Developers constantly update and refine these algorithms. In order to master SEO, you’ll need to stay up to date with these algorithms. When it comes to SEO improvement, you need to be no more than a step or two behind the changes.

This is one of the challenges you’ll need to overcome. The search engine robots are smart. Often they can tell when you’re applying SEO methods that aren’t natural. So if you are looking to dive into SEO improvement, here are some of the things you must know before you begin.


1. Optimize YouráOn-Site SEO

On-site optimization will go a long way toward improving your site’s SEO. The first thing you must do for on-site SEO improvement is to ensure that each page of your site and its content are stellar. These elements play a major role in influencing how your site performs.

When you’re developing a page for your website, for instance, make sure to include keywords in the major heading for your content. This helps search engines to understand the context and meaning of your content.

Additionally, use keywords in your titles. It’s even more beneficial to use keywords that contain 2 or 3 words. These are known as long-tail keywords. Always make sure that your content is of the highest quality and suited to your audience.


2. Off-Site Optimization Can Help, Too

Off-site optimization includes a variety of tactics, all of which help to give your site some authority. These strategies range from guest blogging to using social channels to showcase your website.

Be sure choose a guest platform that has authority, however. To do this, approach administrators of high authority sites that allow guest posts. Ask them if you can get a slot.




3. Earn Your Links

Some people will tell you that it’s all right to buy links. However, this is a detrimental approach.

Google loathes paid links. If the Google bots flag your site for engaging in link buying, that will mark the end of its journey on Google.

Therefore, make sure to post only high-quality content and reach out to your audience through social media. People will notice your good postings. Some of them will be inspired to mention your site on their blog posts. This will earn you links in a natural way.


4. Watch Your Speed

Analyze your website’s speed to ensure it loads well. This is one of the metrics that Google uses to rank sites. Therefore, you could be slipping in the ratings if you don’t optimize your site for speed.

Do this by making sure you don't use heavy images on your site. Also check for broken links. These will make your site sluggish. A slow site is a bad experience for users, so be sure to watch your speed.



5. Optimize for Mobile

Mobile matters in the current digital space.

That’s because more and more users access content over their mobile devices. Therefore, make sure your site runs well on both large and small screens. You might be surprised to learn that Google also uses mobile optimization as a factor in their rankings. This is because mobile optimization shows that you care about user experience and quality.

If you’re not sure how to go about optimizing for mobile screens, hire an SEO company in Las Vegas by going to Platinum Web Marketing. These folks will help you to modify your site so that it’s mobile-ready.


Enjoy Your Rise to the Top

SEO improvement is not all that difficult. With the tips we’ve given here, you can learn to master the essentials. From there, you can design a site that is useful to your site’s users. Before you know it, you’ll be earning links and enjoying a steady rise in the rankings.

The post Aiming for SEO Improvement? 5 Things You Need to Know appeared first on Business Opportunities.

Mon, 19 Mar 2018 03:14:37 +0000 Bizop Team

New to Game Development? Avoid These Common Mistakes

Are you new to game development? Or are you planning to develop a game? Then this article was written for you.

Here, we discuss some of the worst mistakes that beginning game developers make. Learn about them before you start your game development project.


Building Games, Not Technology

Don’t start developing your game by thinking that you will build a game engine. This is probably the worst mistake you can make as a beginning game developer.

This is because the engine that drives the game needs much more work than the game itself does. The game engine is the dark work, the work that no one will see.

If you’re working on the engine instead of the game, you’ll have no visual indicators that show your work in progress. Even with all the benefits ofámodern tools, libraries, and other materials, building the engine can be difficult. Leave the engine-building aspect of game development to the advanced programmers. As a beginner, focus instead on the game itself.




Choosing Too Big a Scope

Do not start your game development career by trying to make a big game your first time out. This is the problem that a lot of beginning game developers face. You will end up leaving it incomplete because the scope of your game is too massive.

Instead, begin your game development career by designing a smaller game, especially if you’re working alone. Start with a simple game that you can get your head around. Then the next time, take on a bigger game.

For your first game, start with an idea that excites you. Aim to get your game finished in a month or two. Then, with your newly acquired sense of accomplishment, try designing a larger game. This is how you will grow as a game developer.

After you’ve gotten a good sense of game development, if you want to design larger games, join up with a team of professional game developers. Remember that it can take up to a year for a team of 20 professional game developers working on professional gamer PCáto build a big game.


Not Showing Your Game to Others

Showing people your game is important for multiple reasons. First of all, if you are isolated, you will begin to lose your motivation and even your interest in your project. There is a chance that you will end up abandoning it.

Also, you will have no accountability if you do not show your game progress to another person. Then, too, people will make suggestions that can help you to improve your game. They will keep you on track and hold you accountable. They will help you to stay motivated until you complete your game.



Trying to Please Everybody

On the other hand, if you pay attention to everyone’s opinions and suggestions, you’ll end up pleasing no one, including yourself. What’s the point of that?

So listen to your game’s fans, but learn to ignore the comments of those who are trying to distract you. Your fans will tell you what they like about your specific game. Their comments can help you enormously to make improvements to your game.

People we admire are the people who finish what they start, and that includes people in the game development field. The world wants more games. Therefore, finish making your game by avoiding the mistakes mentioned here.

The post New to Game Development? Avoid These Common Mistakes appeared first on Business Opportunities.

Plugin Settings

Plugin settings are stored as preferences variables. To reference a plugin setting write %<plugin>_<setting>%, for example, %HEADLINESPLUGIN_SHORTDESCRIPTION%. Note: Don't modify the settings here; copy and customize the settings in Main.TWikiPreferences. For example, to customize the USERAGENTNAME setting, create a HEADLINESPLUGIN_USERAGENTNAME setting in Main.TWikiPreferences.

  • One line description, shown in the TextFormattingRules topic:
    • Set SHORTDESCRIPTION = Show headline news in TWiki pages based on RSS and ATOM news feeds from external sites

  • Refresh rate in minutes for cached feeds. Disable caching: 0, default: 60
    • Set REFRESH = 60

  • Maximum number of items shown. Default: 100
    • Set LIMIT = 100

  • Use LWP::UserAgent, or fallback to TWiki's internal getUrl() method. Default: yes

  • Timeout fetching a feed using the LWP::UserAgent. Default: 20

  • Name of user agent. Default: TWikiHeadlinesPlugin/2.21
      * Set USERAGENTNAME = TWikiHeadlinesPlugin/2.21

  • Default header: (variables are explained in the syntax rules)
      * Set HEADER = <div class="headlinesChannel"><div class="headlinesLogo"><img src="$imageurl" alt="$imagetitle" border="0" />%BR%</div><div class="headlinesTitle">$n---+!! <a href="$link">$title</a></div><div class="headlinesDate">$date</div><div class="headlinesDescription">$description</div><div class="headlinesRight">$rights</div></div>

  • Default format of one item: (variables are explained in the syntax rules)
      * Set FORMAT = <div class="headlinesArticle"><div class="headlinesTitle"><a href="$link">$title</a></div>$n<span class="headlinesDate">$date</span> <span class="headlinesCreator"> $creator</span> <span class="headlinesSubject"> $subject </span>$n<div class="headlinesText"> $description</div></div>

  • Values taken from configure: (only supported if CPAN:LWP is installed)
    • $TWiki::cfg{PROXY}{HOST} - proxy host, such as "proxy.example.com";
    • $TWiki::cfg{PROXY}{PORT} - proxy port, such as "8080";
    • $TWiki::cfg{PROXY}{SkipProxyForDomains} - domains excluded from proxy, such as "intra.example.com, bugs.example.com";

Style Sheets

The default HEADER and FORMAT settings use the following styles. See the style.css file defining the default CSS properties (indentation illustrates enclosure).

  • headlinesRss: output of the HeadlinesPlugin (div)
    • headlinesChannel: channel header (div)
      • headlinesLogo: channel logo (div)
      • headlinesTitle: channel title (div)
      • headlinesDate: channel date (div)
      • headlinesDescription: channel description (div)
      • headlinesRight: channel copyright (div)
    • headlinesArticle: one news item (div)
      • headlinesTitle: article title (div)
      • headlinesDate: article date (span)
      • headlinesCreator: author of article (span)
      • headlinesSubject: subect category of the article (span)
      • headlinesText: article text (div)

Plugin Installation Instructions

  • Download the ZIP file.
  • Unzip it in your twiki installation directory. Content:
    File: Description:
    data/TWiki/HeadlinesPlugin.txt plugin topic
    pub/TWiki/HeadlinesPlugin/style.css default css
    lib/TWiki/HeadlinesPlugin.pm plugin perl module
    lib/TWiki/HeadlinesPlugin/Core.pm plugin core
    Check if above examples show a news feed instead of variable.
  • Optionally, run HeadlinesPlugin_installer.pl to automatically check and install other TWiki modules that this module depends on. You can also do this step manually.
  • Alternatively, manually make sure the dependencies listed in the table below are resolved.
    Digest::MD5>=2.33Required. Download from CPAN:Digest::MD5
    LWP::UserAgent>=5.803Optional. Download from CPAN:LWP::UserAgent

Plugin Info

Plugin Author: TWiki:Main.PeterThoeny, TWiki:Main.MichaelDaum
Copyright: © 2002-2009, Peter Thoeny, TWIKI.NET; 2005-2007, Michael Daum http://wikiring.de
License: GPL (GNU General Public License)
Plugin Version: v2.3 - 29 Aug 2009
Change History:  
29 Aug 2009: added touch parameter -- Peter Thoeny
12 Feb 2009: {PROXY}{HOST} supports domain with and without protocol -- Peter Thoeny
06 Feb 2009: added {PROXY}{SkipProxyForDomains} configure setting, added USERAGENTNAME plugin setting -- Peter Thoeny
11 Dec 2008: added {PROXY}{HOST} and {PROXY}{PORT} configure settings -- Peter Thoeny
13 Sep 2007: fixed parsing of content:encoded
23 Jul 2006: improved atom parser; if a posting has no title default to 'Untitled'
26 Apr 2006: added lazy compilation
10 Feb 2006: packaged using the TWiki:Plugins/BuildContrib; minor fixes
03 Feb 2006: off-by-one: limit="n" returned n+1 articles; make FORMAT and HEADER format strings more robust
23 Jan 2006: released v2.00
05 Dec 2005: internal feed urls must be absolute
02 Dec 2005: added web.topic shorthand for internal feeds
29 Nov 2005: fixed CDATA handling
21 Nov 2005: added ATOM support; extended RSS support; added dublin core support; added content support; optionally using LWP to fetch feeds to follow redirections; corrected CPAN dependencies ; recoding special chars from html integer to entity encoding to increase browser compatibility; added css support; use getWorkArea() if available
11 May 2005: TWiki:Main.WillNorris: added DevelopBranch compatability
31 Oct 2004: Fixed taint issue by TWiki:Main.AdrianWeiler; small performance improvement
29 Oct 2004: Fixed issue of external caching if mod_perl or SpeedyCGI is used
02 Aug 2002: Implemented caching of feeds, thanks to TWiki:Main/RobDuarte
11 Jun 2002: Initial version (V1.000)
Perl Version: 5.8
TWiki:Plugins/Benchmark: GoodStyle 100%, FormattedSearch 99.5%, HeadlinesPlugin 94%
Plugin Home: TWiki:Plugins/HeadlinesPlugin
Feedback: TWiki:Plugins/HeadlinesPluginDev
Appraisal: TWiki:Plugins/HeadlinesPluginAppraisal

-- TWiki:Main.PeterThoeny - 29 Aug 2009

Log In, to register you need to be a member of the club and contact the webmaster.
Topic revision: r2 - 2009-08-29 - 21:55:14 - TWikiContributor

This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
Note: Please contribute updates to this topic on TWiki.org at TWiki:TWiki.HeadlinesPlugin