Anthony

I'm doing some issue cleanup. Are we going to do anything else here? Can this issue be closed?

Yeah, sudoers policies are hard to get right and are a common exploit target. There are similar exploits to yours that would allow root access. > build.commands does not allow...

> That said, even if it works for this case, I still think it's a good feature to develop eventually. Yeah, this does feel like a disconnect, but I think...

@henryiii just to clarify, are you using `build.commands` or `build.jobs` configuration? We discussed a path forward to making `build.jobs` easier to use for arbitrary documentation generation, and this would make...

Okay yeah, this is exactly the case we discussed then. You have pinpointed the current issue, and you will need to get creative with build.jobs to replace the build command...

I'd like to prioritize adding support for `build.jobs.build` step override so that we can point users towards `build.jobs` when they want to use custom build pipelines. I still do think...

Yeah, the two are different, technically speaking, but what I'm saying is that if we add support for overriding `build.jobs.build`, I think we would point most users towards customization through...

I have felt that even Pelican/Docusaurus/etc should all be supported with `build.jobs` too. Would there be anything stopping the user from doing something like this if we supported it? ```yaml...

Yeah, I'm not talking that deep on package reuse yet. This conversation is centered around finishing the overrides to `build.jobs.build` because we get more value from less effort with that...

@mgeier So, we have still not prioritized this particular issue internally, but we _are_ also actively working on changing our approach to injecting all of our features into documentation project...