-
-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Velocity Documentation #521
Conversation
I've been thinking of this a bit more - if we're going to have a clear separation between sections and chapters in our documentation, would it be easier to maintain (and more well-structured) to format the directory structure as well? I believe mdBook allows directories for its
We could also continue this with something like...
Just a thought. Not sure how relevant this is at this stage, but if we continue branching out to different platforms (fabric, forge, sponge, etc.), it's probably worth considering. |
Yeah, it probably makes sense adding something like that. |
Maybe we could also bring the
That way, for example, when you're working with the bukkit documentation pages Or maybe we could completely merge the
I'm not sure if mdBook, Java, or Kotlin like all those files in the same place, but it would make it very easy to find the files that hold the code that documentation pages reference. Individual code files for each documentation page might be easier to understand than monolithic But yeah, that's probably not something we need to set up now for a single page about Velocity. |
For this PR, I intentionally paid attention to not change any existing documentation code locations because that would need to be updated in the pages as well which to be honest I deemed to not be within the scope of this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few notes. Maybe once we do some more Velocity docs it would make sense to restructure, but this PR definitely achieves the goal of letting people know Velocity CommandAPI exists.
No argument here. Restructuring definitely makes sense but also definitely doesn't fit into this PR. Also thanks for the few notes. I'll do them all locally but will add you as a co-author for the suggested changes as GitHub would do the same. |
2b356ed
to
f21ca60
Compare
f21ca60
to
34bae23
Compare
2a512c6
to
c191687
Compare
This is supposed to add a bit of Velocity documentation to the documentation.
Feel free to suggest anything else that you think should be added!