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.

Notes:

  • RSS (Rich Site Summary) is an XML standard used to publish frequently updated works such as blog entries, news headlines and audio.
  • Atom is an XML syndication format used for web feeds.
  • Syndic8.com at http://www.syndic8.com/ lists many RSS and ATOM feeds.

Syntax Rules

%HEADLINES{"..."}%

Parameter Explanation Default
"..." Source of RSS or ATOM 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
header="..." Header. May 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. May 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
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

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. Note that some of the variables are already used above. This is done by purpose to use different feeds with the same formatting parameters. If there's a conflict the non-dc tags have higher precedence, i.e. a <title> content </title> is preferred 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 referring 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:

Sun, 17 Nov 2019 18:25:45 +0000
The original blog about business opportunities and business ideas for small business entrepreneurs
Sun, 17 Nov 2019 18:25:43 +0000 Carrol Strain
Featured image by Veerasak Piyawatanakul on Pexels

Employee happiness is one of the key elements behind the ultimate success of a business. But how can you make employees happy? For one thing, consider applying UX principles to improve your office design. The wise use of UX principles can enhance employees’ satisfaction and happiness at work.

What Are UX Principles?

UX is short for “user experience.” According to the Interaction Design Foundation, UX principles involve design elements that are easy to use and pleasurable. Designers in multiple fields rely on these principles. This is true whether they’re designing a website, a building, or a space within a building.

The ultimate aim of UX design is to appeal to users’ senses, whether offline-as in an office-or virtual, as with a website. So, for instance, a designer who is using UX principles in office design might incorporate functional and ergonomic furniture. Additionally, the designer could include spaciousness, pleasant lighting, colorful artwork, live plants, and perhaps even soft background music.

RELATED ARTICLE: RECRUIT TOP TALENT WITH GROOVY OFFICE DESIGN

What Do UX Principles Have to Do with Office Design?

Digital or offline, the user’s experience is one of the main drivers of business development. It ranks high on the list of priorities for any company that wants to succeed in any market.

But what do UX principles have to do with office design?

Office design might be a complex process, but it's not a complicated one. In order to align with UX principles, your office design should take into account:

  • The WHO: Who is it for? Who are the beneficiaries?
  • The WHAT: What is it organizing? Is it spaces, people, resources?
  • The WHEN: When will a certain space, furnishing, or piece of equipment, be used?
  • The WHERE: Where should a designated space, furnishing, or piece of equipment, be located for maximum efficiency?
  • The WHY: Why should office design be made with UX principles in mind?

Incorporate UX Principles That Meet Users' Needs

If your office design process is in its incipient stage, prepare for some back-and-forth between and among you and your team.

For example, on more than on one occasion, designers who were trying to work according to UX principles have found themselves in the wrong. Chiefly, this was because they assumed what users wanted without ever asking. Then, when users complained, back to the drawing board they had to go.

Assuming what users want without asking them represents a major offense when it comes to applying UX principles to office design.

Design for Your Staff, Not for Yourself

There are several things you can do to meet your employees’ needs when preparing office spaces for them. First of all, remember to be flexible. Secondly, design for the users, not for yourself.

Finally, avoid making arbitrary decisions. Instead, start by asking employees their opinions. Then do some A/B testing, all the while keeping UX principles in mind.

For example, let’s say you’re working with furniture arrangement. Perhaps you place a certain sofa near the coffee bar. It seems like a perfectly good idea. It’s convenient, and it looks good, too. However, it turns out to be in everyone's way. So you try moving it elsewhere, because hopefully, it's not nailed down.

Continue the process throughout your office space, taking into account all of users’ senses, including ergonomics and kinesthesia.

Allow the Office Space to Continue to Evolve

You might need to hire an interior designer to come up with a fully functional and beautiful office design. However, once that’s behind you, how can you continue to maintain ease and functionality in everyone’s day-to-day activities?

Fortunately, at least when it comes to booking rooms, you can turn to room booking software from YArooms. This room management system takes care of office functionality with ease. This is because it was built with UX principles in mind.

Turn to YArooms When It Comes to Bookings

When it comes to booking rooms, YArooms makes sure its users' needs are covered. For example, you can access the platform from a browser interface, from Outlook, or even right at your doorstep.

Just go to the Meeting Room Door Panel. Its flexible settings enable users to create multiple scenarios. In short, users will find that the UX principles that YArooms incorporates saves them time and gives them almost limitless flexibility.

The post Applying UX Principles to Modern Office Design appeared first on Business Opportunities.

Sun, 17 Nov 2019 15:04:15 +0000 Mel Martinez
Photo by bruce mars from Pexels

Does your house have a 'property for sale' board outside because you couldn't plan your expenses right? Is your bank account experiencing occasional negative numbers? Are you in need of a change, but struggle to afford the cost of moving? Are upcoming expenses causing you extra stress? You are not alone! The lack of financial fitness is shared among many women all over the country. But there is hope.

Women often find no need to devise a financial plan during times of plenty. It is not until we get into a serious financial crisis that we consider the benefits of tending to financial fitness proactively. As the world hurls into 2020, make the decision to define your financial goals and values and to differentiate between your needs and wants. Commit to financial fitness this year!

Here are 5 tips for women to become financially fit:

Talk About It

The first step to becoming financially fit is to take time to talk about money. Find a safe confidant with whom to share your financial concerns. This person could be an intimate partner or a friend or family member. However they are a part of your life, their ability to maintain confidentiality and ask you tough questions is of greatest concern. Money is a necessary resource for a healthy life and healthy conversation about money makes the difference for change and fitness.

RELATED CONTENT: DON’T LET FINANCIAL PHOBIAS KEEP YOU FROM GETTING DEBT RELIEF

Know Your “Why?”

You will not become financially independent without clear goals; the ''why'' of making sound financial decisions. Every woman has a different answer to this 'why' because each person's goals are unique. Whether it's to live your life well after retirement or to send your kids to college, being financially fit provides a way forward. 

Set a Financial Routine  

We all know about a weight loss routine. But have you ever heard of a financial workout routine? It works similarly to a fitness regime. You invest your time and energy to reap the rewards later. Both routines require mental and physical determination. 

Evaluate your spending habits and monitor your credit card expenditure every month. This will help you determine which items are costing you more, which items are necessities, and what expenses you can cut. Avoid over-spending so you do not feel overwhelmed or trapped by financial obligations. Start by making small changes and adjustments for creating a bigger impact later. 

Ask yourself, ''Are you always buying things you actually need or are you spending money unnecessarily?'' Lowering your expenses on unnecessary purchases allows you to begin saving money. Give the practice of saving a short term try, like a 20-day challenge. You may be surprised to see just how much you can save in just a short time. 

For reaping long-term benefits, identify the things you want to pay off in a certain time frame, such as six months. For example, focus on paying off credit card debts or your mortgage. Interest rates accrued on debts such as these make your overall spending higher than the amount you borrow. You must not lose your valuable property investments because of financial errors. So, clear those debts as quickly as possible. You will soon see how much you can save by doing so.

Reward Yourself

Accomplishing goals should be celebrated in ways big and small. For larger saving goals, set smaller ''milestone'' amounts that you can celebrate along the way. Plan your celebrations ahead of time and involve your family. It is fun to celebrate together! 

In addition, commit to a philanthropy of some sort. There are incredible rewards to your emotional and mental health that come from spending money on other people or for a good cause. Treat your friends or family to an evening out or donate generously to an effort to help society.

Push Yourself

Nobody can force you to become financially fit. Overcome bad spending habits and surround yourself with people who are positive and believe in planning for the future. When you push yourself, you get greater outcomes. 

In Conclusion

Financial fitness is a gift you can give yourself. With intention and focus, it is possible to work toward financial freedom, one small gain at a time. Your efforts will not only benefit you but also those in your life who observe you. When financial fitness is a reality, pass what you have learned on to others so they may benefit as well.

The post Financial Fitness – 5 Tips for Women appeared first on Business Opportunities.

Plugin Settings

Plugin settings are stored as preferences settings. Do not change the settings here, they are here only for illustration purposes showing the default values. Define the settings in Main.TWikiPreferences. For example, to customize the HEADLINESPLUGIN_USERAGENTNAME setting, add a * Set HEADLINESPLUGIN_USERAGENTNAME = ... bullet in Main.TWikiPreferences.

  • Refresh rate in minutes for cached feeds. Set to 0 to disable caching:
    • Set HEADLINESPLUGIN_REFRESH = 60

  • Maximum number of items shown:
    • Set HEADLINESPLUGIN_LIMIT = 100

  • Use LWP::UserAgent if set to 1, or fallback to TWiki's internal getUrl() method if set to 0:
    • Set HEADLINESPLUGIN_USELWPUSERAGENT = 1

  • Timeout fetching a feed using the LWP::UserAgent:
    • Set HEADLINESPLUGIN_USERAGENTTIMEOUT = 20

  • Name of user agent:
    • Set HEADLINESPLUGIN_USERAGENTNAME = TWikiHeadlinesPlugin/2011-07-08

  • Default header: (variables are explained in the syntax rules)
      * Set HEADLINESPLUGIN_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 HEADLINESPLUGIN_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

This is a pre-installed plugin. TWiki administrators can upgrade the plugin as needed on the TWiki server.

Note: You do not need to install anything on the browser to use this plugin. The following instructions are for the administrator who installs the plugin on the TWiki server.

  • For an automated installation, run the configure script and follow "Find More Extensions" in the in the Extensions section.

  • Or, follow these manual installation steps:
    • Download the ZIP file from the Plugins home (see below).
    • Unzip HeadlinesPlugin.zip in your twiki installation directory. Content:
      File:Sorted ascending Description:
      data/TWiki/HeadlinesPlugin.txt Plugin topic
      lib/TWiki/HeadlinesPlugin/Core.pm Plugin core
      lib/TWiki/Plugins/HeadlinesPlugin.pm Plugin Perl module
      pub/TWiki/HeadlinesPlugin/style.css Default CSS
    • Set the ownership of the extracted directories and files to the webserver user.
    • 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 configuration and testing:
    • Run the configure script, enable the plugin in the Plugins section
    • Configure the plugin: See plugin settings above.
    • Test if the installation was successful: See example above.

Plugin Info

  • 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

Plugin Author: TWiki:Main.PeterThoeny, TWiki:Main.MichaelDaum
Copyright: © 2002-2013 Peter Thoeny, TWiki.org
© 2005-2007 Michael Daum wikiring.de
License: GPL (GNU General Public License)
Plugin Version: 2013-02-16
2013-02-16: TWikibug:Item7091: Use TWISTY in installation instructions section and change history
2013-01-29: TWikibug:Item7131: HeadlinesPlugin doesn't match pattern in multiple lines.
2012-12-10: TWikibug:Item7070: HeadlinesPlugin doesn't support multiple disks.
2012-11-13: TWikibug:Item7016: Restore changes for earlier versions with LWP
2012-11-13: TWikibug:Item7020: Categorize TWiki Variable
2012-10-31: TWikibug:Item7016: Utilize <guid> value when it is available
2012-09-05: TWikibug:Item6837: Doc fixes
2011-07-17: TWikibug:Item6764: Add VarHEADLINES variable documentation; doc improvements; setting NO_PREFS_IN_TOPIC
2011-07-08: TWikibug:Item6725: Change global package variables from "use vars" to "our"
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
Plugin 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: VarHEADLINES, TWikiPlugins, AdminDocumentationCategory, TWikiPreferences


This topic: TWiki > HeadlinesPlugin
Topic revision: r8 - 2013-02-16 - TWikiContributor
 
Copyright © 1999-2019 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.