I think these are good to implement in standards sub-domain website:
build a dictionary list (unlike @pipauwel’s advise) which all can find dictionaries and files easily (instead of searching the sub-domain context on Google)
Early days when I joined to buildingSMART forum, I suggested to develop IFC schema and documents, it’s better to have a cloud system, “Function as a Service - FaaS” like AWS Lambda
Then you will be able to improve things better, and independently.
You’ve started to follow this in IfcDoc for versioning, but can use this for documents and everything too
If you want speed up IFC development you need a cloud version which your teams be able to work function by function, service by service (microservice)