Headlines Plugin

Show headline news in TWiki pages based on RSS and ATOM news feeds from external sites

Description

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

%HEADLINES{"..."}%

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>.

Examples

Slashdot News

Write

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

Business Opportunities Weblog

Write

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

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

Thu, 03 Dec 2020 21:58:48 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Thu, 03 Dec 2020 21:58:47 +0000 Carrol Strain
Featured image by Å˜aj Vaishnaw from Pexels

While this post mainly addresses the needs of job-seekers, its advice is applicable to business owners as well. Which of your vendors, perhaps, might appreciate receiving a thank you email from you? Which of your clients? Your investors? Expressions of gratitude are never out of place and always welcome.

RELATED ARTICLE: ANDREW MILLER’S ADVICE TO CEO’S: NETWORK TO HELP YOUR BUSINESS

Businesses are continually looking for high-quality employees. They want people who are serious about working for their company, people who want to help the company succeed. However, many employers say that finding qualified workers is difficult.

On the other hand, job-seekers often find it difficult to find just the right position. Once you've been asked to attend an interview, you should do everything possible to impress the interviewer. You don't want to miss this opportunity since doing so could result in your missing out on a great opportunity.

With few jobs available, you need to take full advantage of the opportunities that come your way. With that being said, you should think about sending a thank you email after the interview has ended.

Ending the Interview

First and foremost, you should know that the interview doesn't end when you leave the office. The interview is a major component of the hiring process but it isn't the only step. You'll want to do what you can to show the HR representative that you're serious about getting the job. Show them not only that you want the job but also that you are more qualified.

So don’t stop when the interview has ended. There are ways to boost your chances afterward. One of those ways is to send the hiring manager a thank you email within a day after the interview.

Don't stop after the interview ends, because somebody else might not. If someone else sends a thank you letter and you don't, you just might lose the job to that person.

About Thank You Emails

You can learn more about thank you emails by visiting Algrim.co. Thank you emails are straightforward and uncomplicated. After the interview has ended, you'll want to thank the HR representative for taking time out of their day to sit down with you.

You'll want to thank them for listening to everything you had to say. And you'll want to thank them for giving you the chance. The thank you email helps you achieve these goals. On top of that, you can use the email to remind the individual about your credentials and qualifications.

Don't ramble on during your thank you email. Instead, keep it concise and get straight to the point. It is best to keep the email to one or two paragraphs. Anything longer would be going overboard.

How a Thank You Email Helps

Sending a thank you email will prove to be hugely beneficial. With this email, you'll be able to tell the interviewer that you sincerely care about getting the job. You'll also be able to tell them more about your credentials and experience.

Sending a thank you email is a quick, convenient, and free way to boost your chances of getting the job. Your email will remind the hiring manager about you. Use it to recap your qualifications quickly and succinctly. Above all, don't miss this opportunity. You might not get another one.

So remember: Send a thank you email promptly to improve your chances of getting the job.

Tips for Writing Thank You Emails

When it comes down to it, you have to keep your thank you emails brief. You don't want to create a hassle for the interviewer since this may create problems. If you take up too much of their time, your email might annoy them. They might not even read it at all.

So be concise. You should get to the point as quickly as possible. Again, it is best to write one or two paragraphs. You'll want to start by thanking the representative for their time and giving you a chance.

Then, you'll want to tell them more about you and your qualifications. Let them know you're interested in getting the job. Do this and your chances of being selected will increase significantly.

Boosting Your Chances with an Email After the Interview

At the end of the day, it can be difficult to find a good job these days. You shouldn't let this stop you, though.

When you get the opportunity for an interview, take full advantage of it. To do that, you should prepare for the interview before you go, then send a thank you email afterward. This combination can boost your chances.

Remember, if you want to beat the competition and get the job, sending a thank you email is a must.

The post How Thank You Emails Can Improve Your Prospects appeared first on Business Opportunities.

Wed, 02 Dec 2020 16:42:06 +0000 Carrol Strain
Featured image by aelitta

It is imperative to create a deep network of key individuals in your business to succeed as an executive today. We talked to the former CEO of Polycom Inc., Andrew Miller, to learn how he manages to create a powerful and valuable network.

Network Within Your Company

First, Miller gave us his insight into why he interacts with people in his organization at all stages and manufacturing areas. He claims that knowing what is going on at each of these levels allows him to more effectively direct his business.

Speaking and communicating with these individuals, he says, gives him important insights. Otherwise, he would not completely understand or be aware of various aspects of the operation. These ties help Miller to see what his business is doing well. Also, they show him what needs change and what corrections he needs to make.

Determine Your Why

You will get the most benefit out of every networking opportunity by determining your specific purpose. If you can't determine your specific goal, then identify how someone else can help you reach your goals. Learn this tailored strategy and network with those who are most profitable for you. Then you will begin to establish a dynamic community. Importantly, this invaluable network will help you accomplish your company's objectives.

RELATED ARTICLE: HOW BENCHMARKING CAN HELP YOUR ORGANIZATION CRUSH THE COMPETITION

Be Helpful

While establishing networking connections, you should first establish a mutually beneficial relationship. To this end, be authentic in your relationships. Also, offer your services when initially connecting. Show you are interested in their goals as much as your own. Accordingly, you will both enjoy a long-term and more fulfilling partnership.

RELATED ARTICLE: HOW TO IMPROVE YOUR NETWORKING APPROACH

Leverage LinkedIn by Networking with People You Know

Miller suggests utilizing LinkedIn by connecting with people you know. Be sure to include friends and colleagues who are able to speak to your work ethic and who you are as an individual. As you build your network within LinkedIn, utilize the ''People You May Know'' feature to expand your connections. Look for individuals who went to the same school you did. Also, look for others who work in related positions or industries in your area.

Sharing your experiences and ideas through LinkedIn is also valuable. A brilliant way to launch a dialogue with fellow CEO’s or colleagues is to share a brief video interview you have completed or a recent article you have posted. Also include any related hashtags. From your network, you will gain multiple insights and viewpoints. These may also encourage other experts to contact you specifically for your services.

RELATED ARTICLE: BUSY ENTREPRENEURS STAY AHEAD WITH ORGANIZATIONAL TIPS

Conclusion

Networking, with a little experience and perseverance, will help you engage with significant individuals and roles more efficiently. Take a few social risks and you will be met with incredible new relationships and opportunities.

The post Andrew Miller's Advice to CEO’s: Network to Help Your Business 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
    • Set USELWPUSERAGENT = yes

  • Timeout fetching a feed using the LWP::UserAgent. Default: 20
    • Set USERAGENTTIMEOUT = 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.
    NameVersionDescription
    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-2010, Peter Thoeny, Twiki, Inc.; 2005-2007, Michael Daum http://wikiring.de
License: GPL (GNU General Public License)
Plugin Version: v2.6 - 2010-05-16
Change History:  
2010-05-16: TWikibug:Item6433 - more doc improvements
2010-04-25: TWikibug:Item6433 - doc fix: Changing TWIKIWEB to SYSTEMWEB
2010-02-27: TWikibug:Item6313 - fixed bug in ATOM feed with <link ...></link> instead of <link ... /> -- Peter Thoeny
2009-09-30: fixed bug in lastBuildDate of feeds affecting touch parameter functionality -- Peter Thoeny
2009-08-29: 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: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPlugin
Feedback: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPluginDev
Appraisal: http://TWiki.org/cgi-bin/view/Plugins/HeadlinesPluginAppraisal

Related Topics: TWikiPlugins, AdminDocumentationCategory, TWikiPreferences

Topic revision: r1 - 2010.05.17 - TWikiContributor
 
This site is powered by the TWiki collaboration platformCopyright © 1999-2020 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.