From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/website: add commercial support section with Mind
Date: Fri, 24 Jan 2020 11:37:45 +0100 [thread overview]
Message-ID: <20200124103745.5132-1-arnout@mind.be> (raw)
Add a section to the support page for commercial support.
Add a box for Mind in that section.
This can be used as an example for other companies that provide
technical support for Buildroot.
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
There has been some discussion (off-list) about how to formalize
acceptance criteria for companies to be added to this commercial support
section, but without conclusion AFAIU. So I thought I'd go ahead and
just add one example that should be uncontroversial :-)
I have not looked at how it looks in the browser, because I don't know
how to deploy the website in a way that I can preview it...
---
docs/website/support.html | 37 +++++++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/docs/website/support.html b/docs/website/support.html
index 1a5ce9e225..5128eb291e 100644
--- a/docs/website/support.html
+++ b/docs/website/support.html
@@ -92,6 +92,43 @@
</div>
</div>
+ <div class="panel panel-primary">
+ <div class="panel-heading">Commercial support</div>
+ <div class="panel-body">
+ <p>In addition, the following companies are able to provide commercial support.</p>
+
+ <div class="row">
+ <div class="col-sm-4">
+ <div class="panel panel-default panel-sponsor">
+ <div class="panel-body">
+ <div class="col-sm-12" style="height: 150px;">
+ <a href="http://www.mind.be">
+ <img class="img-responsive center-block" src="images/mind-logo.png"/>
+ </a>
+ </div>
+ <div class="col-sm-12" style="height: 350px;">
+ <p><a href="http://www.mind.be">Mind</a> provides consultancy
+ and services (outsourcing and fixed price projects), as well as
+ support and training, in the field of Linux, Android and Open
+ Source software for embedded systems. Within this field, Mind's
+ core expertise is in Low-level software development, Networking,
+ Security and Multimedia.</p>
+
+ <p>Our team consists of highly skilled and enthusiastic embedded
+ software engineers with a passion for Open Source software and
+ for hardware.</p>
+
+ <p>We can provide services for the initial bringup of a
+ Buildroot-based system, developing extensions to Buildroot, and
+ long-term maintenance.</p>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+ </div>
+
</div><!--/.col-sm-10 -->
</div><!--/.row -->
</div>
--
2.21.1
next reply other threads:[~2020-01-24 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 10:37 Arnout Vandecappelle [this message]
2020-01-26 15:42 ` [Buildroot] [PATCH] docs/website: add commercial support section with Mind Yann E. MORIN
2020-01-27 16:49 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2020-02-05 15:08 Arnout Vandecappelle
2020-02-05 15:16 ` Romain Naour
2020-02-20 20:34 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200124103745.5132-1-arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox