Skip to content
LinkPress™
LegalCommunity

Community & Editorial Policy

Our editorial standards, contribution guidelines, code of conduct, accuracy policy, and complaints procedure — in one place.

Last updated: May 19, 2025Jurisdiction: Germany / EUOpen-Source
Part 1: Editorial ResponsibilityPart 2: Contribution Guidelines

Part 1: Editorial Responsibility

Standards for accuracy, independence, attribution, and how we handle corrections and complaints.

Editorial Contents

  1. 01Our Editorial Mission
  2. 02Editorially Responsible Person
  3. 03Accuracy & Corrections
  4. 04Editorial Independence
  5. 05Sources & Attribution
  6. 06Complaints & Press Enquiries
  7. 07Right of Reply
  8. 08Archive Policy
01

Our Editorial Mission

LinkPress™ exists to help business professionals think more clearly, lead more effectively, and act with greater intentionality. Our editorial mission is to publish content that is accurate, independent, practically useful, and respectful of our readers' time and intelligence.

02

Editorially Responsible Person

The person responsible for all editorial content published on https://linkpress.app under § 55 Abs. 2 RStV is Mithun A. Sridharan, based in Heidelberg, Germany. Questions about specific articles, corrections, or complaints should be directed to [email protected].

03

Accuracy & Corrections

Fact-checking — All factual claims in our editorial content are verified before publication. We cross-reference primary sources, official documentation, and reputable secondary sources.
Corrections policy — When errors are identified — by our team or by readers — we correct them promptly and transparently. Corrections are noted inline within the affected article, with the date of correction.
Reporting errors — If you spot a factual error, a broken link, or outdated information, please email [email protected] with the article URL and the specific issue. We appreciate every report.
Retractions — In rare cases where an article cannot be corrected without substantially changing its meaning or is found to be fundamentally misleading, we will publish a retraction notice.
04

Editorial Independence

Separation of church and state — Editorial decisions are made independently of commercial relationships. Advertisers, sponsors, and vendors cannot influence article content, tone, or conclusions.
No pay-to-play coverage — We do not accept payment for positive reviews, rankings, or editorial features. Our vendor directory and product recommendations reflect genuine editorial judgement.
Sponsored content — Any sponsored or paid content is clearly labelled as "Sponsored" or "Partner Content" at the top of the article. Sponsored content is written to our editorial standards but represents the sponsor's viewpoint.
Affiliate links — Where we use affiliate links (e.g. for tools we genuinely recommend), this is disclosed at the top of the relevant article. Affiliate relationships do not influence editorial recommendations.
05

Sources & Attribution

Primary sources — We prefer to link directly to primary sources: official documentation, peer-reviewed papers, company announcements, or first-hand accounts.
Attribution — All quotations, data, charts, and non-original materials are attributed to their source with a link where one exists. We do not reproduce substantial portions of others' work without permission.
AI-assisted content — Where generative AI tools are used to assist in drafting or research, the final article is reviewed, fact-checked, and edited by a human editor before publication. AI-generated content is not published unreviewed.
06

Complaints & Press Enquiries

We take complaints about our editorial content seriously. If you believe we have published inaccurate, misleading, defamatory, or otherwise problematic content, please contact us at [email protected] with a clear description of the issue. We aim to respond to all editorial complaints within 5 business days.

07

Right of Reply

Individuals or organisations that are the subject of critical coverage on this site have the right to submit a factual response for publication. We will publish factually accurate responses that address specific claims in the original article. Contact us at [email protected] to request a right of reply.

08

Archive Policy

We maintain an archive of all published articles. We do not delete articles from our archive except in cases of legal necessity, fundamental inaccuracy, or editorial retraction. Deleted or substantially changed articles are noted with a visible notice.

Part 2: Contribution Guidelines

How to contribute code, content, or feedback — and the standards we hold ourselves and contributors to.

Contribution Contents

  1. 01Welcome, Contributor
  2. 02Code of Conduct
  3. 03Types of Contribution
  4. 04Guest Contributors
  5. 05Content & Writing Standards
  6. 06Getting Started
  7. 07Pull Request Guidelines
  8. 08Coding Standards
  9. 09Licensing of Contributions
  10. 10Review Process & Timeline
01

Welcome, Contributor

LinkPress™ is made better by its community. Whether you're submitting a bug fix, proposing a new feature, writing an article, or simply opening a well-crafted issue, your contribution matters. These guidelines help us maintain quality, consistency, and a welcoming environment for everyone.

02

Code of Conduct

Be respectful — Treat all contributors with respect regardless of experience level, background, or viewpoint. Constructive disagreement is welcome; personal attacks are not.
Be constructive — When reviewing code or content, focus on the work — not the person. Explain your reasoning. Good feedback includes suggestions for improvement.
Be inclusive — We welcome contributors from all backgrounds. Use inclusive language. Avoid jargon that excludes newcomers unless you explain it.
Consequences — Violations of this Code of Conduct may result in contributions being rejected, comments being removed, or the contributor being blocked from the project. Report issues to [email protected].
03

Types of Contribution

Bug reports — Found something broken? Open an issue with a clear title, steps to reproduce, expected vs actual behaviour, and your environment (browser, OS, version).
Feature requests — Have an idea? Open a discussion or issue explaining the use case, the problem it solves, and any alternative approaches you considered.
Code contributions — Pull requests are welcome for bug fixes, performance improvements, and features that have been discussed and accepted in an issue first.
Documentation — Typos, unclear explanations, missing examples — documentation PRs are among the most valuable contributions and are always welcome.
04

Guest Contributors

Pitching an article — Pitch your idea to [email protected] with a 2–3 sentence summary before writing the full piece. We commission based on relevance, originality, and the author's relevant experience.
Editorial standards — Guest articles are subject to the same editorial standards as staff-written content: factual accuracy, relevance, and independence. We edit for clarity and accuracy.
Disclosure of conflicts — Guest contributors must disclose any financial, professional, or personal interests that could be perceived as influencing their article.
Bylines — Guest articles are published under the contributor's name with a brief bio. Ghostwriting for third parties is not permitted.
05

Content & Writing Standards

Audience — Write for informed business professionals. Assume familiarity with general business concepts but explain specialised or technical terms on first use.
Tone — Direct, clear, and conversational — not academic. Prefer active voice. Keep sentences under 25 words where possible.
Length — Articles should be as long as they need to be and no longer. Aim for depth over breadth.
Examples — Practical examples, case studies, and real-world applications are highly valued. All factual claims and data must be verifiable and accurate.
Citations — Link to primary sources. Do not reproduce substantial portions of third-party content without permission.
06

Getting Started

Fork and clone — Fork the repository on GitHub, clone your fork locally, and create a new branch for your change: `git checkout -b feat/your-feature-name`.
Install dependencies — Run `pnpm install` to install dependencies. We use pnpm as our package manager; please do not switch to npm or yarn.
Run locally — Start the dev server with `pnpm dev`. The site will be available at http://localhost:4321.
Run tests — Run `pnpm test` before submitting your PR. All tests must pass. Add tests for new functionality where applicable.
07

Pull Request Guidelines

One change per PR — Keep PRs focused on a single concern. Large, multi-purpose PRs are harder to review and more likely to be rejected or delayed.
Descriptive title & description — Use a clear PR title (e.g. "fix: correct broken link in footer"). In the description, explain what changed, why, and how to test it.
Reference issues — If your PR closes an issue, include "Closes #123" in the description so it is automatically linked and closed on merge.
Keep commits clean — Use conventional commit messages (feat:, fix:, docs:, chore:, refactor:). Squash work-in-progress commits before requesting review.
Pass CI — All automated checks (lint, type-check, tests, build) must pass before a PR will be reviewed.
08

Coding Standards

TypeScript — All new code must be written in TypeScript with strict mode enabled. Avoid `any` types.
Astro components — Follow the existing component structure. Props interfaces must be explicitly typed. Use semantic HTML.
CSS — Use Tailwind utility classes where possible. Avoid inline styles. Custom CSS goes in the relevant `.css` file in `src/styles/`.
Accessibility — New UI components must meet WCAG 2.1 AA standards. Use semantic elements, provide ARIA labels where needed, and test keyboard navigation.
Performance — Avoid adding unnecessary dependencies. Images must use the Astro Image component. Lazy-load off-screen content.
09

Licensing of Contributions

By submitting a contribution to this project, you agree that your contribution is licensed under the same terms as the project (MIT License for code; editorial copyright for written content). You confirm that you have the right to submit the contribution and that it does not infringe third-party rights.

10

Review Process & Timeline

We aim to acknowledge all PRs and issues within 5 business days. Reviews may take longer during busy periods. If your contribution has not received a response within 10 business days, feel free to ping us at [email protected]. We are a small team and genuinely appreciate your patience.

Get in Touch

For corrections, complaints, press enquiries, article pitches, or questions about contributing:

[email protected]

We aim to respond to all enquiries within 5 business days.