Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since the relaunch, we have been using a hack to make it appear that the main website (built with Jekyll) and the GT guidelines (built with DITA-OT) were seamlessly integrated (same menu, header, footer and style). To achieve this, we basically fed the output of DITA-OT into Jekyll again, which works but only because browsers are so tolerant against faulty markup.
With this PR, the GT Guidelines are a separate area of the website (with a link back to the main site once OCR-D/gt-guidelines#26 is merged).
The drawback is that there is no consistent top menu. The advantage is that the GT guidelines are vastly more readable and therefore, hopefully, more useful.