Docs are there.
They aren't, only index.html.
ownCloud 10.1.0 Community and Enterprise bundles.
In the old versions 10.0.10 of the tarballs the docs are there.
Since we migrated to a new documentation format, we'll need extra steps to make sure the documentation is correctly bundled as it was before.
Now bundling the new one is likely not only a matter of putting the files there, we should also check that it properly renders in the UI.
Alternatively we could also decide to remove the bundled documentation altogether.
The various links inside of ownCloud are already pointing at the online documentation instead of the bundled one.
@settermjd @pmaier1 @hodyroff thoughts ?
GitMate.io thinks possibly related issues are https://github.com/owncloud/core/issues/12665 (Docs), https://github.com/owncloud/core/pull/31265 (Fix missing exception doc), https://github.com/owncloud/core/issues/55 (Missing translation), https://github.com/owncloud/core/issues/66 (Icons missing), and https://github.com/owncloud/core/issues/21164 (Admin manual missing from releases).
@tboerger @settermjd the docs used to be built as part of the release process by running the scripts from the Makefile from https://github.com/owncloud/documentation
Should we add Antora / docker / etc and everything needed to the old release script to build the HTML admin and user docs for bundling, or should the docs be prebuilt and delivered for download under a known URL ? (maybe zip or tar that can be extracted during release build)
This is how it looks like for 10.1.0 on my server:

the third alternative is removing the bundled docs and have the "Help" menu entry on the top right point directly at the online docs...
I had a quick look and it looks like the antora docs currently would build all of the manuals, not only admin or user. Also there will likely be a problem with URLs as those would expect to be deployed under a specific subfolder. These need to be remapped at build time to allow for deploying inside of OC.
From my understanding this might need an alternative site.yml specific to the OC build ?
@PVince81, I'll see what I can do to make the bundled docs gr8 again!
I'm experimenting with updating core's Makefile to build the docs locally. However, if it takes too long, likely the best solution would be just to point to the online docs. They have a whole build pipeline after all.
Actually, thinking about it further, why not just take the simplest path and link directly to the online docs? No need to maintain the docs in two places.
Actually, thinking about it further, why not just take the simplest path and link directly to the online docs? No need to maintain the docs in two places.
this would be a PM decision as there might have been reasons to bundle the docs in the past, maybe for offline instances.
@pmaier1 @hodyroff what do you think ?
Actually, thinking about it further, why not just take the simplest path and link directly to the online docs? No need to maintain the docs in two places.
:+1: the bundled docs will be out dated the day we ship them in the release. And they will stay there for years. Kill them!
as discussed with @pmaier1 and @cdamken we decided to not bundle it any more.
it's not used in EE, only CE.
I'll take care in next sprint, there's some code in core to delete...
@sharidas please take care. compare EE with CE in terms of bundled docs and then delete all related code in CE so that the section disappears, just like on EE.
EE does not have:
CE does have:
Objective:
Help from the CE.Created PRs here:
we still have this PR for rewiring the doc links: