egroupware/doc
2024-09-30 10:11:00 +02:00
..
docker Wait 5 instead of 3 seconds between installation attempts, as sometimes 10*3=30s is not enough for the DB to get ready on new installs 2024-09-23 17:44:50 +02:00
etemplate2 Import bootstrap CSS for docs 2024-09-09 10:20:46 -06:00
IDE
ldap
mail
REST-CalDAV-CardDAV
rpm-build fix Hunk/offset in async-service patch 2024-09-30 10:11:00 +02:00
scripts
ad-migration.sh
add_et2_dtd.sh
analyse-warnings.php
check_namespace.php
check-metadata.php
config2xet.php
dovecot-mailbox-status-compare.php
Entry change push update.drawio
Entry change push update.pdf
etemplate2-rng.php
fix_api.php
fix_depricated.php
fix-8.1-depricated-interfaces-return-vals.php
import-mail-credentials.php
js2ts.php
lang_files.txt
ldif2sql.php
LICENSE
links-www.egroupware.org.txt
lotus-structured-text2csv.php
merge-cal-events-by-uid.sh
new-egw-app.php
php_syntax_check.sh
phpunit_bootstrap.php
phpunit.xml
README-dirs-less-css
README.md
test-cli.php
travis-ci-apache.conf
UCS-SAML-SSO.md

Notes on automatic documentation

This is a project in itself. Here's how the pieces fit together:

  • build:dev package script calls /doc/scripts/build.mjs which is responsible for calling the individual pieces. We pass files to the subprocesses, but options are set in a separate config file.
  • /doc/scripts/metadata.mjs extracts the component information using CEM, and stores it to /doc/dist/custom-elements.json
  • /doc/scripts/etemplate2/eleventy.config.cjs uses 11ty to build a documentation site, from the subdirectories in /doc/etemplate2, and stores it to /doc/dist/site

If a component doesn't show up, it's probably not in the manifest.