<p>Plugins are an important method of customisation for Cuberite. There are many different first and third-party plugins available in the <ahref="https://forum.cuberite.org/forumdisplay.php?fid=2">plugins section</a> of our forum. For information on adding a plugin to your server, read the <ahref="https://book.cuberite.org/#2.4">user's manual</a>. If you want to write your own plugin, you will find all the necessary information in the <ahref="http://api-docs.cuberite.org/">API Documentation</a>.</p>
<p>Plugins are an important method of customisation for Cuberite. There are many different first and third-party plugins available in the <ahref="https://forum.cuberite.org/forumdisplay.php?fid=2">plugins section</a> of our forum. For information on adding a plugin to your server, read the <ahref="https://book.cuberite.org/#2.5">user's manual</a>. If you want to write your own plugin, you will find all the necessary information in the <ahref="http://api-docs.cuberite.org/">API Documentation</a>.</p>
I think we should come up with a solution here. These links shouldn't be dependent on placement order. Perhaps have a random unique string for each subsection? @bearbin
I think we should come up with a solution here. These links shouldn't be dependent on placement order. Perhaps have a random unique string for each subsection? @bearbin
That would still break if we ever change the title. We either have to be careful with title choices, or come up with the random string I originally proposed.
That would still break if we ever change the title. We either have to be careful with title choices, or come up with the random string I originally proposed.
How do you propose that a random string be generated that persists over changes of title/content.
Anyway, even with a random string, content being moved from one section to another (with some of the original being left in place) would not be handled. I think we should just be cautious changing titles, or maybe not move things around so much?
How do you propose that a random string be generated that persists over changes of title/content.
Anyway, even with a random string, content being moved from one section to another (with some of the original being left in place) would not be handled. I think we should just be cautious changing titles, or maybe not move things around so much?
I originally thought of adding a unique random string at the first line of each subsection file. That would persist even after a title change, and would be used as an anchor.
I originally thought of adding a unique random string at the first line of each subsection file. That would persist even after a title change, and would be used as an anchor.
I don't think there's any point changing the ToC - at the moment it auto-updates, and changing it would mean you have to update it manually. We only want to make it so external links don't need to be updated.
I don't think there's any point changing the ToC - at the moment it auto-updates, and changing it would mean you have to update it manually. We only want to make it so external links don't need to be updated.
This comment has been minimized.
SafwatHalabyFeb 6, 2016
MemberI think we should come up with a solution here. These links shouldn't be dependent on placement order. Perhaps have a random unique string for each subsection? @bearbin
SafwatHalaby repliedFeb 6, 2016
I think we should come up with a solution here. These links shouldn't be dependent on placement order. Perhaps have a random unique string for each subsection? @bearbin
This comment has been minimized.
sphinxc0reFeb 6, 2016
That would be good. If @bearbin comes up with a clean solution, I'm all for it
sphinxc0re repliedFeb 6, 2016
That would be good. If @bearbin comes up with a clean solution, I'm all for it
This comment has been minimized.
bearbinFeb 6, 2016
MemberThis is an easy fix, working on it now.
bearbin repliedFeb 6, 2016
This is an easy fix, working on it now.
This comment has been minimized.
bearbinFeb 6, 2016
MemberThis issue should now be fixed, look in the HTML for a new link-ref which is the title of the subsection.
e.g.
https://book.cuberite.org/#sub-introduction
bearbin repliedFeb 6, 2016
This issue should now be fixed, look in the HTML for a new link-ref which is the title of the subsection.
e.g.
https://book.cuberite.org/#sub-introduction
This comment has been minimized.
bearbinFeb 6, 2016
MemberBTW, the code won't get run for another 20 mins so be patient.
bearbin repliedFeb 6, 2016
BTW, the code won't get run for another 20 mins so be patient.
This comment has been minimized.
SafwatHalabyFeb 6, 2016
MemberThat would still break if we ever change the title. We either have to be careful with title choices, or come up with the random string I originally proposed.
SafwatHalaby repliedFeb 6, 2016
That would still break if we ever change the title. We either have to be careful with title choices, or come up with the random string I originally proposed.
This comment has been minimized.
bearbinFeb 6, 2016
MemberHow do you propose that a random string be generated that persists over changes of title/content.
Anyway, even with a random string, content being moved from one section to another (with some of the original being left in place) would not be handled. I think we should just be cautious changing titles, or maybe not move things around so much?
bearbin repliedFeb 6, 2016
How do you propose that a random string be generated that persists over changes of title/content.
Anyway, even with a random string, content being moved from one section to another (with some of the original being left in place) would not be handled. I think we should just be cautious changing titles, or maybe not move things around so much?
This comment has been minimized.
SafwatHalabyFeb 6, 2016
MemberI originally thought of adding a unique random string at the first line of each subsection file. That would persist even after a title change, and would be used as an anchor.
SafwatHalaby repliedFeb 6, 2016
I originally thought of adding a unique random string at the first line of each subsection file. That would persist even after a title change, and would be used as an anchor.
This comment has been minimized.
bearbinFeb 6, 2016
MemberThe best fix for this would be manual, by placing:
at the beginning of every subsection. Then you can have whatever string you want and changes are decoupled from titles.
bearbin repliedFeb 6, 2016
The best fix for this would be manual, by placing:
at the beginning of every subsection. Then you can have whatever string you want and changes are decoupled from titles.
This comment has been minimized.
SafwatHalabyFeb 6, 2016
MemberSounds good to me.
SafwatHalaby repliedFeb 6, 2016
Sounds good to me.
This comment has been minimized.
bearbinFeb 6, 2016
MemberI will remove the code I introduced earlier then.
bearbin repliedFeb 6, 2016
I will remove the code I introduced earlier then.
This comment has been minimized.
SafwatHalabyFeb 6, 2016
MemberYou'd still need to make the Table of Contents point to the right thing though.
SafwatHalaby repliedFeb 6, 2016
You'd still need to make the Table of Contents point to the right thing though.
This comment has been minimized.
bearbinFeb 6, 2016
MemberI don't think there's any point changing the ToC - at the moment it auto-updates, and changing it would mean you have to update it manually. We only want to make it so external links don't need to be updated.
bearbin repliedFeb 6, 2016
I don't think there's any point changing the ToC - at the moment it auto-updates, and changing it would mean you have to update it manually. We only want to make it so external links don't need to be updated.