yes, this is planned to be supported as well.
- generate static html from markdown
- validate context files
- compile “common” terms into a top-level context
- create a versioned context whenever a new term is added
i think it is a good idea to practice “asset colocation” and keep FEP-specific files stored within the FEP-specific directory. what’s “confusing” is that we have essentially three current paths that FEP submitters have to be aware of:
feps/fep-xxxx.mdfeps/assets/fep-xxxx/filename.extcontexts/fep-xxxx/context.jsonld(pending 2e40 or 9606)
there is additionally an issue of unclear editing authority. better to avoid write conflicts and just give each FEP editor an FEP-specific directory.
EDIT: FEP-9606 PR has been submitted