Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Dan Allen
    @mojavelinux
    for each file, you have access to file.src.origin which contains the repository URL, the reference, and the start path. then file.src.path gives you the path from the start path.
    you could always clone the repo again yourself. but what is missing, now that I think about it, is where Antora cloned it
    (if it's a local repository, that information is obviously the url)
    danyill
    @danyill
    Where Antora temporarily stored it?
    For processing/
    ?
    Dan Allen
    @mojavelinux
    it uses an auto-generated folder name in the system cache folder (or if the cache folder that you specify in the configuration)
    you could always figure it out of course by using the same logic antora uses to generate the folder name, but that's just not very nice
    we should pass it on
    file.src.origin.cloneDir or something of that sort
    we'll need an issue for that. really no reason not to do it
    keep in mind right now that is a bare repository
    in the future, i'm thinking we want a setting as to whether Antora clones bare or not bare
    but you still wouldn't be able to use the worktree alone since Antora works with multiple refs
    but with a git client, you can access what you need
    i recommend isomorphic-git for reasons previously stated
    danyill
    @danyill
    OK. I see. Probably a little early for this. I am in no hurry. I think if I can for my purposes mostly pass attributes at build time since most of them are branch/tag related. For the rest I can just rewrite it and hard code it in when I convert to the Antora structure.
    Dan Allen
    @mojavelinux
    if you want to file that issue to put the repo dir of the clone in the model, that will get the ball rolling on that
    like I said, I have, I just don't think it gets passed on
    Joseph Cayouette
    @jcayouette
    @danyill You are using an include to insert page headers? Does this work
    danyill
    @danyill
    I am using include to set things like sectnums, sectlinks, data-uri, linkcss, experimental, stem, stylesheets, fontawesome, docinfo etc. related stuff for javascript. Most of which I haven't tried to get going in Antora yet...
    Yes I shall file an issue soonish. Thanks!
    @jcayouette something like this is typical which I just include into my header
    Dan Allen
    @mojavelinux
    another way to set common attributes in a more dynamic way is to use a preprocessor. then you have access to the Antora context. it's a more brute force way, but sometimes I summon it
    Joseph Cayouette
    @jcayouette
    @danyill Ill have to give this a try, I know it wont be supported on github, but with antora we wont be using github for "viewing" docs :D The goal is antora, or a published output.
    @mojavelinux Thank you
    @danyill Woops :D Thank you
    danyill
    @danyill
    Well with the BRAND SPANKING NEW Antora includes if they work up at component level what I do might be a convenient way to set attributes across an entire website
    I'm used to publishing all my documentation as discrete zip files (I know...) and I have a subtree with my "regular include Asciidoc files" to help with this
    :fireworks: :fireworks:
    Dan Allen
    @mojavelinux

    I do might be a convenient way to set attributes across an entire website

    exactly!

    though you can also do that using the playbook ;)
    but where it becomes very useful is per component
    danyill
    @danyill
    Ah. true.
    Dan Allen
    @mojavelinux
    that per component (at least per component version) will also be happening in antora.yml in 1.2 or 1.3
    i've needed that multiple times. but as you pointed out, the include can get you there too
    danyill
    @danyill
    I haven't caught up with some of the new features yet. I have to decide whether to stop doing my zip files once I move to Antora. One of the things I don't know how to do is to link to large PDFs (which I do a lot of) and have Antora intelligently re-open the link in the same window it's already open in a sane way (probably possible with Javascript). On a local filesystem this just doesn't matter (because it's fast) but online opening a 50MB file too many times is a problem
    This is part of why I'm so whiny about the resource id thing because when I migrate I have to deal with forward/backwards compatibility and I want to be able to script going between the "old way" and the "Antora structure"
    But I'm sure I can get there just by moving slowly and I'm starting to see the pluses on the resource id approach that's been taken. Things do have a home.
    Joseph Cayouette
    @jcayouette
    @danyill Stop using pdf XD hehe problem solved. "grins"
    @danyill I also have pdf requirements, it can be challenging.
    brb lunch
    danyill
    @danyill
    If only it was possible. I work in the electricity industry and we do everything like it's no later than 2006
    And the company mandates Sharepoint and Word. Antora/Asciidoc is my blackmarket attempt to illustrate what a better life could look like (I have yet to find a problem Sharepoint actually solves)
    Dan Allen
    @mojavelinux
    i want to be clear I'm totally fine with producing PDFs. it's not PDF itself I have a problem with, per se
    it's the idea that you can make a PDF creator that's any good without either a) paying or b) using the brower
    and clearly, b) is the way to go for an OSS project ;)
    I tried to create a PDF converter. it can do some things...but then you hit a very very thick wall
    so now I understand the problem space better