Best practices for distributing a company document style file

How can I tell someone that I want to be his or her friend?

How can I make my BBEG immortal short of making them a Lich or Vampire?

Anagram holiday

What killed these X2 caps?

Is the Joker left-handed?

Facing a paradox: Earnshaw's theorem in one dimension

How could indestructible materials be used in power generation?

Where does SFDX store details about scratch orgs?

Why is consensus so controversial in Britain?

Python: return float 1.0 as int 1 but float 1.5 as float 1.5

When a company launches a new product do they "come out" with a new product or do they "come up" with a new product?

What to put in ESTA if staying in US for a few days before going on to Canada

Brothers & sisters

How to take photos in burst mode, without vibration?

Fully-Firstable Anagram Sets

Can a virus destroy the BIOS of a modern computer?

Today is the Center

Combinations of multiple lists

Twin primes whose sum is a cube

How do I write bicross product symbols in latex?

I Accidentally Deleted a Stock Terminal Theme

Forgetting the musical notes while performing in concert

Neighboring nodes in the network

Is delete *p an alternative to delete [] p?



Best practices for distributing a company document style file














0















I've recently created a new document class that implements all the stylistic standards and requirements for documentation at my company. Now I'm trying to find the best way that this style file and required images can be used by others in the company. (and the company alone)



I want a solution where the company_style.cls is:



  1. version controlled in it's own repository

  2. easily available for others to use in their documents

  3. easy for existing documents to update to newer versions of company_style.cls

  4. is not in a sub repository.

The current solution that I have is as followes:



  1. the company_style.cls and required images are in a mercurial repository.

  2. our CI server stores versions of the style

  3. users can download and extract the style artifact from the CI server next to the root .tex file so that they can specify documentclass[numbered]style/company_style

  4. compile and enjoy

Other notes:



  1. The "required images" are things like company logo, and footer images. I don't want to make people download these separately.









share|improve this question







New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 2





    Welcome to TeX.SX! While the file at question is a TeX file I don't think this question is really related to LaTeX. It is about sharing some files in an efficient and version controlled manner. I therefore vote to close it as off-topic.

    – Skillmon
    1 hour ago











  • Welcome to TeX.SE!

    – Kurt
    1 hour ago











  • All common tex inputs could be subject to usual warnings about cloud file systems accents etc be simply on a server user mapped share or better still in a user local texmf / texinputs folder system

    – KJO
    1 hour ago















0















I've recently created a new document class that implements all the stylistic standards and requirements for documentation at my company. Now I'm trying to find the best way that this style file and required images can be used by others in the company. (and the company alone)



I want a solution where the company_style.cls is:



  1. version controlled in it's own repository

  2. easily available for others to use in their documents

  3. easy for existing documents to update to newer versions of company_style.cls

  4. is not in a sub repository.

The current solution that I have is as followes:



  1. the company_style.cls and required images are in a mercurial repository.

  2. our CI server stores versions of the style

  3. users can download and extract the style artifact from the CI server next to the root .tex file so that they can specify documentclass[numbered]style/company_style

  4. compile and enjoy

Other notes:



  1. The "required images" are things like company logo, and footer images. I don't want to make people download these separately.









share|improve this question







New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.















  • 2





    Welcome to TeX.SX! While the file at question is a TeX file I don't think this question is really related to LaTeX. It is about sharing some files in an efficient and version controlled manner. I therefore vote to close it as off-topic.

    – Skillmon
    1 hour ago











  • Welcome to TeX.SE!

    – Kurt
    1 hour ago











  • All common tex inputs could be subject to usual warnings about cloud file systems accents etc be simply on a server user mapped share or better still in a user local texmf / texinputs folder system

    – KJO
    1 hour ago













0












0








0








I've recently created a new document class that implements all the stylistic standards and requirements for documentation at my company. Now I'm trying to find the best way that this style file and required images can be used by others in the company. (and the company alone)



I want a solution where the company_style.cls is:



  1. version controlled in it's own repository

  2. easily available for others to use in their documents

  3. easy for existing documents to update to newer versions of company_style.cls

  4. is not in a sub repository.

The current solution that I have is as followes:



  1. the company_style.cls and required images are in a mercurial repository.

  2. our CI server stores versions of the style

  3. users can download and extract the style artifact from the CI server next to the root .tex file so that they can specify documentclass[numbered]style/company_style

  4. compile and enjoy

Other notes:



  1. The "required images" are things like company logo, and footer images. I don't want to make people download these separately.









share|improve this question







New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I've recently created a new document class that implements all the stylistic standards and requirements for documentation at my company. Now I'm trying to find the best way that this style file and required images can be used by others in the company. (and the company alone)



I want a solution where the company_style.cls is:



  1. version controlled in it's own repository

  2. easily available for others to use in their documents

  3. easy for existing documents to update to newer versions of company_style.cls

  4. is not in a sub repository.

The current solution that I have is as followes:



  1. the company_style.cls and required images are in a mercurial repository.

  2. our CI server stores versions of the style

  3. users can download and extract the style artifact from the CI server next to the root .tex file so that they can specify documentclass[numbered]style/company_style

  4. compile and enjoy

Other notes:



  1. The "required images" are things like company logo, and footer images. I don't want to make people download these separately.






documentclass






share|improve this question







New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 1 hour ago









Chui VanfleetChui Vanfleet

1




1




New contributor




Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Chui Vanfleet is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.







  • 2





    Welcome to TeX.SX! While the file at question is a TeX file I don't think this question is really related to LaTeX. It is about sharing some files in an efficient and version controlled manner. I therefore vote to close it as off-topic.

    – Skillmon
    1 hour ago











  • Welcome to TeX.SE!

    – Kurt
    1 hour ago











  • All common tex inputs could be subject to usual warnings about cloud file systems accents etc be simply on a server user mapped share or better still in a user local texmf / texinputs folder system

    – KJO
    1 hour ago












  • 2





    Welcome to TeX.SX! While the file at question is a TeX file I don't think this question is really related to LaTeX. It is about sharing some files in an efficient and version controlled manner. I therefore vote to close it as off-topic.

    – Skillmon
    1 hour ago











  • Welcome to TeX.SE!

    – Kurt
    1 hour ago











  • All common tex inputs could be subject to usual warnings about cloud file systems accents etc be simply on a server user mapped share or better still in a user local texmf / texinputs folder system

    – KJO
    1 hour ago







2




2





Welcome to TeX.SX! While the file at question is a TeX file I don't think this question is really related to LaTeX. It is about sharing some files in an efficient and version controlled manner. I therefore vote to close it as off-topic.

– Skillmon
1 hour ago





Welcome to TeX.SX! While the file at question is a TeX file I don't think this question is really related to LaTeX. It is about sharing some files in an efficient and version controlled manner. I therefore vote to close it as off-topic.

– Skillmon
1 hour ago













Welcome to TeX.SE!

– Kurt
1 hour ago





Welcome to TeX.SE!

– Kurt
1 hour ago













All common tex inputs could be subject to usual warnings about cloud file systems accents etc be simply on a server user mapped share or better still in a user local texmf / texinputs folder system

– KJO
1 hour ago





All common tex inputs could be subject to usual warnings about cloud file systems accents etc be simply on a server user mapped share or better still in a user local texmf / texinputs folder system

– KJO
1 hour ago










0






active

oldest

votes












Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "85"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);






Chui Vanfleet is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483272%2fbest-practices-for-distributing-a-company-document-style-file%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Chui Vanfleet is a new contributor. Be nice, and check out our Code of Conduct.









draft saved

draft discarded


















Chui Vanfleet is a new contributor. Be nice, and check out our Code of Conduct.












Chui Vanfleet is a new contributor. Be nice, and check out our Code of Conduct.











Chui Vanfleet is a new contributor. Be nice, and check out our Code of Conduct.














Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f483272%2fbest-practices-for-distributing-a-company-document-style-file%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How should I use the fbox command correctly to avoid producing a Bad Box message?How to put a long piece of text in a box?How to specify height and width of fboxIs there an arrayrulecolor-like command to change the rule color of fbox?What is the command to highlight bad boxes in pdf?Why does fbox sometimes place the box *over* the graphic image?how to put the text in the boxHow to create command for a box where text inside the box can automatically adjust?how can I make an fbox like command with certain color, shape and width of border?how to use fbox in align modeFbox increase the spacing between the box and it content (inner margin)how to change the box height of an equationWhat is the use of the hbox in a newcommand command?

Doxepinum Nexus interni Notae | Tabula navigationis3158DB01142WHOa682390"Structural Analysis of the Histamine H1 Receptor""Transdermal and Topical Drug Administration in the Treatment of Pain""Antidepressants as antipruritic agents: A review"

inputenc: Unicode character … not set up for use with LaTeX The Next CEO of Stack OverflowEntering Unicode characters in LaTeXHow to solve the `Package inputenc Error: Unicode char not set up for use with LaTeX` problem?solve “Unicode char is not set up for use with LaTeX” without special handling of every new interesting UTF-8 characterPackage inputenc Error: Unicode character ² (U+B2)(inputenc) not set up for use with LaTeX. acroI2C[I²C]package inputenc error unicode char (u + 190) not set up for use with latexPackage inputenc Error: Unicode char u8:′ not set up for use with LaTeX. 3′inputenc Error: Unicode char u8: not set up for use with LaTeX with G-BriefPackage Inputenc Error: Unicode char u8: not set up for use with LaTeXPackage inputenc Error: Unicode char ́ (U+301)(inputenc) not set up for use with LaTeX. includePackage inputenc Error: Unicode char ̂ (U+302)(inputenc) not set up for use with LaTeX. … $widehatleft (OA,AA' right )$Package inputenc Error: Unicode char â„¡ (U+2121)(inputenc) not set up for use with LaTeX. printbibliography[heading=bibintoc]Package inputenc Error: Unicode char − (U+2212)(inputenc) not set up for use with LaTeXPackage inputenc Error: Unicode character α (U+3B1) not set up for use with LaTeXPackage inputenc Error: Unicode characterError: ! Package inputenc Error: Unicode char ⊘ (U+2298)(inputenc) not set up for use with LaTeX