RFP Kit

Tender responses in hours, not weeks.

Q: Frequently asked questions

May I copy the catalogue into a tender response? Yes. The catalogue is explicitly designed for this. Please reach out briefly before submission so we can align on version and, if needed, add refined acceptance criteria. How current is the catalogue? The revision date is in the YAML frontmatter (`revision_date`). We update the catalogue at every release cut. For a dated version at the moment of submission we'll happily send a signed copy. What licence applies to the catalogue? The content is cleared for use in tender processes and product evaluations. Redistribution as your own work is not permitted; pointers back to lernhive.de are welcome. Is there a structured JSON version? On request. The Markdown version is deliberately primary — it stays human-readable while being structured enough for agents. A JSON derivative is delivered on concrete demand. Can acceptance criteria be extended per project? Yes. As part of a partner call we gladly add tender-specific criteria (e.g. concrete response times, integration with existing SSO providers, specific export formats).

A machine-readable feature catalogue for tender desks, specification teams and AI agents. Each building block ships with a YAML header covering release, dependencies, Flavours and compliance tags — plus bilingual summary, capability bullets and acceptance criteria. Ready to use, to copy, to filter.

Download catalogue (.md) Open in browser See preview

What's in the kit.

A single Markdown file of around 800 lines — small enough to fit directly into an AI agent's context window; structured enough to be filtered programmatically.

19 Building blocks catalogued

2 Languages in one file (DE/EN)

5 Release stages (R1 / R2 / live / LXP / scope)

6 Compliance tags (GDPR, ISO 27001, WCAG 2.2 AA, BITV, BFSG, EN 301 549)

◉

YAML header per building block

Every entry starts with a YAML block: id, component, category, release, maturity, dependencies, flavours, compliance, tags. Machine-readable without HTML parsing.

◐

Bilingual in one file

German summary, English summary, capability bullets in both languages, bilingual acceptance criteria. No second download, no sync gap.

◈

Compliance hooks

Every building block lists relevant compliance tags directly in YAML. 'Which building blocks are BFSG-relevant?' — one regex is enough.

★

Acceptance criteria per building block

Where possible: measurable acceptance criteria (e.g. 'Search returns matches within 100 ms for ≤1,000 commands'). Copy-ready for specifications.

Three typical workflows.

The kit is deliberately lean — a single Markdown text. That enables a range of usage paths.

1. Feed an AI agent Load the file into an agent (Claude, GPT, internal system). Prompt: 'Based on this catalogue, generate chapters 3.2 through 3.8 of our specification.' The agent already knows releases, dependencies and compliance tags.

2. Filter for a tender Only R1 blocks? Only BFSG-relevant components? Only 'lxp' Flavour blocks? Because all metadata sits in YAML, a short script — `grep`, `yq` or one line of Python — is enough to extract a targeted subset.

3. Copy directly Open, search, copy — capability bullets and acceptance criteria are written so they fit directly into specifications, project briefs or requirement backlogs without rephrasing.

Structure at a glance.

This is what an entry looks like: YAML header, bilingual summary, capabilities, acceptance criteria. Below: two real examples from the catalogue.

Document frontmatter

---
document: LernHive RFP Feature Catalogue
vendor: eLeDia GmbH
product: LernHive
delivery_model: Managed SaaS
hosting_regions: [DE]
compliance: [GDPR, ISO27001]
platform_foundation: Moodle 5.x (ohne Fork / without fork)
languages_supported: [de, en]
licensing_model: subscription-per-monthly-active-user
canonical_terminology:
  plugin_marketing: Baustein / Building block
  plugin_technical: Plugin (Moodle component)
---

Two example entries

R1 productive GDPR ISO 27001 WCAG 2.2 AA

2.1 Plattform-Basis / Platform Foundation

id: platform
component: local_lernhive
category: foundation
release: R1
maturity: productive
dependencies: []
flavours: [school, lxp, all]
compliance: [gdpr, iso27001, wcag-aa]
required_by: all_other_building_blocks

Foundation building block. Ships the five-tier level system (Explorer → Creator → Pro → Expert → Master), the feature registry for configurable level rights, and the shared UI classes used by every building block surface. The invisible backbone carrying all other building blocks.

R1 productive GDPR WCAG 2.2 AA

2.3 ContentHub

id: contenthub
component: local_lernhive_contenthub
category: foundation
release: R1
maturity: productive
dependencies: [local_lernhive]
flavours: [school, lxp, all]
compliance: [gdpr, wcag-aa]

Unified entry screen for content creation. One dialog answers the question "Where does your content come from?" and hands off to the responsible building block: blank course, copy, library import, template or AI generator. No content logic of its own — pure orchestration.

Full catalogue overview.

The 21 building blocks, grouped by category — release status visible at a glance.

No.	Building block	Category	Release
2.1	Platform Foundation	Foundation	R1
2.2	Launcher	Foundation	R1
2.3	ContentHub	Foundation	R1
2.4	Course Copy Wizard	Foundation	live
2.5	Library	Foundation	live
2.6	Flavours	Configuration	R1
2.7	Configuration History	Configuration	R1
2.8	Onboarding	Guidance	R1
2.9	Context Helper	Guidance	R1
2.10	Explore	LXP	R1-LXP
2.11	Follow & Bookmark	LXP	R1-LXP
2.12	Digest & Notifications	LXP	R1
2.13	Audience	Targeting	R1
2.14	Reporting	Analytics	live
2.15	Skills & Learning Plans	Pathways	R2
2.16	Orgchart	Structure	live
2.17	Seminar Management	Scope	Scope
2.18	LernHive Theme	Surface	R1
2.19	Snacks & Communities	Course formats	R2
2.20	Learning Pathways	Pathways	live
2.21	Certify	Pathways	live

Cross-cutting chapters

Beyond the building block catalogue the file carries cross-cutting sections on accessibility (WCAG 2.2 AA, BITV, BFSG, EN 301 549), privacy (GDPR, Privacy API, retention), security (ISO 27001, TOMs, ISMS), exportability (open formats, no lock-in), integration (SSO, SCIM, xAPI/cmi5) and language support.

Frequently asked questions

May I copy the catalogue into a tender response? Yes. The catalogue is explicitly designed for this. Please reach out briefly before submission so we can align on version and, if needed, add refined acceptance criteria.

How current is the catalogue? The revision date is in the YAML frontmatter (`revision_date`). We update the catalogue at every release cut. For a dated version at the moment of submission we'll happily send a signed copy.

What licence applies to the catalogue? The content is cleared for use in tender processes and product evaluations. Redistribution as your own work is not permitted; pointers back to lernhive.de are welcome.

Is there a structured JSON version? On request. The Markdown version is deliberately primary — it stays human-readable while being structured enough for agents. A JSON derivative is delivered on concrete demand.

Can acceptance criteria be extended per project? Yes. As part of a partner call we gladly add tender-specific criteria (e.g. concrete response times, integration with existing SSO providers, specific export formats).

Read the catalogue, then talk.

Download the Markdown file and look at the blocks relevant to your tender. When you'd like a partner call afterwards — happy to come prepared with concrete specification passages — we'll reply within 48 hours.

Download catalogue Partner talk