Skip to content

Commit b4afbb5

Browse files
authored
Add testimonials (#12)
1 parent 8844c09 commit b4afbb5

3 files changed

Lines changed: 133 additions & 6 deletions

File tree

‎README.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ transition to open source under a fiscal sponsorship agreement with
66
published as a fully static site through GitHub Pages.
77

88
The site has two pages: the main page in `index.html`, and John Spicer's
9-
announcement note with the transition FAQ in `announcement.html` (served at
10-
`/announcement/`). Both are built on a small Jekyll scaffold:
9+
announcement note with testimonials and the transition FAQ in
10+
`announcement.html` (served at `/announcement/`). Both are built on a small Jekyll scaffold:
1111

1212
- `_layouts/default.html` – page shell
1313
- `_includes/head.html`, `header.html`, `footer.html` – shared chrome

‎announcement.html‎

Lines changed: 63 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,18 @@
33
title: What's Next for EDG
44
permalink: /announcement/
55
description: >-
6-
A note from John Spicer on EDG's C++ front end becoming open source, with
7-
answers to frequently asked questions about the transition.
6+
A note from John Spicer on EDG's C++ front end becoming open source,
7+
testimonials from the C++ community, and answers to frequently asked
8+
questions about the transition.
89
---
910
<section class="hero hero--compact" aria-labelledby="hero-title">
1011
<div class="container">
1112
<p class="eyebrow eyebrow--on-dark">The EDG open source transition</p>
1213
<h1 id="hero-title">What’s next for EDG</h1>
13-
<p class="lead">A note from John Spicer on EDG's move to open source, followed by answers to the questions EDG users are most likely to ask about the transition.</p>
14+
<p class="lead">A note from John Spicer on EDG's move to open source, followed by testimonials from across the C++ community and answers to the questions EDG users are most likely to ask about the transition.</p>
1415
<div class="hero__actions">
1516
<a class="button button--primary" href="#note">Read the note</a>
17+
<a class="button button--ghost" href="#testimonials">Read the testimonials</a>
1618
<a class="button button--ghost" href="#faq">Jump to the FAQ</a>
1719
</div>
1820
</div>
@@ -58,7 +60,64 @@ <h2 id="note-title">A note from John Spicer</h2>
5860
</div>
5961
</section>
6062

61-
<section id="faq" class="section section--alt" aria-labelledby="faq-title">
63+
<section id="testimonials" class="section section--alt" aria-labelledby="testimonials-title">
64+
<div class="container">
65+
<p class="eyebrow">Testimonials</p>
66+
<h2 id="testimonials-title">What people are saying</h2>
67+
<p class="section__lead">Reflections on EDG and its move to open source from the C++ Alliance, the C++ standards community and EDG users.</p>
68+
69+
<div class="testimonials">
70+
<figure class="testimonial">
71+
<blockquote>
72+
<p>Many C++ developers have never heard of EDG, but a lot of them have used it. It has been working quietly inside compilers and tools for decades, and it’s one of the most exacting C++ front ends there is. Now, anyone can read that code, learn from it and build on it. Our job at the C++ Alliance is to support the project, not run it. Opening EDG was President John Spicer’s decision, and he has taken real care to do it in a way that works for the people who depend on it.</p>
73+
</blockquote>
74+
<figcaption>
75+
<span class="testimonial__name">Harry Bott</span>
76+
<span class="testimonial__role">CEO of C++ Alliance</span>
77+
</figcaption>
78+
</figure>
79+
80+
<figure class="testimonial">
81+
<blockquote>
82+
<p>EDG has a very special place in my heart. It was the first compiler I ever tinkered with, and I was incredibly fortunate to be given the opportunity to work on it, alongside some of the great names in the C++ community. I have enormous respect for what EDG has built over nearly four decades.</p>
83+
<p>I'm delighted to see the EDG C++ Front End begin a new chapter as an open-source project, and particularly excited to see the C++ Alliance investing in its future. One of the things I have come to greatly appreciate about the Alliance is its willingness to invest in talented people and ambitious projects that can make a real contribution to the future of C++. The EDG C++ Front End feels like a natural fit for that mission.</p>
84+
<p>I'm very excited to see what the Alliance and the wider C++ community can build on the extraordinary foundation EDG has created.</p>
85+
</blockquote>
86+
<figcaption>
87+
<span class="testimonial__name">Nina Ranns</span>
88+
<span class="testimonial__role">ISO C++ committee vice convener, Standard C++ Foundation vice chair, EDG and GCC compiler engineer, C++ consultant at NMLB ltd.</span>
89+
</figcaption>
90+
</figure>
91+
92+
<figure class="testimonial">
93+
<blockquote>
94+
<p>I have known EDG since I became involved in C++ standardization around 1997. I have encountered its work from several vantage points: as a GCC developer who sought to bring EDG-level diagnostics to GCC, in academic research (including the early implementation of the IPR), and in industry as the architect of a product serving millions of C++ developers. I offer these thoughts in a personal capacity, drawing in part on my former work at Microsoft, not speaking for the company.</p>
95+
<p>What has impressed me about EDG's front end is the quality of its engineering. It takes both the finer points of the C++ standard and the messy reality of compatibility with other compilers seriously. We sometimes joke that EDG is more compatible with other C++ front ends than those front ends are with themselves. Behind the joke is a serious achievement: engineers willing to wrestle with the hard cases, not just implement the easy ones.</p>
96+
<p>I designed the IFC format and developed its specification as part of the implementation of C++20 Modules. I had the pleasure of working with EDG engineers on that effort. Their feedback was exacting, constructive, and grounded in the realities of implementing C++. Our conversations made the specification stronger. Just as memorable was the thoughtful, generous way they engaged with the work.</p>
97+
<p>John Spicer's technical leadership and longstanding involvement in C++ standardization have meant a great deal to me personally. His feedback has contributed to my work on constexpr, modules, concepts, and to advocacy for safety in C++. He brings deep technical judgment to difficult questions and takes other people's ideas seriously. That combination is rare, and it has helped both the language and the people working to advance it.</p>
98+
<p>I am delighted to see EDG become open source. It gives more of the C++ community a chance to learn from and to contribute to the work John and so many exceptional EDG engineers have built over the years. I look forward to what we can make possible together in this next chapter.</p>
99+
</blockquote>
100+
<figcaption>
101+
<span class="testimonial__name">Gabriel Dos Reis</span>
102+
<span class="testimonial__role">Technical Fellow at Susquehanna International Group</span>
103+
</figcaption>
104+
</figure>
105+
106+
<figure class="testimonial">
107+
<blockquote>
108+
<p>Veracode depends on the EDG compiler frontend for our Static Application Security Testing (SAST) of our customers’ C++ applications. We have found it to be of the highest quality and to live up to its reputation as an industry standard.</p>
109+
<p>EDG’s broad range of support for the different C++ language versions and compatibility modes with different C++ compiler vendors is invaluable in enabling us to support parsing virtually any C/C++ code from our customer base. John Spicer is a pleasure to work with and always responsive, helpful, and supportive. We are very happy to know he will be continuing to steward the EDG technology.</p>
110+
</blockquote>
111+
<figcaption>
112+
<span class="testimonial__name">Bruce Duncan</span>
113+
<span class="testimonial__role">Director, Software Engineering at Veracode</span>
114+
</figcaption>
115+
</figure>
116+
</div>
117+
</div>
118+
</section>
119+
120+
<section id="faq" class="section" aria-labelledby="faq-title">
62121
<div class="container">
63122
<p class="eyebrow">FAQ</p>
64123
<h2 id="faq-title">Frequently asked questions</h2>

‎assets/css/main.css‎

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -684,6 +684,74 @@ p {
684684
color: var(--muted);
685685
}
686686

687+
/* Testimonials */
688+
689+
.testimonials {
690+
display: grid;
691+
gap: 1.25rem;
692+
max-width: 52rem;
693+
}
694+
695+
.testimonial {
696+
position: relative;
697+
margin: 0;
698+
padding: 2rem 2rem 1.75rem 4.5rem;
699+
border: 1px solid var(--border);
700+
border-left: 4px solid var(--accent);
701+
border-radius: var(--radius);
702+
background: #fff;
703+
}
704+
705+
.testimonial::before {
706+
content: "\201C";
707+
position: absolute;
708+
top: 1.25rem;
709+
left: 1.25rem;
710+
font-size: 4rem;
711+
font-weight: 700;
712+
line-height: 1;
713+
color: var(--accent-soft-border);
714+
}
715+
716+
.testimonial blockquote {
717+
margin: 0;
718+
font-size: 1.0625rem;
719+
line-height: 1.7;
720+
}
721+
722+
.testimonial blockquote p {
723+
margin-bottom: 1rem;
724+
}
725+
726+
.testimonial figcaption {
727+
display: flex;
728+
flex-direction: column;
729+
gap: 0.15rem;
730+
margin-top: 1.5rem;
731+
padding-top: 1.25rem;
732+
border-top: 1px solid var(--border);
733+
}
734+
735+
.testimonial__name {
736+
font-weight: 700;
737+
}
738+
739+
.testimonial__role {
740+
font-size: 0.95rem;
741+
color: var(--muted);
742+
}
743+
744+
@media (max-width: 520px) {
745+
.testimonial {
746+
padding: 3.5rem 1.25rem 1.5rem;
747+
}
748+
749+
.testimonial::before {
750+
top: 1rem;
751+
font-size: 3.25rem;
752+
}
753+
}
754+
687755
/* FAQ */
688756

689757
.faq {

0 commit comments

Comments
 (0)