Get the table styling correctly

doc/content/post/basic_config.md

@@ -2,7 +2,7 @@
 title = "Basic Org file"
 author = ["Óscar Nájera"]
 draft = false
-weight = 1002
+weight = 1003
 +++
 
 The basic structure of an org file containing your CV is shown next.
@@ -10,13 +10,14 @@ The basic structure of an org file containing your CV is shown next.
 
 ## Personal contact information {#personal-contact-information}
 
-`TITLE` and `AUTHOR` are standard org options. But on `TITLE` you put your
-foreseen job.
+`TITLE`, `AUTHOR` and `EMAIL` are standard org options. But on `TITLE` you
+put your foreseen job.
 
 | Field    | Description                                        |
 |----------|----------------------------------------------------|
 | TITLE    | Desired job                                        |
 | AUTHOR   | Who you are?                                       |
+| EMAIL    | Your contact email                                 |
 | ADDRESS  | Mailing address, this can span over multiple lines |
 | HOMEPAGE | URL of your website                                |
 | MOBILE   | Mobile phone                                       |

doc/content/post/latex_export.md

@@ -2,7 +2,7 @@
 title = "Latex Exporter"
 author = ["Óscar Nájera"]
 draft = false
-weight = 1003
+weight = 1004
 +++
 
 ## Using modern-cv {#using-modern-cv}

doc/themes/project-landing-page

@@ -1 +1 @@
-Subproject commit 35665596cdd2a60e6cbf7b48a97bc2c0570de0c4
+Subproject commit 753b51a174b8126ad9fb68f3f5eb2c6fe7cf217b

readme.org

@@ -40,13 +40,14 @@ use =use-package= to manage the installation for example of =ox-moderncv=.
   :END:
 The basic structure of an org file containing your CV is shown next.
 ** Personal contact information
-=TITLE= and =AUTHOR= are standard org options. But on =TITLE= you put your
-foreseen job.
+=TITLE=, =AUTHOR= and =EMAIL= are standard org options. But on =TITLE= you
+put your foreseen job.
 
 | Field    | Description                                        |
 |----------+----------------------------------------------------|
 | TITLE    | Desired job                                        |
 | AUTHOR   | Who you are?                                       |
+| EMAIL    | Your contact email                                 |
 | ADDRESS  | Mailing address, this can span over multiple lines |
 | HOMEPAGE | URL of your website                                |
 | MOBILE   | Mobile phone                                       |
@@ -150,7 +151,7 @@ The style of this CV is more involved and you need some configuration in
 your org file to get it to work. First define the margins, the large margin
 to the right is to allow for a second column.
 #+BEGIN_SRC org :tangle altacv.org
-,#+LATEX_HEADER: \geometry{left=1cm,right=9cm,marginparwidth=7cm,marginparsep=1.2cm,top=1.25cm,bottom=1.25cm}
+,#+LATEX_HEADER: \geometry{left=1cm,right=9cm,marginparwidth=6.8cm,marginparsep=1.2cm,top=1.25cm,bottom=1.25cm}
 #+END_SRC
 # Next block is to generate exports
 #+BEGIN_SRC org :exports none :tangle altacv.org
@@ -207,53 +208,6 @@ When exporting you can call the following function to get the latex file.
 #+END_EXPORT
 
 
-* Docker container
-* Update readme
-** TODO examples [2/2]
-*** DONE pictures
-- State "DONE"       from "TODO"       [2018-05-01 Tue 20:41]
-The website generates the output pdfs, and the orgmode logo is just taken
-from wikipedia commons by link.
-*** DONE scripts
-- State "DONE"       from "TODO"       [2018-05-01 Tue 20:40]
-Now I can completely build a website from this readme and get the targeted CVs.
-* TODO Make a package
-Complete the file with license and how to load it.
-* DONE Base environment
-- State "DONE"       from "TODO"       [2018-03-22 Thu 17:57]
-I have the basic cv template that gets exported
-* DONE org-exporter for latex
-- State "DONE"       from "TODO"       [2018-04-05 Thu 03:04]
-:LOGBOOK:
-CLOCK: [2018-03-22 Thu 23:17]--[2018-03-23 Fri 03:25] =>  4:08
-CLOCK: [2018-03-22 Thu 17:58]--[2018-03-22 Thu 18:37] =>  0:39
-:END:
-I'm comparing the contents of the template export function. It looks that
-this one give the genera document layout and this is where I shall insert
-them data.
-comparing ox-latex, ox-beamer, ox-koma
-
-I learned quite a lot from the main latex and koma files. Currently I
-already reproduce latex export, which is not much as that was already a
-working output. But now I have the specific keywords for the personal
-information part.
-** DONE Process headings with properties into cventries
-- State "DONE"       from "TODO"       [2018-03-24 Sat 03:02]
-:LOGBOOK:
-CLOCK: [2018-03-23 Fri 22:54]--[2018-03-24 Sat 03:05] =>  4:11
-CLOCK: [2018-03-23 Fri 14:41]--[2018-03-23 Fri 19:05] =>  4:24
-:END:
-I'm constructing the entries quite fine but somehow the intermedia function
-refuses to get written even when it appears that its output is correct.
-
-I don't fully understand. But it appear that I need to call the exporter
-again within the exporting of the headings. This maybe is what helps
-getting down the subtrees and getting to the latex output.
-** DONE Incorporate from beamer how the do the theme settings
-- State "DONE"       from "TODO"       [2018-03-23 Fri 16:01]
-This looks like a fancy way to avoid repetition. Have a look too trying to
-imitate that behavior for the other personal tags of social media,url,phones.
-* DONE Markdown exporter for integration with hugo blog
 * Local Variables                                                   :ARCHIVE:
 # Local Variables:
 # eval: (add-hook 'after-save-hook #'org-hugo-export-wim-to-md-after-save :append :local)