This project was bootstrapped with Create React App. It is a single page app hosted on GitHub Pages in which user can prepare personal resume and download it in .pdf format.
The user should be able to insert data manually or by using LinkedIn account.
However, according to GitHub Pages:
#### Notes on client-side routing GitHub Pages doesn’t support routers that use the HTML5
pushStatehistory API under the hood (for example, React Router using
browserHistory). This is because when there is a fresh page load for a url like
http://user.github.io/todomvc/todos/42`, where /todos/42
is a frontend route, the GitHub Pages server returns 404 because it knows nothing of /todos/42
. If you want to add a router to a project hosted on GitHub Pages, here are a couple of solutions:
- You could switch from using HTML5 history API to routing with hashes. If you use React Router, you can switch to
hashHistory
for this effect, but the URL will be longer and more verbose (for example,http://user.github.io/todomvc/#/todos/42?_k=yknaj
). Read more about different history implementations in React Router. - Alternatively, you can use a trick to teach GitHub Pages to handle 404 by redirecting to your
index.html
page with a special redirect parameter. You would need to add a404.html
file with the redirection code to thebuild
folder before deploying your project, and you’ll need to add code handling the redirect parameter toindex.html
. You can find a detailed explanation of this technique in this guide.
In the other hand, LinkedIn oAuth2.0 process does not allow as a redirection uri a path with '#', which is integral part of hashRouting
for react-router-dom.
Please treat connect with LinkedIn feature, as a demo feature which could be run on proper server instead of GitHub Pages.
jsPDF
html2canvas
query-string
react-router-dom
node-sass
gh-pages