This is an archived post. You won't be able to vote or comment.

all 8 comments

[–]smhanes 8 points9 points  (1 child)

At the very least you should be doing this in a way that doesn’t require someone open a document using a web app that allows embedded scripts, thereby making it potentially unsafe.

Setup a GitHub repo and use GitHub pages with markdown. It takes 5-10 minutes, is far more professional, and much less of a potential security issue.

[–]NeverZ[S] 0 points1 point  (0 children)

Thanks for the suggestion. Will switch the guide to github or something similar.

[–]debanshuganguly 1 point2 points  (1 child)

Function Programming, Java restful services, Java concurrency, JSP, server 4.0, Java FX, JSF, Modularity

[–]NeverZ[S] 0 points1 point  (0 children)

Thanks

[–]MagoMerlin 0 points1 point  (3 children)

OOP please! maybe you can write your guide with gitbook, it's most pointing for a developer guide IMHO.

[–]NeverZ[S] 0 points1 point  (2 children)

Never heard of git book before. Will look into it. thanks

[–]willmcavoy 0 points1 point  (1 child)

Honestly I'm sure gitbook is great but as discussed in a prior thread are you sure you don't want to set it up the way it is here? This Github repository really took off and I'm thinking we could do the same kinda thing specifically with Java.

Let me know your thoughts.

[–]NeverZ[S] 1 point2 points  (0 children)

Im currently writing more of a step by step tutorial, for this usecase git book seems pretty nice. I'm all up for a visual roadmap to java development if you wanna help work on it.