We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi all,
I'm new in alectyron, so I'm hoping that anyone can answer my question.
Is there are way to replace IBM_PLEX_CDN and FIRA_CODE_CDN if I'm running the CLI to generate html files?
E.g.: alectryon --frontend coq+rst --backend webpage copy code/code.v -o code.html
Background, we need to use local versions of stylesheets and do not include external resources.
I found the variables defined here: alectryon/html.py
And all I can think about yet is to set up a fork and modify this.
But I'm wondering if there’s an easier way, and I'm missing something.
Thanks, CArina
The text was updated successfully, but these errors were encountered:
Hi CArina , welcome to Alectryon :)
No need to form; what you want for customized output is a "custom driver", as documented here: https://github.com/cpitclaudel/alectryon#with-a-custom-driver
You can just import the relevant packages, set these two variables, and then call main. Let me know if you run into trouble!
Sorry, something went wrong.
No branches or pull requests
Hi all,
I'm new in alectyron, so I'm hoping that anyone can answer my question.
Is there are way to replace IBM_PLEX_CDN and FIRA_CODE_CDN if I'm running the CLI to generate html files?
E.g.:
alectryon --frontend coq+rst --backend webpage copy code/code.v -o code.html
Background, we need to use local versions of stylesheets and do not include external resources.
I found the variables defined here:
alectryon/html.py
And all I can think about yet is to set up a fork and modify this.
But I'm wondering if there’s an easier way, and I'm missing something.
Thanks,
CArina
The text was updated successfully, but these errors were encountered: