Skip to content
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

Replace the Documentation Makefile with a Shell Script #2601

Merged
merged 13 commits into from
Nov 21, 2019

Conversation

settermjd
Copy link
Contributor

@settermjd settermjd commented Jul 5, 2019

This is a port of the cli script from the docs repository, streamlined for a single-component Antora setup. It also supports exporting the manual to docx format as well.

The manual generation can be tested with the following commands:

cd docs
bin/cli -m && bin/cli -d

@settermjd settermjd requested a review from tboerger July 5, 2019 11:41
@settermjd settermjd self-assigned this Jul 5, 2019
@settermjd settermjd changed the title Replace the docs Makefile with a cli script Replace the Documentation Makefile with a Shell Script Jul 5, 2019
Copy link
Contributor

@tboerger tboerger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't get why we want to generate a .docx format at all.

@settermjd
Copy link
Contributor Author

settermjd commented Jul 5, 2019

@pmaier1 has requested .docx copies of the manual a few times, so it made sense to codify the functionality here to avoid having to remember it for next time.

@michaelstingl
Copy link
Contributor

@settermjd what are the recommended steps to test-drive this? yarn antora and yarn serve aren't enough?

This is a port of the cli script from the docs repository, streamlined
for a single-component Antora setup. It also supports exporting the
manual to docx format as well.
@settermjd settermjd force-pushed the migrate-docs-makefile-to-cli-script branch from fbe7957 to db1f6e7 Compare July 5, 2019 12:07
@tboerger
Copy link
Contributor

tboerger commented Jul 5, 2019

@pmaier1 please clarify why you need this. Changes to a .docx document will never be put back into the repository. Why do we need that? I don't think that we want to maintain another container which includes the required tools just for fun or if there is no need for it.

@settermjd
Copy link
Contributor Author

@michaelstingl, I've updated the PR description with the relevant information. @tboerger, the docx generation command would only be used locally.

@settermjd
Copy link
Contributor Author

@pmaier1, I need your feedback to @tboerger's feedback.

@pmaier1
Copy link

pmaier1 commented Jul 12, 2019

I don't get why we want to generate a .docx format at all.

We needed the export once currently for some people to develop their own documentation based on ours. I don't know about further requirements or similar. At this point I don't find it necessary to automate this. I would rather want to check with those people whether they can also use Antora to create their own/branded docs.

@knugz38277

This comment has been minimized.

@settermjd
Copy link
Contributor Author

The functionality for generating docx versions of the manual have been removed.

@settermjd
Copy link
Contributor Author

@pmaier1 / @tboerger, can this now be merged?

settermjd and others added 6 commits October 17, 2019 13:17
The script was missing the mplus fonts and one of the notoserif font
files was incorrectly named. This commit corrects both of these
issues.
Honestly, I don't see an advantage one way or another, whether the
attributes set on the command line or in the config file. However, the
command line approach does provide that much greater level of
flexibility, which is the motivation for this commit, originally
inspired by tboerger in
#2601 (comment).
I never encountered this while developing the script on macOS (using GNU
Bash), however, using Bash 4.4.20(1)-release on Linux Mint 19.2, the
script doesn't work, because asciidoctor-pdf says that it can't read a
FIFO, only a file. Given that, this change is being made to have it run
properly on Bash in Linux.
This is perhaps just me being nitpicky, but in certain instances, when
the text is full justified, it renders somewhat unprofessionally. Left
justified, however, never has this problem, so the change is being made.
@settermjd
Copy link
Contributor Author

@tboerger, can I get another review, pls?

@settermjd settermjd merged commit 66e8e25 into master Nov 21, 2019
@delete-merged-branch delete-merged-branch bot deleted the migrate-docs-makefile-to-cli-script branch November 21, 2019 10:54
abelgardep pushed a commit that referenced this pull request Dec 16, 2019
Honestly, I don't see an advantage one way or another, whether the
attributes set on the command line or in the config file. However, the
command line approach does provide that much greater level of
flexibility, which is the motivation for this commit, originally
inspired by tboerger in
#2601 (comment).
abelgardep pushed a commit that referenced this pull request Jun 3, 2020
Honestly, I don't see an advantage one way or another, whether the
attributes set on the command line or in the config file. However, the
command line approach does provide that much greater level of
flexibility, which is the motivation for this commit, originally
inspired by tboerger in
#2601 (comment).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants