- ö gets mangled, ö (o and U+0308) results in "o?"
- ü doesn't get mangled and survives in the PDF for some reason
- When you return to the page all of ö, ü and ß are replaced by their HTML entities
You can enter math mode and do fun stuff, but with people not knowing that it's LaTeX underneath this probably just invites fun errors when people use $ to mean $.
I've written my CV in LaTeX 1½ years ago (mostly because I didn't have a good-looking template in Word and was too lazy to build one myself) and I remember that I had to fight hard against moderncv to get it to do the things I wanted. It's not exactly flexible.
In the screenshots, I see the same problem that I was facing with an [offline tool]:
There are too many hyphens all over the place! For example in this screenshot:
... you can see "Devel-oped" "function-ality" "con-version" "expo-sure" "communi-cations"
Most other word processors can justify text without too much hyphenation. The TeX system seems to work differently (at least by default).
Incorrect domain of Email-id! (only gmail, yahoo, msn, outlook, rediff, hotmail are supported for now).
Do you have plans to support a greater number of domains soon?
In that case, you should check against a blacklist instead: http://torvpn.com/temporaryemail.html
This is interesting, and maybe I'll give it a try, but
how are you planning to monetize it?
(disclaimer I am the cofounder of sharelatex.com)
By the way, I don't know where are you from, but this tool looks cool enough for Nordic countries. In particular, you could target easily carrier centers in Danish universities (http://bss.au.dk/knowledge-exchange/career-centre/). These centers offer free advice for students' CV. I see this service being advised or even used there (like the students upload his CV on the system and gets help virtually).
I write it in Markdown, and then build it into both a PDF and HTML. Then I use Github Pages to publish both with a simple push.
Unfortunately, the preview doesn't work for me. Do you have some problems or is it a matter of only half-filling the form?
BTW What's "Pincode" in the contacts section? Zip/postal code?
EDIT: No, got it. You need to click save on each section. Unfortunately it doesn't handle non-ascii characters.
And the design is inspired from moderncv, a great LaTeX package :)
At first it was using LaTeX to produce the PDF, but now it is just HTML/CSS templating, and the pdf rendering is done using wkhtmltopdf.
Actually, handling special characters was one of the reasons to switch to HTML.
I know this is focused on a specific domain, but you have serious competition with these dudes.
Any chance to make an option to download the LaTeX code for manual tailoring?
10/Dec/2013 [Short Month]
10/December/2013 [Long Month]
Probably there's a typo in first sample. Also DD > 12 helps unambiguously identify DD from MM.
Obviously, date formats are different for each locale; en-US: MM/DD/YYYY, en-GB: DD/MM/YYYY, de-DE: DD.MM.YYYY.
Have you seen templates hosted at "LaTex Templates"?  I would be curious to know if you're using them or plan to use them in the future.
…which use hyphen in date ranges
I got bit by propaganda too last year.
I am a little nervous at the moment because I am picking up latex again in some weeks after months of not using it and I wonder what has changed and what I have forgotten since then.
Suggestion: A lot of requests going to the server when creating a resume. Use local storage for storing the data and send it to the server once when user clicks the save button.
You have to be smart to send the data that is changed or client side compression is another option.
(disclosure: we are building a tool for researchers to write better papers: bohr.launchrock.com)
- Felt compelled to fill in "Personal" section, even though specifying Gender, DOB, Nationality is very unprofessional. Only because it is a section that cannot be removed, and became a Giant Bold "PERSONAL" at the bottom of my resume that was empty -- so if I can't remove it, I guess I better have -something- there !
>> agreed. have listed it as a bug to be fixed in next release! sorry for that.
- so then I fill in some hobbies, at least, and it won't wrap along the margins correctly, as though I shouldn't have so many interesting hobbies for these templates? Looks very bad when everything else does wrap, makes it look shoe-horned.
>> agreed. the list of hobbies & languages are supposed to be small. if you need a full fledged hobbies / languages space you can create a custom section for it & list everything there :) as for wrapping. we will try to fix it.
- holding multiple positions and titles in a single company, as many as 4 in 3 years, and 3 in 3 years for the next job, I prefer to list them in descending chronological order under the same section, describing the various 'accomplishments' underneath as opposed to describing 4 different "jobs".
- i had to forgoe this information, and instead list all 3 or 4 titles as a single sentance, comma-seperated, which word wraps with a hyphen and looks confusing. I guess I would have to pick my "favorite" title, and stick with it.
>> agreed. will brainstorm on how we can fix this. how would you do this in linked-in? it would be another position right? we are asking this as we are trying to keep 1:1 compatibility with linkedin since that data will need to be copied in the same format here.
- No place, really, to list the "business unit" or "department" under which those titles were held. Both the titles and the department are far more telling about the employment history than any bulletpoint can say.
- I would also have to add a comma, and a business unit/department, after "Company", if I wanted this information present. I do, it is very vital information, especially in a large corporation like $#!^, where discovering which dept. to contact for verifying employment would be impossible otherwise.
>> agreed. we missed location of office & department in positions. will add them soon.
- A number of times 'preview' did not reflect what I had recently saved. I did notice the baloon tip to save the first time I changed templates. I'm very sure I saved it vigorously before preview. Feels like I'm hitting a server farm that isn't replicating quickly enough.
>> we are on Google App Engine (GAE) with 3 idle instances & with auto scaling feature of GAE (best in class) this should not have been the case. But we went totally viral today! We will see what we can do about this.
- preferred page breaks on sections are needed, I don't like seeing a single bullet point on the top of page 2 describing something I did at a job on the bottom of page 1. I might be tempted to simply remove an accomplishment to make it break where I'd like! Only to decide against it, or other padding methods, because I decide on a different template or add or remove another line above it.
>> agreed. we are brainstorming on pagebreaks & greater control on footers.
- Here I've avoided the privacy invasion of Facebook, Linked In, Twitter, and all of these other data mining whores, but just to provide you feedback I'm suddenly pushing data through Google anyway. Makes me consider where my data is actually stored -- an AWS cluster, a google app engine database? Now I'm going to have to go back, re-login, and anonymize my data I've provided you. sigh.
>> we chose to store data on GAE since it provides the best security that can be provided. Its certainly much more than what a 2 member dev team can provide. as for the data, we promise not to share that data with anyone without your consent. is there anything more we can do in this regard?
>> we are on cloud. (GAE & AWS to be more specific) and we are there not because they are cheap. they do cost quiet some money! we chose them because we think they actually can provide much more security, reliability & performance that a small dev team can with an owned instance of sever & database. we would surely think of having our own server, database etc. when we actually can afford them.
- Nobody likes seeing & in their resume when editing. It looks like it decodes correctly in preview, but why should we have to be confused by it in editing? As software engineer, I feel compelled to correct it each time -- it frightens me that it could become doubly-escaped, becoming && later when I'm not looking, when the & in & gets re-encoded again sometime later, and make me look like a real idiot to a prospective employer.
>> agreed. will add that as a bug to be fixed in next release.
- I would not pay for your service: #1: Privacy and #2 Templating issues (described in previous feedback) -- my own resume made in MS Word simply looks much better.
>> have a look at some samples made on our site:
and if you prove us your similar looking template on word doc is better after print we will shutdown the service. period.
- I would recommend your service to others: who don't really care about who has their address, phone number, date of birth stored on some-random-harddisk, and have a very difficult time in MS Word. When I worked as a tutor in a college, I assisted at least 100 students with their resumes each quarter -- you would want to consider advertising in such spaces, though many would be inaccessible by you by their tax-funded nature: Workplace placement programs and libraries, for instance.
>> yes students are our first goto market since they would be our early adopters. we are thinking on how we can reach them.
- I would actually pay for your service if you did anything more useful than templating (and the formatting and limitations previously mentioned were resolved). For instance: providing shorthand.com/firstname-lastname URL's for a web version, exporting to .doc, and finishing out the many unfinished concepts already here.
>> yes. we know you would not pay for the currently running software online. and thats why its free :) we have premium templates & public resumes in our roadmap. but we are still thinking on a path to choose.
- Your pintrist referral link at the bottom just makes you look like a cheap, cheap, attention-seeking whore.
>> yes. sadly we are in attention seeking mode right now & we would not make any balls about it. we have worked on this for a year now & we think it can serve the people for good. we want it to reach as many eyeballs as possible and get as many feedbacks as possible.
Thank you for your time. Appreciate it. Hope this reply makes you feel much better about the whole thing :)