You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be possible to build a specific SAFETAG guide section that pulls in the relevant endnotes and appendices (e.g. example/ content) for that section.
This is very possible. Currently the makefile just targets the main index's. We would want to actually script up the current builder to be more than a makefile. Once we do this it could do much much more. Here is what it would look like in make speak, but we would want to actually transition it into a language that is robust.
Note that this is very close, but due to the SAFETAG per-chapter indices being at a different directory level than the master indices, the copy to tmp/.../target must stay at the root of the content, but the ../ structure in the index/ files can't correctly reference out.
This might end up being a SAFETAG issue again, or an extra doc builder option for the "working" directory?
The text was updated successfully, but these errors were encountered:
Moved in from SAFETAG/SAFETAG#82
It should be possible to build a specific SAFETAG guide section that pulls in the relevant endnotes and appendices (e.g. example/ content) for that section.
This is very possible. Currently the makefile just targets the main index's. We would want to actually script up the current builder to be more than a makefile. Once we do this it could do much much more. Here is what it would look like in make speak, but we would want to actually transition it into a language that is robust.
Note that this is very close, but due to the SAFETAG per-chapter indices being at a different directory level than the master indices, the copy to tmp/.../target must stay at the root of the content, but the ../ structure in the index/ files can't correctly reference out.
This might end up being a SAFETAG issue again, or an extra doc builder option for the "working" directory?
The text was updated successfully, but these errors were encountered: