https://discuss.asciidoctor.org/have-asciidoctorj-output-html-to-be-include-in-jekyll-generated-site-tp8353p8368.html
I completely don’t understand what you mean here, what specifically are these parts that you think should be in a shared component?
AFAICT everything you might be maintaining is in your one repo in my PR — not necessarily the best structure but the most compact.
Perhaps one problem is that in Antora ‘component’ has a specific meaning that I’m used to and isn’t what you mean :-)
If you are saying that you would like the tabs asciidoctor extension and related Antora UI bits, and the copy-to-clipboard UI bits to be in external separately maintained reusable projects, I think that’s a good idea and I may pursue it.
Publishing the tabs asciidoctor extension to npm is a trivial undertaking.
However, AFAIK there is no good accepted way to make a “js + css” extension in general; for non-Antora projects you’re going to be adjusting the stylesheets and header/footer scripts yourself.
My Antora UI-builder project is my idea on how this might be done, but it’s in early stages and, for instance, hasn’t been reviewed by Dan.
If you know of a good technology for unified extensions to the css + js for a site, I’d like to know about it.
Looking forward to your feedback,
David Jencks
On Nov 22, 2020, at 1:31 AM, maxandersen [via Asciidoctor :: Discussion] <
[hidden email]> wrote:
David Jencks wrote
I spent a little time setting up the readme.adoc as an Antora site:
https://github.com/jbangdev/jbang/pull/535 <
https://github.com/jbangdev/jbang/pull/535>.
This includes the two bits from couchbase, the tabs-block extension and the clipboard.js.
The basics of including the code so it’s usable/accessible was trivial however….
* Tabs work although they don’t look elegant, so I might have missed some important css.
* The js for clipboard works but the functionality seems to rely on font awesome icons, and I can’t get it to work. is ‘far fa-copy’ a pro icon?
Thank you very much David for taking the time to do that - really appreciated; but the result is what I'm trying to avoid - that inside the project is now all these parts I believe is better of in a shared component so I don't have to maintain this across multiple repos.
I know Dan says one with my expertise can make that happen; but my expertise also tells me that such things gets stale fast - hence why I like asciidoctorj as here I in my circle of what I know can see they are being maintained and made reusable.
For some reason (unless i'm blind) in case of ruby based asciidoctor the reusable parts gets copied around.....thats what I was trying to avoid.
My personal opinion is that having this readme as one page is extremely user-unfriendly. If you’re interested in pursuing Antora-izing, you should be set up with this PR to start breaking the content into reasonable sized pages.
The whole goal of this is to get it to split up - I just didn't do that yet as I'm trying to figure out where the doc will end up living which depend on the stack used/applied.
again thanks for the PR - I'll definitely take a look and see if can learn something.