Slash (software)
the content management software used by website Slashdot
Slash (Slashdot-Like Automated Storytelling Homepage) is a content management system, originally created for Slashdot, one of the oldest collaborative sites on the Internet. Slash has also been known as Slashcode.
Slash is a set of modules, plugins and applets — scripts or programs executed by the server — written in Perl.
History
Early versions of Slash were written by Rob Malda, founder of Slashdot, in the spring of 1998. Andover.net bought Slashdot in June 1999. Work was done by Brian Aker, Patrick Galbraith and Chris Nandor, resulting in version 2 of the software, released in 2001. Until 2009, Slash was maintained by Jamie McCarthy and Chris Nandor, among others. The original codebase was abandoned in September 2009.
Rehash remains primarily under the GNU General Public License and anyone can contribute to development.
SoylentNews
SoylentNews is a fork of Slashdot using a 2009 fork of the Slashdot engine.
The public source identifies “Slash (software)” as the content management software used by website Slashdot. This brief keeps that definition visible, then builds a research path around Slash, software and content.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Slash (software)”, the useful work is to connect “the content management software used by website Slashdot” to the records capable of establishing context and consequence.
The date and method of observation matter as much as the stated conclusion, especially where classification or consensus has changed. The source revision retrieved here is dated Dec 23, 2025. The linked authority identifier is Q6130350. 1 of 1 selected statements include explicit references; 0 carry qualifiers and 0 use preferred rank. The first chronological checks are 1998, 1999, 2001 and 2009.
Current terminology should not be projected backward without checking the classification used when the underlying evidence was created. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Check terminology, classification and the date of the cited evidence. Scientific names and technical consensus can change while older records retain historical value.
- Current terminology
- Classification context
- Finding cited technical literature
Primary datasets, specimen catalogues, standards bodies and the most recent peer-reviewed literature.
Three-step research path
- Establish the record: confirm the title “Slash (software)”, its source revision and the description used here.
- Expand the search: follow Slash (software) primary sources, Slash (software) archive and Slash research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Slash (software)”?
- Is the terminology current, historical or disputed?
- Has classification or technical consensus changed since the cited source?
Search terms from this dossier
This entry incorporates text from “Slash (software)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.