Kashaneh policies

Submissions and Publishing Guidelines

Final version 1.0 | Effective 22 November 2026

Kashaneh welcomes writing, visual art, translation, research, audio, video, and other announced forms. Submissions and membership are free. Approved active members may submit throughout the year. A themed call may set an additional scope or deadline. Available media types and upload limits are shown in the form; a policy description does not enable a disabled feature.

Identified submissions and rights

Submission location is optional and editable, starting from the author's saved city/country. Select public display only if you want it shown with this work; it is off by default. Reviewers and administrators can correct the place text, but cannot enable public display against your choice. Change the location or its visibility from the work record, including after publication.

Review is identified. Authorized editors receive the author's name, account identifier, chosen publication name, work, AI-use category, and relevant rights and affiliation disclosures. There is no requirement to remove the author's name or accept anonymous review. Account identifiers are for internal administration and must not appear on the public publication page.

Submit only work you created or are authorized to submit. Identify co-authors, image creators, quotations, translations, sponsors, affiliations, and any permission required. At submission, read and accept the versioned work-specific Exclusive Publication Licence and attest to your authority. Copyright ownership remains with the author. Renew the recorded acceptance when a revision changes the work or rights materially; there is no separate final-proof acceptance step.

Select No AI use, AI-assisted, or AI-generated accurately. Both AI-assisted and AI-generated works are eligible. Tool names are optional. The disclosure is available to the editorial team and is not automatically public. You remain responsible for facts, citations, permissions, and the work's quality.

Two editorial reviews

A submission enters the editors' shared review queue directly. There is no preliminary editor screening stage. One editor picks up the identified work from the shared queue and records an Accept or Reject decision with a meaningful comment. Ordinary editors must declare a conflict of interest and cannot review their own work. The administrator exception below is explicit and recorded; it is not an assumption that a self-review is independent.

After a first-stage acceptance, the work is marked First Approved and returned to the shared editorial queue for a second review. In the ordinary editorial workflow this must be a different editor: a non-administrator who completed the first review cannot pick up or decide the second review. A second-stage acceptance approves publication directly. A rejection at either stage returns the work to the author with the decision comment and a route to revise or explain their disagreement. A submission does not go to a chief editor for mandatory final preparation and does not wait for author proofreading or final approval.

Each stage has one responsible editor and one decision. There is no committee vote, invitation-acceptance stage, or chief-editor tie-break. Editors see queue and workload information before picking up a work. The two deciding ordinary editors must be different. Administrators have the explicit exception described below.

Administrator authority and recorded exceptions

Administrators can grant or remove supported account roles, including the administrator role. A user is not an administrator merely because the interface shows a control; authorization and active account status are checked by the server, and privileged accounts require MFA.

An administrator may pick up and decide either review stage, complete both stages of the same work, and review their own submission. An administrator may explicitly take over a review already assigned to another editor. The interface must explain the exception or takeover before the action, and the system records the administrator, submission, stage, decision/comment, time, and previous assignee where applicable. Ordinary editors cannot use this exception. The normal two-stage state progression still applies unless staff use the separately recorded direct-publication route. Administrative review authority does not create copyright ownership or replace the work-specific licence or required rights evidence.

Private review of files and links

Authorized editors can inspect supplied images, audio, video, supported media links, and manuscript attachments within the private submission record. Uploaded material stays blocked until managed malware scanning confirms the exact immutable version is clean. Review previews are authenticated and limited to the authorized record; a preview or short-lived media URL does not make an unpublished work public.

Supported PDF files use a restricted inline viewer; TXT is displayed as escaped text; DOCX can be shown as safely extracted text without running macros, scripts, or embedded active content. Supported external media providers use controlled in-page players. An ordinary webpage or a provider that disallows embedding may instead offer a clearly labelled link to open it; not every supplied URL can safely become an iframe. Unsafe links, arbitrary embed HTML, scripts, and blocked or unscanned uploads must not be rendered. External providers may process a reviewer's connection information under their own privacy practices when a player or link is used.

Revisions, responses, and the same record

Revise or respond to a rejection using the existing submission record rather than creating a duplicate. Your explanation, the editorial comment, the current work, and the workflow history stay attached to the same identifier and return to the same responsible editor within the same editorial group. A response may explain why you disagree without requiring a change to the text. The editor responsible for the rejected stage considers the response and records the next decision. A second-stage revision keeps the first approval; it does not restart the first review. The dashboard identifies the current review stage and who has picked up the work.

While a work is being reviewed, request changes through its editorial thread. Staff can return it for editing. Authors cannot silently replace a version under active review. By default resubmission is allowed; a final decline that prevents further resubmission must be clearly identified and explained. Comments on submissions and editorial decisions remain in their associated records rather than a general member-to-member messaging system.

Publication, scheduling, and attribution

After second approval, the default publication date is today, using Kashaneh's Australia/Sydney operational date. An authorized editor may choose a future release date. Scheduled material remains private until that date. The recorded date and status must distinguish a scheduled work from one already public. No final user review is required.

Publication uses the original submitted language. Submit a translation separately. The page uses a light watermark-style Kashaneh frame and responsive text; the website controls final typography and spacing. The author's approved publication name appears with the work. The author biography and profile picture appear at the end, with a link to their public profile. Obtain the depicted person's permission and the image owner's permission before supplying a portrait. Private contact details and internal account IDs remain private.

Administrators and editors may create an attributed author record and publish directly without a member submission or the two review stages. They must record their authority to publish, the correct author or authorized publication name, and applicable rights evidence. Creating a profile does not create the author's consent, transfer copyright, or permit staff to impersonate an author. Direct publication, changes, scheduling, and overrides must be audited. Distribution to another channel depends on an enabled, configured integration and rights covering that channel; a website publication is not proof that another channel received it.

Preparing readable text

Editors may check and apply website-only formatting while preserving your words, quotations, poetry line breaks and original uploads. Formatting changes do not add editorial approvals or produce corrected downloadable Word files. AI-assisted social summaries are separate promotional drafts, in the original language by default; editors may request the other language. Branded covers reuse the approved header image or a text-only template. An editor or administrator must approve each current social package before automatic, scheduled or manual posting to the selected channels. This does not create a translated publication or change the author's AI-use declaration for the work.

Use the following defaults for a manuscript attachment; when pasting into the website use the matching semantic structure. The web page is responsive and does not preserve fixed paper pagination.

  • Page: A4 portrait, 2.5 cm margins on every side. Use a single column. Do not add decorative borders, background images, or the Kashaneh frame to the manuscript.
  • English body: a readable font such as Arial, Calibri, or Times New Roman, 12 pt. Persian body: Vazirmatn or Tahoma, 14 pt. Use Unicode text, correct Persian characters, and half-spaces where appropriate.
  • Main title: one title, approximately 20 pt for English or 22 pt for Persian. Use title or heading styles rather than enlarged spaces. The website supplies the single page H1; body headings start at H2 and proceed in order.
  • Section headings: English 16 pt and Persian 18 pt; subheadings: English 14 pt and Persian 16 pt. Do not skip heading levels or use bold text as the only section structure.
  • Body line spacing: 1.6 for English and 1.8–1.9 for Persian. Use paragraph spacing rather than repeated blank lines. Align English left and Persian right; avoid full justification and manual line breaks in normal prose.
  • Header and footer: leave empty for web publication. Do not place the title, author's name, contact information, running headings, or page numbers in repeating headers or footers. Put author and affiliation details in the dedicated form fields. A review-only PDF may have page numbers, but these are not part of the web article.
  • Quotes and poetry: use proper quotation or verse paragraphs. Explain any line breaks that are essential to the work. Do not use tabs, spaces, or screenshots to position text.
  • References: use a consistent citation method, identify sources, and provide descriptive links. Use real numbered or bulleted lists. Keep tables simple, with a header row; avoid wide spreadsheets inside the article.
  • Do not place essential writing inside an image or PDF alone. Provide selectable text so the article remains readable on phones, searchable, and accessible.

Text and document formats

The preferred submission is plain Unicode text in the website editor. Paste the title into the title field and the body into the body field; do not duplicate the title in the body. Separate paragraphs with a blank line; use ## Section heading for a second-level heading and ### Subheading for a third-level heading. Begin each list item on its own line with - . Raw HTML is never rendered. Preserve verse line breaks within a paragraph. Check the watermark frame at phone and desktop widths. The editorial team checks the publication layout before release; this does not create a final author-proof step.

If document uploads are enabled and the form lists them, provide an editable DOCX or UTF-8 TXT source. A PDF may accompany it as a visual reference; a PDF alone is not a substitute for accessible publication text. Other document and research-supplement formats, including ODT, CSV and XLSX, are not enabled in this release; ask the editors before sending them. Do not submit macros, executables, embedded scripts, password-protected documents, or unsupported archive formats. Do not rename a file extension to bypass a restriction.

File uploads are disabled by default and controlled separately by type. Every uploaded file must remain in quarantine until managed malware scanning reports a clean supported result. Failed, skipped, unsupported, oversized, encrypted, or unscanned files remain blocked. The form's current file-size and count limits take precedence over examples in this document.

Recommended defaults, when enabled: documents 10 MiB, images 2 MiB, audio 25 MiB and video 100 MiB per file. The form accepts one main media/manuscript attachment, one header image and a separate profile portrait. Administrators may adjust the supported limits to control cost. Large works should use an approved external host when practical.

Hero image and illustrations

Header images must be uploaded through the Proposed Header Image field; external header-image links are not accepted. Each publication can have a top image; for a video it also serves as the thumbnail or poster. Prefer a landscape image around 1600 × 900 pixels, in WebP, JPEG, or PNG. Aim for 500 KB or less when reasonable; preserve legibility and let the enabled upload limit govern. Supply meaningful alternative text, a caption where needed, and creator and permission credits. Do not include a large title or essential text in the picture, and do not stretch a portrait to fill a landscape slot.

Use inline illustrations only where they help the work. Keep a safe margin around important subjects because thumbnails may crop. Provide the separate author portrait at roughly 400 × 400 pixels, preferably below 150 KB, with permission to publish it. Never submit a photograph of another person as your own profile picture.

Audio and video

When enabled, provide a supported HTTPS external media link or a permitted direct upload. YouTube and other supported embed providers play within the publication page; a provider that prohibits embedding may require a supported replacement. A normal webpage URL is not necessarily a playable media file. Never paste arbitrary iframe, script, or embed HTML into the submission.

Recommended delivery: MP4 with H.264 video and AAC audio, up to 1080p; MP3 or M4A for audio, with WAV accepted only when enabled and necessary. Provide the title, creator, duration, language, a poster image, captions for speech in video, and a transcript or equivalent text. Playback is user initiated; do not request autoplay. External players contact their own providers and are subject to those providers' privacy practices. Direct uploads follow the same quarantine and clean-scan requirement as other files.

Dates, reports, and editorial privacy

Persian-facing publication and workflow dates use the Persian Imperial calendar: the Solar Hijri year plus 1180, retaining the same month and day. For example, 23/08/1405 is displayed as 23/08/2585. Calendar display does not change the stored instant or the scheduled release timezone. English-facing dates use the stated Gregorian date.

Editors may see active submission counts, current stages, picked-up work, queue sizes, and completed-work totals to balance workload. Authorized staff may use graphs and export reports. Reports contain confidential operational information and must not be published, shared through a public link, or retained longer than necessary. A queue count is a workload indicator, not an automatic ranking of editorial quality.

Exclusivity waiver and contact

Authors keep ownership and may request a waiver of exclusivity at any time, including after publication. The chief editor and one administrator must both approve. Once approved, authors may publish elsewhere; Kashaneh may retain the existing published work under the non-exclusive archive permission in the licence. A waiver is not automatic removal from the site.

Use the submission thread for a revision, response, rights question, or correction. Essential account and workflow notices stay enabled; optional communication preferences may be changed. See the Privacy Notice, Website and Member Terms, Exclusive Publication Licence, and Editorial Complaints and Corrections policy. These guidelines apply to work submitted on or after their effective date.