jsonresume / jsonresume-theme-boilerplate Goto Github PK

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

The Theme Development section mentioned about getting values from JSONResume via Handlebars but I would like to know where the data is stored. Is it somewhere within the boilerplate directory?

Because while working offline I noticed this in Terminal:
Could not find: /xxx/xxx/xxx/jsonresume-theme-boilerplate/resume.json Using example resume.json from resume-schema instead... Using local theme.

The project could not be analyzed because of maven build errors. Please review the error messages here. Another build will be scheduled within 24 hours. If the build is successful this issue will be closed, otherwise the error message will be updated.

_{This is an automated GitHub Issue created by Sonatype DepShield. GitHub Apps, including DepShield, can be managed from the Developer settings of the repository administrators.}

I forked this boilerplate repo and added a Lorem ipsum to the top:

https://github.com/MikelArnaiz/jsonresume-theme-boilerplate/blob/2289e54fdbe9f12a178cdeb1a441a757bbdda38b/resume.hbs#L14-L17

However when running resume serve that is not shown:

Am I doing anything wrong?

General

Where is actually the right place to discuss export related "rules"?
Because these kind of ideas/issues (like #6) are related to any export format (json->pdf, json->html, json->txt) and are not supposed to be relevant in the schema definition IMO.

Ordering

Currently there is no definition (or i can't find) on how to tell the export middleware how you'd like to sort the main categories. This is also useful (maybe mandatory?) for the basics entries. Let me show you some use cases:

• Different countries have different priorities or strict rules on the basic information order
• Someone going the academic way wants to have his education section above the work section

And no, this should not be the function of the "theme" to force me the way it should visualize my data. A theme (and any kind of export middleware) should define how it visualizes the data, but the ordering should be also in my hand.

Also I think this is nothing schema-related, so it should be a separate definition which could also solve the #6?

Interested in your thoughts :)

Hello,

I was playing with the boilerplate and other themes like flat that is running with this boilerplate as well and there are two fields that are not compliant with the JSON Schema in work.hbs https://jsonresume.org/schema/ https://github.com/jsonresume/jsonresume-theme-boilerplate/blob/master/partials/work.hbs

Faulty fields:

• company should be name
• website should be url

Thanks,

Some kind of localization for the descriptions/headings would be nice. Best case would be seperate localization files + picking language in cli.

Should there not be a after the last partial to close the

It would be great to add a basic unit test, perhaps via .travis.yml to help developers confirm their theme is working.

I would like to define words that need to be bolded in resume.json, how would I go about passing this to handlebars to be rendered as HTML? I just needing the simplest solution

Lets say i've got this json

  "work": [
    {
      "summary": "Pied Piper is a multi-platform technology based on a proprietary universal compression algorithm that has consistently fielded high Weisman Scores™ that are not merely competitive, but approach the theoretical limit of lossless compression.",
      "highlights": []
    }
  ]

I'm attempting to render it like this -

Pied Piper is a multi-platform technology based on a proprietary universal compression algorithm that has consistently fielded high Weisman Scores™* that are not merely competitive, but approach the theoretical limit of lossless compression.

Depshield will be deprecated on Monday December 12th

Please install our new product, Sonatype Lift with advanced features

https://semaphoreci.com/blog/2018/03/27/phantomjs-is-dead-use-chrome-headless-in-continuous-integration.html

You should use the standard .hbs file-ending for handlebars templates.
Then editors can automatically use the right syntax highlighting and people know what to expect!

Could you please mark this repository as a "Template repository". After marking this repository as a template there will appear an "Use this template" button on the main page of this repository.

The schema has support for certifications, but there is no listing output for it in the boilerplate, and thus none in the themes that use the boilerplate.

Can we please add a section for certificates in the boilerplate hbs file.