|
Link - KEYWORD SEARCH RESULTS
Return to Links Main Page
2 - PRIMARY Keyword matches for PRODUCT
Click on any Title to go to that site
|
| Title |
Description |
WIKI ASP
Type: Product
Primary Key: Product
|
Wiki Asp is a wiki server written in ASP (Active Server Pages) code for Microsoft Windows. It is a variant of the original Aspwiki engine. It is probably one of the easiest to use and most effective wiki programs available for FREE.
* WikiAsp is very easy to use and yet powerful wiki.
* WikiAsp works with most free ASP sites like Brinkster.com.
Wiki Asp has a valid RSS feed.
|
|
How to choose a wiki engine
Examples of wiki software
. Python-based
. Ruby-based
. PHP-based
. LISP-based
. Microsoft
. Java-based
. Perl-based
. Smalltalk-based
. Unknown
Examples of wiki hosting services
See also
External links
How to choose a wiki engine
When choosing a wiki engine, criteria to consider might include:
* Who is developing it? A single person or a growing team?
* What license is it distributed under?
* Who is using it? A good wiki engine is likely to have a large group of existing users, and this is helpful if you need support running it.
* Features for editors: easy to write (and powerful) formatting rules, WYSIWYG capabilities, sectional editing, easy to roll back to earlier versions, file upload, insert image, able to write complex formulae etc.
* Features for readers: table of contents, search, navigation bar, access statistics, article rating, high quality printable version.
* User management: user personal page, personalized toolbar and preferences.
* Groupware features: forum, gallery, message system.
* Access controls. This is important for company intranet with security consideration.
* Be able to import external files (html, doc), export to external files (doc, pdf)
* Customizable interface: including main page, topbar, bottombar, sidebar; skins.
* Multilingual support.
* Extensibility: what third-party plugins exist, and what mechanisms are there for creating them.
* Portability. Are you locked into a particular package or wikitext format? Is it possible to export your text to other systems?
* Scalability: Is it suitable for large amount of pages or just a light-weight wiki software? Most scalable wiki software need a back end database to store pages.
|
9 - SECONDARY Keyword matches for WIKI
Click on any Title to go to that site
Click on any Primary Key to search by that keyword
|
| Title |
Description |
|
Amaya is a complete web browsing and authoring environment and comes equipped with a WYSIWYG style of interface, similar to that of the most popular commercial browsers. With such an interface, users do not need to know the HTML or CSS languages.
* Amaya lets users both browse and author Web pages
Using Amaya you can create Web pages and upload them onto a server. Authors can create a document from scratch, they can browse the web and find the information they need, copy and paste it to their pages, and create links to other Web sites. All this is done in a straightforward and simple manner, and actions are performed in a single consistent environment. Editing and browsing functions are integrated seamlessly in a single tool.
* Amaya maintains a consistent internal document model adhering to the DTD
Amaya always represents the document internally in a structured way consistent with the Document Type Definition (DTD). A properly structured document enables other tools to further process the data safely. Amaya allows you to display the document structure at the same time as the formatted view, which is portrayed diagrammatically on the screen.
* Amaya is able to work on several documents at a time
Several (X)HTML, native MathML (.mml) and SVG (.svg) documents can be displayed and edited at a time.
* Amaya helps authors create hypertext links
The editor helps you create and text out links to other documents on the Web from the document you currently are working on. You can view the links and get a feel for how the information is interconnected. This feature is not limited to HTML anchors. With XLink, any MathML and SVG element can be a link too.
* Amaya includes a collaborative annotation application
Annotations are external comments, notes, remarks that can be attached to any Web document or a selected part of the document. This application is based on Resource Description Framework (RDF), XLink, and XPointer recommendations. Amaya demonstrates an implementation of MathML which allows users to browse and edit Web pages containing mathematical expressions (see some examples). Like the rest of the document, these expressions are manipulated through a WYSIWYG interface. Amaya uses namespaces to integrate MathML expressions within XHTML documents, i.e. HTML documents written in XML syntax. This mechanism is also used to mix graphics in SVG and mathematics in MathML within XHTML documents.
|
|
A potentially very useful and interesting site but it loads so slowly it's almost useless
|
|
.
The most obvious difference between participatory journalism and traditional journalism is the different structure and organization that produce them.
Traditional media are created by hierarchical organizations that are built for commerce. Their business models are broadcast and advertising focused. They value rigorous editorial workflow, profitability and integrity. Participatory journalism is created by networked communities that value conversation, collaboration and egalitarianism over profitability.
Clay Shirky, an adjunct professor at New York University who has consulted on the social and economic effects of Internet technologies, sees the difference this way: "The order of things in broadcast is ‘filter, then publish.’ The order in communities is ‘publish, then filter.’ If you go to a dinner party, you don’t submit your potential comments to the hosts, so that they can tell you which ones are good enough to air before the group, but this is how broadcast works every day. Writers submit their stories in advance, to be edited or rejected before the public ever sees them. Participants in a community, by contrast, say what they have to say, and the good is sorted from the mediocre after the fact.
Many traditional journalists are dismissive of participatory journalism, particularly webloggers, characterizing them as self-interested or unskilled amateurs. Conversely, many webloggers look upon mainstream media as an arrogant, exclusive club that puts its own version of self-interest and economic survival above the societal responsibility of a free press.
According to Shirky, what the mainstream media fail to understand is that despite a participant’s lack of skill or journalistic training, the Internet itself acts as editing mechanism, with the difference that "editorial judgment is applied at the edges-after the fact, not in advance.
In The Elements of Journalism, Kovach and Rosenstiel take a similar view: "This kind of high-tech interaction is a journalism that resembles conversation again, much like the original journalism occurring in the publick houses and coffeehouses four hundred years ago. Seen in this light, journalism’s function is not fundamentally changed by the digital age. The techniques may be different, but the underlying principles are the same.
…
|
|
htmlArea is a WYSIWYG editor replacement for any ""textarea"" field. Instead of teaching your software users how to code basic HTML to format their content, they can use htmlArea to: * Format text to be bold, italicized, or underlined. * Change the face, size and colour. * Left, centre, or right-justify paragraphs. * Make bulleted or numbered lists. * Indent or un-indent paragraphs * Insert a horizontal line. * Insert hyperlinks and images. * Insert tables * View the raw HTML source of what they're editing.
|
|
Wikis are most commonly used as community-created resources for reference (like Wikipedia) or collaboration. I've been getting interested in them mainly for their e-learning potential. I'm starting to like them immensely, even though they're generally rather ugly (more on that below).
|
|
SnipSnap is a free and easy to install weblog and wiki tool written in Java.
|
|
Socialtext Workspace adapts wikis and weblogs for enterprise productivity and scale. Communication, collaboration and publishing for: IT and Consulting Project Management, Research and Analysis, Product Management and Events. Socialtext provides Social Network Analysis and Visualization services as an indicator of collaboration patterns and value generated. The analysis uses data based on publicly visible collaboration patterns within the organization, revealing the collaborative patterns in the group:
|
|
Welcome to TWiki, a flexible, powerful, and easy to use Web-based collaboration platform. Use TWiki to run a project development space, a document management system, a knowledge base, or any other groupware tool, on an intranet or on the internet. Web content can be created collaboratively by using just a browser. Developers can create new web applications based on a Plugin API.
"TWiki is powerful" said Jon Udell, a BYTE.com editor. "Among other things, TWiki eases one of the concerns about classic Wiki, which is that the radically egalitarian "edit this page" scheme leaves no change log. TWiki includes powerful revision support. Every change leaves a footprint, and you can follow these easily and effectively."
What does it look like?
TWiki looks and feels like a normal Intranet or Internet web site. However it also has a Edit link at the bottom of every topic (web page), everybody can change a topic or add content by just using a browser.
Who is using TWiki?
TWiki is installed on many web sites, mainly behind corporate firewalls. TWiki is being used by many major companies, because it is very user friendly compared to some well established commercial groupware systems like Lotus Notes. Read some TWikiSuccessStories to get an idea of how companies like Motorola (story) or SAP (story) are using the TWiki platform.
How is TWiki being deployed?
Companies are deploying TWiki in different ways, and TWiki is quite flexible to adapt to different needs. Here is a non comprehensive list of how TWiki is being used:
* To replace a static intranet. Content is maintained by the employees, thus eliminating the "one webmaster syndrome" of outdated and insufficient intranet content.
* As a knowledge base and FAQ system. The TWikiSuccessStoryOfTakeFive tells you more about that.
* To design and document software projects.
* To track issues (i.e. bugs) and features. TWiki itself is managed this way; more on that in TWiki.Codev.
* As a document management tool.
* To collaborate on common goals, i.e. the Helsinki Institute of Physics Technology Programme web portal.
* As a software archive, i.e. the TWiki Plugins archive.
* As a company internal message board, i.e. for job listings.
What are the Main Features of TWiki?
TWiki is a mature, full featured web based collaboration system:
* Any web browser: Edit existing pages or create new pages by using any web browser. There is no need for ftp or http put to upload pages.
* Edit link: To edit a page, simply click on the Edit link at the bottom of every page.
* Auto links: Web pages are linked automatically. You do not need to learn HTML commands to link pages.
* Text formatting: Simple, powerful and easy to learn text formatting rules. Basically you write text like you would write an e-mail.
* Webs: Pages are grouped into TWiki webs (or collections). This allows you to set up separate collaboration groups.
* Search: Full text search with/without regular expressions. See a sample search result.
* E-mail notification: Get automatically notified when something has changed in a TWiki web. Subscribe in WebNotify.
* Structured content: Use TWiki Forms to classify and categorize unstructured web pages and to create simple workflow systems.
* File attachments: Upload and download any file as an attachment to a page by using your browser. This is similar to file attachments in an e-mail, but it happens on web pages.
* Revision control: All changes to pages and attachments are tracked. Retrieve previous page revisions and differences thereof. Find out who changed what and when.
* Access control: Define groups and impose fine grained read and write access restrictions based on groups and users.
* Variables: Use variables to dynamically compose your pages. This allows you for example to dynamically build a table of contents: include other pages; or show a search result embedded in a page
|
|
We are building an open-content encyclopedia in many languages. Learn how to edit pages, experiment in the sandbox, and visit our Community Portal to find out how you can participate in the development of Wikipedia.
|
|
