remote-jobs/test/fixtures/valid-incomplete/parsed-content/18f.remoteStatus.html
James Nylen 2682009c9f
Parse profile content into a JSON+HTML data structure (#445)
* A few minor tweaks

* Add toIdentifierCase function

* Use toIdentifierCase function to make profile content more code-friendly

* Improve "incomplete profile" indicator checks

In order to properly check the "incomplete profile" indicators, the
"Company blurb" section should exist.

* Return parsed HTML content for each company

* Test parsing of invisible "variation selector" character

* Strip out invisible "variation selector" character
2018-06-25 02:16:13 -05:00

7 lines
818 B
HTML

<p>18F employees live all over the country. We work out of homes in Dayton and Tucson, St. Louis and Chapel Hill &#x2014; and in federal buildings in San Francisco, Chicago, New York City, and Washington D.C.</p>
<p>That means many of our project teams are also made up of distributed employees working all over the country. For example, you may have a developer in Austin, a designer in Washington D.C., and a content strategist in Portland &#x2014; but they&#x2019;re all working on the same team and with the same partners.</p>
<p>Because we work on distributed teams so frequently, we&apos;ve developed certain strategies for working well as a collaborative operation.</p>
<p><a href="https://18f.gsa.gov/2015/10/15/best-practices-for-distributed-teams/">We have a &#x201C;remote first&#x201D; mindset.</a></p>