public
Last active

add position

  • Download Gist
basic_form.html
HTML
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
<div class="guided-edit">
{>_close_action/}
{<closeText}{i18n_text_plain__close}{/closeText}
{?firstTaskTitleString}
<h1>{firstTaskTitleString|s}</h1>
{/firstTaskTitleString}
<form class="standard-form" id="{name}_id" name="{name}" method="{method}" action="{action}">
<fieldset>
<legend>{i18n_text_plain__what_is_your_industry}</legend>
<ul>
<li>
{#industryChooser choose=i18n__text_plain__choose}
{>singleSelect/}
{/industryChooser}
</li>
</ul>
 
{>action_params/}
{<saveText}{i18n__text_plain__save}{/saveText}
{<skipText}{i18n__text_plain__skip}{/skipText}
 
{>_guided_edit_flow_hidden/}
</fieldset>
</form>
{>_guided_edit_flow/}
</div>

Hey thanks for the interesting article over @ linkedin. Would be very interesting to see a future article on how you deal with I18n in your front-end stack. Cheers.

Our i18n solutions are built inhouse, we dont crowd source and it is extensive and rich. We would never rewrite all this on client.

We have a server-side solution to this that seamlessly works across different jvm stacks.

I would love to share more details here, but that will be the topic of next few posts. stay tuned.

Highly encourage you to read this

http://engineering.linkedin.com/translations/linkedin-translation-whats-name

Very interesting article over @linked in. How do you take care of SEO issues if your presentation is assembled at the browser?

@amlanc - this can be achieved parsing dust.js template with Node.JS in the server-side. After that you can send to the client-side the result. I could user Rhino for parsing too.

Check the section: Leaving JSPs in the dust, the fifth topic, Server side support.
http://engineering.linkedin.com/frontend/leaving-jsps-dust-moving-linkedin-dustjs-client-side-templates

Please sign in to comment on this gist.

Something went wrong with that request. Please try again.