Go to file
JD 29b00a6f22 Merge pull request #5 from fluentdesk/dev
Merge from dev.
2015-10-27 10:28:02 -04:00
themes Compact: Collapse jobs > 4 and use safe dates. 2015-10-27 10:30:59 -04:00
.gitattributes Initial commit. 2015-10-06 14:20:47 -04:00
.gitignore Reorganize themes. 2015-10-26 04:57:06 -04:00
LICENSE.md Initial commit. 2015-10-06 14:20:47 -04:00
README.md Rename to fluent-themes. 2015-10-26 13:36:18 -04:00
package.json Unprivatize package.json. 2015-10-26 13:39:58 -04:00

README.md

fluent-themes

Resume themes for FluentCV and FluentCMD.

  • minimist: A no-frills theme.
  • modern: A middle of the road theme with a modern look 'n feel.
  • hello-world: A simple-as-possible example theme.
  • New themes forthcoming.

How It Works

Each theme lives in a folder, e.g., themes/informatic or themes/modern. The folder contains individual template files assembled by the theme author. Each template can be used to generate a single type of output file such as HTML, Word, or PDF. Template files are named according to this scheme...

[ OuputFormat ].[ InputFormat ]

...where [OuputFormat] and [InputFormat] are both one of html, pdf, md, txt, doc, or xml. For example:

  • html.html = An HTML template used to generate an HTML document.
  • doc.xml = An XML template used to generate an MS Word document.
  • pdf.html = An HTML template used to generate a PDF document.
  • md.txt = A text template used to generate a Markdown document.

This scheme ensures that theme template files have the "correct" file extension when the theme author is working with them in an editor—if your source data is XML then the template file will have an .xml extension regardless of whether you're ultimately generating an HTML page or a PDF document from that XML. It also provides a declarative mapping between a given input format (say, XML) and a given output file type (say, a Word doc or spreadsheet).

License

MIT. See LICENSE.md for details.