You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When it comes to resume writing and then sharing the template you put so much time into, it's very common to just strip out the personal bits and call it a template. However, this puts the consumer into a spot where they are somewhat-obligated to stick with your own personal requirements.
For instance, a resume should typically have most important to least important from top to bottom, and an education section will naturally drop lower throughout most careers.
Rather than a monolithic single page design, if shortcodes were used, your exampleSite could provide a single index page with example usage of those shortcodes.
This also comes with the benefit of keeping content separate from configuration and code, and will hugely simplify the logic used throughout the front page assembly.
I have a resume .tex template with similar code logic that you may find interesting.
(... this also make your time with hugo less exhausting, because {{ .Site.Params.about.content | markdownify }} and other filter-based solutions will simply not be needed)
The text was updated successfully, but these errors were encountered:
When it comes to resume writing and then sharing the template you put so much time into, it's very common to just strip out the personal bits and call it a template. However, this puts the consumer into a spot where they are somewhat-obligated to stick with your own personal requirements.
For instance, a resume should typically have most important to least important from top to bottom, and an
education
section will naturally drop lower throughout most careers.Rather than a monolithic single page design, if shortcodes were used, your exampleSite could provide a single index page with example usage of those shortcodes.
This also comes with the benefit of keeping content separate from configuration and code, and will hugely simplify the logic used throughout the front page assembly.
I have a resume .tex template with similar code logic that you may find interesting.
(... this also make your time with hugo less exhausting, because
{{ .Site.Params.about.content | markdownify }}
and other filter-based solutions will simply not be needed)The text was updated successfully, but these errors were encountered: