Salisbury Post
newspaper in Salisbury, North Carolina
The Salisbury Post is an American, English-language daily newspaper, founded in 1905, in Salisbury, North Carolina that serves the city and other municipalities in Rowan County, as well as the county itself. The publisher of the Post is John Carr and its editor is Chandler Inions. The paper was known as the Salisbury Evening Post (1905–1984).
History
The Salisbury Post debuted as The Salisbury Evening Post on January 9, 1905, and immediately proclaimed itself as "Salisbury's Leading Afternoon Newspaper."
J. B. Doub, E. C. Arey and Gabe M. Royal launched the newspaper at 114½ North Main Street, on the floor over G.A. Jackson's saloon. Joe X. Roueche and Clint N. Brown, former owners and publishers of the competing Salisbury Daily Sun, soon bought the Post and moved the operation across North Main Street to occupy the second floor of the old Meroney Opera House. A fire destroyed the Meroney Opera House on the morning of May 12, 1912, and took every vestige of equipment and record of the Post. But the newspaper kept publishing, as the editorial and mechanical staffs traveled to Spencer and used the office of A.W. Hicks, publisher of a small weekly.
Meanwhile, Roueche and Brown began negotiating the sale of the Post to a group of investors led by James Franklin Hurley, a former owner of The Concord Tribune. The change in ownership became official on July 22, 1912, and the Post moved back to Salisbury and began publication in the Shaver Building at 110 W. Innes St. Hurley served as both editor and publisher.
The public source identifies “Salisbury Post” as newspaper in Salisbury, North Carolina. This brief keeps that definition visible, then builds a research path around Salisbury, Post and newspaper.
Why this record matters
A short description can identify a subject without explaining its stakes. For “Salisbury Post”, the useful work is to connect “newspaper in Salisbury, North Carolina” to the records capable of establishing context and consequence.
Named sources, stable identifiers and responsible institutions provide the strongest route from overview to verifiable evidence. The source revision retrieved here is dated Sep 17, 2026. The linked authority identifier is Q7404799. 2 of 2 selected statements include explicit references; 1 carry qualifiers and 0 use preferred rank. The first chronological checks are 1905, 1984 and 1912.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Salisbury Post”, its source revision and the description used here.
- Expand the search: follow Salisbury Post primary sources, Salisbury Post archive and Salisbury 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 “Salisbury Post”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Salisbury Post” 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.