Truth Before Texture
Style matters, but it cannot rescue weak facts. Verify the concrete details first; polish comes after the piece knows what it is saying.
A practical charter for essays, reports, blogs, issue pieces, posters, submissions, corrections, and the admin decisions that decide what becomes public.
The goal is not to sound important. The goal is to be useful, readable, accurate, and alive. A strong Epigram piece should help someone understand a debate, a campus event, an argument, a book, a policy, a cultural moment, or the work of the society with more clarity than they had before opening it.
Style matters, but it cannot rescue weak facts. Verify the concrete details first; polish comes after the piece knows what it is saying.
Opinion is welcome when it is argued. A strong claim needs reasons, examples, and an honest sense of what a thoughtful reader might object to.
Reports should make public life clearer, not turn students into spectacle. Write about actions, decisions, records, and accountable public roles.
The house tone is confident, plain, observant, and humane. Avoid inflated language, fake grandeur, filler, and borrowed prestige.
Readable typography, useful headings, image descriptions, captions, and mobile layout are not decoration. They decide who can read the work.
Editors should classify work correctly before review. A report is not an opinion piece. A blog is not a press release. A poster is not a substitute for context.
Best for campus life, debate culture, student initiatives, public events, interviews, and researched explainers.
Best for interpretation, criticism, response, campus argument, public affairs, debate analysis, and cultural reflection.
Best for personal reflections, reading notes, informal cultural commentary, and timely responses.
Best for competitions, open debates, workshops, screenings, collaborations, forums, and campus events.
Best for bundled editorial work, recurring columns, special projects, PDF issues, and themed releases.
Best for interviews, podcasts, debate recordings, livestreams, highlight clips, and broadcast explainers.
Editors should not have to guess the author's name, the intended section, whether an image can be used, or what the piece is trying to do. If a contributor is new, the form should guide them; if a contributor is experienced, the standards should challenge them.
A pitch should identify the subject, angle, format, likely sources, and why Epigram's readers should care. "I want to write about debate" is not an angle. "What open debates teach first-year speakers about losing well" is closer.
Editors may improve structure, rhythm, and headline language. They should not have to rescue a piece that has no thesis, no facts, and no sense of audience.
Upload JPG, PNG, or WebP files that are clear, relevant, and publishable. If a poster has text, the article should still include the key details in actual page text.
Work must be original or properly credited. Images must be owned by the contributor, cleared by the organizer, created by Epigram, or licensed for publication.
Epigram's editorial standard is not stiffness. It is control: every paragraph earns its space, every claim knows its basis, and every flourish has a job.
Open with the subject, the tension, the scene, or the question. Do not spend the first paragraph warming up.
The reader should be able to say what the piece is about after the first few paragraphs.
Use sections, turns, and transitions. A list of thoughts is not a structure.
Support claims with observation, documents, interviews, data, direct experience, or careful reasoning.
Prefer sharp plain language over inflated language. Sound like a thoughtful person, not a poster caption.
End by clarifying the consequence of the piece. Avoid sudden moral summaries that could belong to any article.
The easiest way to lose reader trust is to mishandle a small fact. Editors must check the small facts because readers use them to judge the larger work.
Use the person's preferred public name and correct role.
Readers use these details as the public record.
Quotes must preserve meaning and not create a false impression.
Numbers invite authority. They need a source.
Serious claims require serious handling.
Epigram can be lively without being careless. Criticism should be aimed at work, public decisions, arguments, performances, institutions, and accountable roles. Avoid turning private students into props for public writing.
Disclose if the author, editor, photographer, or approving admin is directly involved in the event, team, campaign, dispute, or publication subject. Disclosure does not always prevent publication; secrecy does.
Do not publish private contact details, medical information, personal accusations, classroom incidents, or sensitive images without a clear public-interest reason and senior editorial approval.
When a piece makes a serious criticism of a named person, office, organization, or event team, give them a fair chance to respond before publication whenever possible.
If a published piece contains an error, correct it promptly. For substantive changes, add a correction note with what changed and when.
Remove or unpublish only for strong reasons: legal risk, privacy risk, clear factual failure, rights issues, duplicate publication, or a decision by senior editors.
Use precise, inclusive language. Do not rely on stereotypes, slurs, personal attacks, or jokes that ask marginalized people to carry the cost of the sentence.
Images should help the reader understand the work. The page must still carry the essential details in text for search, accessibility, and clarity.
Use JPG for posters when possible. PNG and WebP are acceptable for artwork, screenshots, and web images. Avoid tiny, blurred, stretched, or heavily compressed files.
Use images created by Epigram, submitted by the author, cleared by an event organizer, or licensed for publication. Do not use random social media images without permission.
Captions should identify the event, people if relevant, photographer or source, and date when known. Do not caption with vague hype.
Alt text should describe what is visually important. If a poster contains essential text, repeat that information in the article body as well.
Do not publish edits that mislead the reader about what happened. Cropping, exposure correction, and layout preparation are fine; invented evidence is not.
Credit photographers, designers, organizers, and partner institutions when the information is available.
The workflow should be simple enough for students to use and strict enough that public pages do not become an unreviewed upload board.
Submission enters the public portal or is created by an editor in the admin portal.
Editor checks format, relevance, rights confirmation, image quality, and whether the piece belongs in Articles, Blog, Reports, Issues, or Airwaves.
Editor checks thesis, structure, clarity, tone, facts, sources, quotes, and any conflicts of interest.
Contributor revises when the piece needs additional reporting, clearer argument, proof, captions, or permissions.
Editor fixes headline, deck, paragraph rhythm, grammar, style, tags, section, slug, excerpt, and image alt text.
Senior editor or authorized admin confirms the piece is ready and publishes or schedules it.
Social caption, poster, Instagram story, newsletter line, or Airwaves tie-in should match the published piece accurately.
Published work should remain findable by title, author, section, date, content type, and related event where relevant.
Any admin who makes text, article content, reports, posters, images, event listings, or publication issues visible to visitors is responsible for the checklist below.
Choose the correct destination: article, blog, report, publication issue, event, notice, broadcast, or resource. Do not publish everything as a generic article.
Confirm the item is meant to be public. Pending submissions and drafts should remain offline until approved.
Use a specific title and a short summary. Avoid all caps, vague slogans, and summaries that repeat the title.
Upload the correct JPG, PNG, or WebP. Check that it renders, has alt text, and matches the content being published.
For events and reports, verify the date, time, venue, organizer, division, and whether the event is upcoming or past.
Use tags readers can actually browse: Debates, Campus, Opinion, Reports, Airwaves, Events, Workshops, Interviews, or Issues.
Test YouTube, Spotify, PDF, article, social, form, and external links before publishing.
Open the public page after saving. Check mobile layout, title wrapping, image crop, and whether the item appears in the right archive.
The house style should help readers move through the site without noticing friction.
Spell names exactly as the person publicly uses them. Confirm class, department, and office before publishing.
Use day, date, month, and year for event reports when possible. Avoid vague dating such as "recently" unless the piece is deliberately informal.
Use clear, specific headlines. A headline should tell the reader the subject or argument, not just the mood.
Use one or two sentences that add context. Do not repeat the headline with different adjectives.
Do not clean quotes so aggressively that the speaker sounds unlike themselves. Light edits for clarity are acceptable when meaning is preserved.
Link to primary sources, related Epigram pages, partner pages, public forms, PDFs, and recordings where useful.
Use official names for Epigram, St. Joseph's University, Epigram Publications, Epigram Airwaves, and named events.
Publish the length the piece earns. Short is acceptable. Long is acceptable. Padded is not.
Epigram should publish work that has a human author accountable for the argument, facts, sources, and final language.
Grammar checks, outline support, transcription cleanup, formatting help, headline brainstorming, and translation assistance when reviewed carefully by the author.
Substantial machine assistance in drafting, translation, image generation, data summary, or interview transcription should be disclosed to the editor.
Fabricated quotes, invented sources, generated reporting, undisclosed ghostwritten submissions, fake images presented as documentary evidence, or work the author cannot explain.
This is the practical checklist editors and admins should use before approving any article, blog, report, issue, event feature, or media post.
Use the submission portal for new work, the admin portal for review, and the contact page for collaboration, corrections, or rights questions.