How to import Helvetica Neue Lt Std Font to apply that font in the Aras css Tech docs?

It's a bit of work. Do you need to use the font everywhere? Or just in some specific locations?
I once did something similar to integrate the Roboto font support into an early I12. Innovator included the font already but it wasn´t "used" yet.

You have a "fonts" folder in the codetree where you can add your custom fonts. Than you need to customize the stylesheets to ensure the font is used.

In my case I only needed to customize common.min.css

For this mod I have just thrown my custom stylesheet behind the minified code. This ensured the custom code is still some kind of readable. 
If you want to use the font for all Innovator elements you might also need to modify other stylesheets like main.css. Don´t forget to document the codetree mod for upgrade.

And if you really want to surprise your users: Use "Comic Sans"! 

It's a bit of work. Do you need to use the font everywhere? Or just in some specific locations?
I once did something similar to integrate the Roboto font support into an early I12. Innovator included the font already but it wasn´t "used" yet.

You have a "fonts" folder in the codetree where you can add your custom fonts. Than you need to customize the stylesheets to ensure the font is used.

In my case I only needed to customize common.min.css

For this mod I have just thrown my custom stylesheet behind the minified code. This ensured the custom code is still some kind of readable. 
If you want to use the font for all Innovator elements you might also need to modify other stylesheets like main.css. Don´t forget to document the codetree mod for upgrade.

And if you really want to surprise your users: Use "Comic Sans"! 

The pdfPublishingRule, used for converting TechDocs into PDFs, is not found in main.css so I may need to look elsewhere or send in a ticket to Aras to ask how I can navigate to that installed module's css folders.

Also, thank you, your response was quite helpful for me to come to this conclusion and it also gave me light in determining the conventional way of applying new styles to Aras. Seems like it is not too hard after all, maybe one day dark mode can come along (if they don't configure that for us in a release one day :) )

Edit: Actually I take back some of what I said - I just now navigated to the converter module, and imported the font face that I wanted. The font still isn't coming through, but this is good progress, hopefully I can find where I really need to apply it within the style's folder. With your response I should be able to deduce what place needs it. Hopefully the rendering of the font family will be a success!

OMG, why don´t we have a dark mode? I never questioned that this one was missing. Thumps up for this idea!!

Quote: "how I can navigate to that installed module's css folders"

Well, basically you navigate to the modules css folders :). There are modules folders and they have stylesheets.
But for PDF publishing you specify the style sheet inside Innovator itself. See "Document Types" in TOC.

Regarding my example with the font you also need to customize your Forms to actually use the new font or customize default.css. 

Right, I was able to navigate to the Conversion Server css. Although, when it comes to using the font-style: 'Helvetica' in the Document Type css it still is not a valid property value.

Here's what I've done so far:

Added a font-face to fonts referring to the local file of the font .otf file

Added in reference to the css in the Document Type's css file

Edit: Font-family:'Helvetica' seems to be a valid property, but the rendering does not happen. I am unsure whether this is where the styling is needed or not.

Hope you document everything for the upgrade team!

Regarding TechDocs maybe have to differentiate the Viewer from the actual printed result?

Hmm. Oh I see what you mean. Yeah - the Output Settings has choice of Editor, PDF, and HTML - all outputs are used and all use the same CSS file so there should be no difference there.

The font has yet to render in the editor. Then I can postulate that rendering the font in the editor is what I need to direct attention to first. It has seemed uninhibited with most css, I know sometimes the HTML and Editor can look a little different despite the same styling, for instance sometimes font colors not showing correctly in the editor (atleast for us, we are using a mismatched version #s between Aras and Technical Documentation lol)

Use the browser debugger, maybe you can discover which specific CSS files are used.

I don´t use TechDocs. But what I see in MPP, there is definitely a Tahoma font reference in Solutions\MPP\styles. In addition in my Innovator 12 the claroGrid.css is still used all over the place for all kind of styling, especially in MPP.

claroGrid always will give us the nostalgic Innovator 11 look.

Brilliant. So I saw in the debugger:

Access to font at '<site>/InnovatorServer/fonts/HelveticaNeueLTStd-Cn.otf' from origin 'null' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

Coming from me using:

@font-face {
font-family: 'HelveticaNeueLtStd-Cn';
src: url('../fonts/HelveticaNeueLTStd-Cn.otf');
}

Will try to look at the file properties and potentially come across something that can make the server recognize the file. Or, potentially change the src: from url() to something that circumvents needing to do CORS, as the file is local in the server 

So I swapped it out for local() rather than url(). I was unable to successfully use the font with any of these combinations:

fonts.css: @font-face: { font: x, src: local(path)}

& in document styles: .ArasTextNode: font-family: 'x'

I had been restarting both services, and I am yet to be successful.

Unfortunately no one else has seen a successful example yet. If there is info around, please share.

Thank you

Regarding CORS error this is so far the best discussion in this forum:  Accessing Aras Innovator instance outside the network using Ngrok Tunneling 

But in your case: Have you asked Aras support already? Custom fonts aren´t a super common requirement, but I definitely think this use case appeared before in the Innovator world. You don´t need to solve everything by yourself :). 

Yea, have met with Aras but was coming up dry in terms of doing so with the output of the Conversion Server publishing dialouge.

I was able to smooth out the CORS error by referring to it as a relative file path instead, although that is a moot point since it was unsuccessful & cannot confirm i.e. whether the font query really grabbed the file.

I'm thinking the actual font used isn't where I think. I deleted all in fonts.css & the font appeared the same. So it may be in a different .css that dictates the default font used. Once I can change that I'll be golden.

I guess I just like to write out my reasoning, that way I don't forget what I thought earlier lol.