mirror of https://github.com/zulip/zulip.git
portico_pages: Add uniform structure HTML structure.
This commit ensures that the Attribution, Jobs, and Team pages all share a uniform structure to match those of other pages. This will simplify styling and should ensure greater confidence when modifying portico landing-page styles. The one CSS modification here, for the jobs page, maintains the space at the top of the "How we work" section.
This commit is contained in:
parent
dd73f7272d
commit
a5ff3d7e59
|
@ -17,14 +17,16 @@
|
|||
<div class="hero empty-hero"></div>
|
||||
<div class="main">
|
||||
<div class="padded-content">
|
||||
<h1>Website attributions</h1>
|
||||
<ul>
|
||||
<li>
|
||||
<b>On <a href="/for/business/">/for/business/</a> page:</b>
|
||||
<img alt="" src="{{ static('images/landing-page/companies/software-engineer.svg') }}" />
|
||||
<p>"<a href="https://iconscout.com/illustration/software-engineer-2043023">Software engineer Illustration</a>" By <a href="https://iconscout.com/contributors/delesign/illustrations">Delesign Graphic</a> is licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</p>
|
||||
</li>
|
||||
</ul>
|
||||
<div class="inner-content">
|
||||
<h1>Website attributions</h1>
|
||||
<ul>
|
||||
<li>
|
||||
<b>On <a href="/for/business/">/for/business/</a> page:</b>
|
||||
<img alt="" src="{{ static('images/landing-page/companies/software-engineer.svg') }}" />
|
||||
<p>"<a href="https://iconscout.com/illustration/software-engineer-2043023">Software engineer Illustration</a>" By <a href="https://iconscout.com/contributors/delesign/illustrations">Delesign Graphic</a> is licensed under <a href="https://creativecommons.org/licenses/by/4.0/">CC BY 4.0</a>.</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
@ -23,98 +23,97 @@
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div class="open-positions-top">
|
||||
<div class="main">
|
||||
<div class="padded-content markdown">
|
||||
<h1>Open positions</h1>
|
||||
<p>
|
||||
We are not actively recruiting for any roles at this time.
|
||||
However, if you are an experienced engineer, and you believe
|
||||
that your background would be a great fit for Zulip, please
|
||||
email us at <a
|
||||
href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your
|
||||
cover letter and resume.
|
||||
</p>
|
||||
<p>
|
||||
All openings are remote, or partially in-person in our San Francisco, CA office.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="how-we-work">
|
||||
<div class="main">
|
||||
<div class="padded-content markdown">
|
||||
<h1 id="how-we-work">
|
||||
How we work
|
||||
</h1>
|
||||
<p>
|
||||
<strong>Open source.</strong> The Zulip software is 100% free and
|
||||
open source. We're <a href="/team/">an open-source project</a> first,
|
||||
and we’re building a sustainable business as a means to support the
|
||||
project's growth and long-term future. We provide the same open-source
|
||||
code to our largest customers as to anyone with <code>git clone</code>.
|
||||
We get paid by enterprises for support, and by smaller companies using
|
||||
our rapidly-growing hosted service.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Open project.</strong> The Zulip project is one where people
|
||||
really do show up through the Internet and start making real changes.
|
||||
That doesn’t happen by accident; it takes work and thoughtfulness. Most
|
||||
of us work remotely, and we discuss our code and our plans in public, in
|
||||
writing, primarily asynchronously, using Zulip and GitHub.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Inclusive community.</strong> The Zulip community is made up of a
|
||||
mixture of volunteers and professionals from all walks of life. Diversity is
|
||||
one of our strengths, and we strive to be a community that welcomes and
|
||||
supports people of all backgrounds and identities from anywhere in the world.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Globally distributed.</strong> Our company is
|
||||
headquartered in San Francisco, CA, but like our community,
|
||||
we work from around the world. Our roles
|
||||
are open to all applicants without regard for location.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Maintainable software.</strong> Great
|
||||
software over time depends on a team’s shared
|
||||
understanding of a system and how to change it, as
|
||||
much as on the code itself. Beyond writing our
|
||||
code so it works today, we put equal effort into
|
||||
writing code, tests, comments, commit history,
|
||||
and <a href="https://zulip.readthedocs.io/en/latest/">documentation</a>
|
||||
clearly, to share with each other and future
|
||||
contributors our understanding of how and why it
|
||||
works, so we can build on it tomorrow.
|
||||
</p>
|
||||
<div class="main">
|
||||
<div class="padded-content">
|
||||
<div class="inner-content markdown">
|
||||
<div class="open-positions">
|
||||
<h1>Open positions</h1>
|
||||
<p>
|
||||
We are not actively recruiting for any roles at this time.
|
||||
However, if you are an experienced engineer, and you believe
|
||||
that your background would be a great fit for Zulip, please
|
||||
email us at <a
|
||||
href="mailto:jobs@zulip.com">jobs@zulip.com</a> with your
|
||||
cover letter and resume.
|
||||
</p>
|
||||
<p>
|
||||
All openings are remote, or partially in-person in our San Francisco, CA office.
|
||||
</p>
|
||||
</div>
|
||||
<div class="how-we-work">
|
||||
<h1 id="how-we-work">
|
||||
How we work
|
||||
</h1>
|
||||
<p>
|
||||
<strong>Open source.</strong> The Zulip software is 100% free and
|
||||
open source. We're <a href="/team/">an open-source project</a> first,
|
||||
and we’re building a sustainable business as a means to support the
|
||||
project's growth and long-term future. We provide the same open-source
|
||||
code to our largest customers as to anyone with <code>git clone</code>.
|
||||
We get paid by enterprises for support, and by smaller companies using
|
||||
our rapidly-growing hosted service.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Open project.</strong> The Zulip project is one where people
|
||||
really do show up through the Internet and start making real changes.
|
||||
That doesn’t happen by accident; it takes work and thoughtfulness. Most
|
||||
of us work remotely, and we discuss our code and our plans in public, in
|
||||
writing, primarily asynchronously, using Zulip and GitHub.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Inclusive community.</strong> The Zulip community is made up of a
|
||||
mixture of volunteers and professionals from all walks of life. Diversity is
|
||||
one of our strengths, and we strive to be a community that welcomes and
|
||||
supports people of all backgrounds and identities from anywhere in the world.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Globally distributed.</strong> Our company is
|
||||
headquartered in San Francisco, CA, but like our community,
|
||||
we work from around the world. Our roles
|
||||
are open to all applicants without regard for location.
|
||||
</p>
|
||||
<p>
|
||||
<strong>Maintainable software.</strong> Great
|
||||
software over time depends on a team’s shared
|
||||
understanding of a system and how to change it, as
|
||||
much as on the code itself. Beyond writing our
|
||||
code so it works today, we put equal effort into
|
||||
writing code, tests, comments, commit history,
|
||||
and <a href="https://zulip.readthedocs.io/en/latest/">documentation</a>
|
||||
clearly, to share with each other and future
|
||||
contributors our understanding of how and why it
|
||||
works, so we can build on it tomorrow.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div class="what-were-building">
|
||||
<div class="main">
|
||||
<div class="padded-content markdown">
|
||||
<h1 id="what-were-building">
|
||||
What we're building
|
||||
</h1>
|
||||
<p>
|
||||
People working together need to communicate with their teammates, and they
|
||||
also need to tune out the conversation to get work done. Teams tired of
|
||||
wasting time in meetings move discussion to email; tired of waiting all
|
||||
day for email replies, move to a team chat like Slack or IRC; and then
|
||||
team chat becomes an always-on meeting, leaving people constantly
|
||||
distracted, missing out on important conversations, or both.
|
||||
</p>
|
||||
<p>
|
||||
Zulip is reinventing chat so teams can accomplish more together. We've
|
||||
created a place where a conversation can shift seamlessly from the
|
||||
immediacy of chat to the reply-whenever efficiency of email, and back;
|
||||
where you can participate in the conversations that matter to you and
|
||||
efficiently tune out the rest, no matter whether you're there in real
|
||||
time, coming online after a morning hard at work, or returning from a
|
||||
vacation away from it.
|
||||
</p>
|
||||
<div class="padded-content">
|
||||
<div class="inner-content markdown">
|
||||
<h1 id="what-were-building">
|
||||
What we're building
|
||||
</h1>
|
||||
<p>
|
||||
People working together need to communicate with their teammates, and they
|
||||
also need to tune out the conversation to get work done. Teams tired of
|
||||
wasting time in meetings move discussion to email; tired of waiting all
|
||||
day for email replies, move to a team chat like Slack or IRC; and then
|
||||
team chat becomes an always-on meeting, leaving people constantly
|
||||
distracted, missing out on important conversations, or both.
|
||||
</p>
|
||||
<p>
|
||||
Zulip is reinventing chat so teams can accomplish more together. We've
|
||||
created a place where a conversation can shift seamlessly from the
|
||||
immediacy of chat to the reply-whenever efficiency of email, and back;
|
||||
where you can participate in the conversations that matter to you and
|
||||
efficiently tune out the rest, no matter whether you're there in real
|
||||
time, coming online after a morning hard at work, or returning from a
|
||||
vacation away from it.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
@ -22,7 +22,7 @@ contributors, and more than 75 with 100+ commits." %}
|
|||
|
||||
<div class="main">
|
||||
<div class="padded-content markdown">
|
||||
<div class="team">
|
||||
<div class="inner-content team">
|
||||
<p>
|
||||
Over 1000 people have contributed to the Zulip
|
||||
codebase, from high school students to 30 year
|
||||
|
|
|
@ -2576,11 +2576,7 @@ button {
|
|||
margin: 20px 0 7px;
|
||||
}
|
||||
|
||||
.portico-landing.jobs .open-positions-top .padded-content {
|
||||
padding-bottom: 0;
|
||||
}
|
||||
|
||||
.portico-landing.jobs .how-we-work .padded-content {
|
||||
.portico-landing.jobs .how-we-work {
|
||||
padding-top: 25px;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue