Change Details

Some extensions are dependent on in-wiki content (e.g. templates, semantic forms, etc.). Such extensions now rely on users importing or creating this content manually in the wiki. An idea, discussed at SMWCon Fall 2017, is to have a mechanism to directly serve contents from static sources (i.e. files) bundled with an extension. Some benefits of this approach would be: - installing an extension automatically makes available the required wiki pages - when the extension is under revision control (e.g. in git), the wikicontents are under the same revision control - this approach would also allow extension developers to produce extension documentation that could be directly viewed from within the wiki (and is always up to date with the actually installed extension version)

Some extensions are dependent on in-wiki content (e.g. templates, semantic forms, etc.). Such extensions now rely on users importing or creating this content manually in the wiki. An idea, discussed at SMWCon Fall 2017, is to have a mechanism to directly serve the content of static sources (i.e. files) bundled with an extension. Some benefits of this approach would be: - installing an extension automatically makes available the required wiki pages - when the extension is under revision control (e.g. in git), the wikicontents are under the same revision control - this approach would also allow extension developers to produce extension documentation that could be directly viewed from within the wiki (and is always up to date with the actually installed extension version)

Some extensions are dependent on in-wiki content (e.g. templates, semantic forms, etc.). Such extensions now rely on users importing or creating this content manually in the wiki. An idea, discussed at SMWCon Fall 2017, is to have a mechanism to directly serve the contents from of static sources (i.e. files) bundled with an extension. Some benefits of this approach would be: - installing an extension automatically makes available the required wiki pages - when the extension is under revision control (e.g. in git), the wikicontents are under the same revision control - this approach would also allow extension developers to produce extension documentation that could be directly viewed from within the wiki (and is always up to date with the actually installed extension version)