As for me the main page of any product is important to make a good first impression. When I open the main page of JanusGraph it looks like the site was constructed in the 90s (sorry for criticism). I understand that the style was taken from TitanDB (http://titan.thinkaurelius.com) but I think it should be changed.
Another concern is that the main page uses http protocol still. I do understand that there is nothing to secure on the main page but I believe that https protocol will make a better impression. Notice that docs.janusgraph.org is using https protocol (Letsencrypt certificate). I believe it isn't hard to add an additional SSL certificate for the main page. Also, Letsencrypt supports wildcard certificates, it is possible to make a certificate for the entire *.janusgraph.org domain to cover all subdomains and use the same certificate on the main page and in the docs.
Hello Jan,Wow. It is an impressive work. I really like this design! Hope it will be merged soon.The one issue which I've noticed is that there is only one (I assume latest) version of the documentation. Right now in JanusGraph there are seven documentations for different versions of janusgraph and we can easily switch between them. Is there a possibility to make such an approach with your solution?
There are also other issues, but I think they are temporary and easy to resolve. I will place them here not to lose:- Some links are shown as `???`.
- Some links doesn't work.- Some images are not loaded.- Some links are wrong named (For example, in the bottom of the `Introduction` section there is a next link which is also called `Introduction` but should be called `Configuration`)- `Edit this page` buttons are referring to the wrong location
Hi Chris,
I would try to remove the most of doc generation from our current build system.
This task would requires to rebase work on each changes of documentation.
I would prefer that following task should be done before merging:
Tasks can be done after merging in small PR:
--
You received this message because you are subscribed to the Google Groups "JanusGraph developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to janusgraph-de...@googlegroups.com.
To post to this group, send email to janusgr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/janusgraph-dev/b09f96d9-0886-4e04-abba-eccf0d78195f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Traefik use tool written by them self called:
https://github.com/containous/structor.
--
Are we fully replacing the current doc generation for the release docs? Or are we going to have two separate systems to manage going forward?
- Markdown has less functionality than AsciiDoc, e.g., including source code from source files isn't supported afaik which would otherwise be a good option to ensure that code examples in the docs keep working (by compiling them and maybe including them in a test).
- We need to find solutions / workarounds for things like the TinkerPop version that is automatically included in all links to TinkerPop docs in the version JanusGraph uses for that version of the docs.
I didn't check, but do we use this AsciiDoc functionality?
Not sure if I understood you correctly, Jan: Are you agreeing with Oleksandr that a feature branch makes sense?
In that case, I can create one, but that would mean of course that you would need to do all changes from then on through PRs. Although we can then just merge these PRs through to the feature branch as the formal review will happen later when we merge the feature branch into a release branch.
We should just create an issue first for that, but that makes sense in general I guess as we can keep track of the progress and what's still left to do in that issue.
Another thing I'm not sure about yet is which release branch should be target for this. We will release a 0.2.3 version. Should that still use our current version of the docs or already the new one?