Google Git
Sign in
apache / db-jdo-site / 889c623e951e0a27fbc1c189832d255e74b9a16b
commit889c623e951e0a27fbc1c189832d255e74b9a16b[log] [tgz]
authorTilmann <zoodb@gmx.de>Tue Dec 03 00:02:10 2019 +0000
committerTilmann <zoodb@gmx.de>Tue Dec 03 00:02:10 2019 +0000
treee45dd604e654940b3c5e9d3f86f7e92352f21211
parent4f955a67f0c864b37017485d4201c15dbec556c1 [diff]
Fixed debug title
113 files changed
tree: e45dd604e654940b3c5e9d3f86f7e92352f21211
  1. docs/
  2. src/
  3. .gitattributes
  4. .gitignore
  5. LICENSE.txt
  6. pom.xml
  7. README.md
README.md

db-jdo-site

Sources for the Apache DB JDO web site

While under construction, the website can be found under https://apache.github.io/db-jdo-site/

This repository contains the JDO website source.

  • The ASCIIDOC sources can be found in src/main/asciidoc
  • The website menu is defined in src/main/template
  • The website can be build with mvn clean build. This generates html files in target/site. These need to be copied manually into the docs folder. Then, after git commit and git push, they should be visible on the website (you may have to refresh the browser). Alternatively, the generated files can of course be viwed locally with a web browser.
  • The converter for migrating the old html files to asciidoc can be found in src/main/java

TODO Asciidoc

  • JDO Usage -> Guides are missing
  • Links in Usage -> Glossary

TODO

  • Downloads -> Any release -> cgi files....
  • Development -> Sourcecode page
  • Development -> Coding standard page
  • Community -> Team?
  • Development -> Dependencies (SVN -> Git)
  • Cleanup everything