Adds the components for constructing a coverletter using awesome-cv
Provides additional sections
CV_ENV: letterheader, lettersection, and cvletter
cvletter provides the overall letter container
lettersection provides underlined letter sections
letterheader provides metadata as below
Letterheader additional variables
RECIPIENT: E.g. Company Recruitment Team
LETTER_OPENING: E.g. Dear Mr./Ms./Dr. LastName,
LETTER_CLOSING: E.g. Yours Sincerely,
LETTER_ATTACHED: E.g. Curriculum Vitae
LETTER_DATE: Uses \\today as default, E.g. <2021-01-01>
Letterheader also uses the following variables
EMPLOYER: E.g. Google Inc.
LOCATION: E.g. 1600 Amphitheatre Parkway\\Mountain View, CA 94043
Enabling export of property drawers might be useful to export HTML or
ASCII versions of the CV, but they are not used in the AwesomeCV LaTeX
export (and in fact break the compilation), so we just ignore them. Also
removed some spurious newlines in some of the environments.
Added a new ox-awesomecv.el, which provides support for the AwesomeCV
LaTeX class: https://github.com/posquit0/Awesome-CV
Added the corresponding documentation in the README as well.
An example of a CV produced with this exporter can be found at
https://zzamboni.org/vita/
Support for AwesomeCV (https://github.com/posquit0/Awesome-CV).
This is based on ox-altacv, with modifications for the macros and
structures supported by AwesomeCV. At the moment the following types
of sections are supported:
- CV_ENV "cventry" converts the section into a cventry environment.
- CV_ENV "cvskills" converts the section into a cvskills
environment. It must contain a description list, which gets renders
as the appropriate "cvskill" elements.
Not including a default value allows users to customize the output colors as
LaTeX header options. The moderncv LaTeX package already defaults to black.
Previously a cventry was inside a div and forced a h3 heading. The content
would not me inside the div because on markdown it wouldn't be
rendered. For limitation it is better to drop the div, make the heading
respect the org level and the properties list is just in one UL tag
