Best practices for distributing a company document style file
What reasons are there for a Capitalist to oppose a 100% inheritance tax?
Why is it a bad idea to hire a hitman to eliminate most corrupt politicians?
Doing something right before you need it - expression for this?
prove that the matrix A is diagonalizable
What does it mean to describe someone as a butt steak?
Fully-Firstable Anagram Sets
intersection of two sorted vectors in C++
How do conventional missiles fly?
Is it canonical bit space?
90's TV series where a boy goes to another dimension through portal near power lines
How could indestructible materials be used in power generation?
1960's book about a plague that kills all white people
Anagram holiday
Is it possible to download Internet Explorer on my Mac running OS X El Capitan?
What is the word for reserving something for yourself before others do?
Forgetting the musical notes while performing in concert
Could gravitational lensing be used to protect a spaceship from a laser?
AES: Why is it a good practice to use only the first 16bytes of a hash for encryption?
Why is consensus so controversial in Britain?
How can I tell someone that I want to be his or her friend?
Why doesn't H₄O²⁺ exist?
In a Spin are Both Wings Stalled?
Why can't we play rap on piano?
Withdrawals from HSA
Best practices for distributing a company document style file
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:
- version controlled in it's own repository
- easily available for others to use in their documents
- easy for existing documents to update to newer versions of company_style.cls
- is not in a sub repository.
The current solution that I have is as followes:
- the company_style.cls and required images are in a mercurial repository.
- our CI server stores versions of the style
- 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 - compile and enjoy
Other notes:
- The "required images" are things like company logo, and footer images. I don't want to make people download these separately.
documentclass
asked 4 mins ago
Chui VanfleetChui Vanfleet
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.
add a comment |
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:
- version controlled in it's own repository
- easily available for others to use in their documents
- easy for existing documents to update to newer versions of company_style.cls
- is not in a sub repository.
The current solution that I have is as followes:
- the company_style.cls and required images are in a mercurial repository.
- our CI server stores versions of the style
- 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 - compile and enjoy
Other notes:
- The "required images" are things like company logo, and footer images. I don't want to make people download these separately.
documentclass
asked 4 mins ago
Chui VanfleetChui Vanfleet
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.
add a comment |
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:
- version controlled in it's own repository
- easily available for others to use in their documents
- easy for existing documents to update to newer versions of company_style.cls
- is not in a sub repository.
The current solution that I have is as followes:
- the company_style.cls and required images are in a mercurial repository.
- our CI server stores versions of the style
- 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 - compile and enjoy
Other notes:
- The "required images" are things like company logo, and footer images. I don't want to make people download these separately.
documentclass
asked 4 mins ago
Chui VanfleetChui Vanfleet
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.
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:
- version controlled in it's own repository
- easily available for others to use in their documents
- easy for existing documents to update to newer versions of company_style.cls
- is not in a sub repository.
The current solution that I have is as followes:
- the company_style.cls and required images are in a mercurial repository.
- our CI server stores versions of the style
- 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 - compile and enjoy
Other notes:
- The "required images" are things like company logo, and footer images. I don't want to make people download these separately.
documentclass
documentclass
asked 4 mins ago
Chui VanfleetChui Vanfleet
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.
asked 4 mins ago
Chui VanfleetChui Vanfleet
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.
asked 4 mins ago
Chui VanfleetChui Vanfleet
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.
asked 4 mins ago
Chui VanfleetChui Vanfleet
1
asked 4 mins 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.
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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.
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.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
