-
Notifications
You must be signed in to change notification settings - Fork 0
/
support.html
66 lines (47 loc) · 2.84 KB
/
support.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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset='utf-8'>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width,maximum-scale=2">
<link rel="stylesheet" type="text/css" media="screen" href="/chromium/assets/css/style.css?v=75652f13ad28bbdba51257ebb499b56d9aabebef">
<!-- Begin Jekyll SEO tag v2.6.1 -->
<title>Support | chromium</title>
<meta name="generator" content="Jekyll v3.9.0" />
<meta property="og:title" content="Support" />
<meta property="og:locale" content="en_US" />
<meta name="description" content="Run a portable Chromium using dotnet 6 and nuget." />
<meta property="og:description" content="Run a portable Chromium using dotnet 6 and nuget." />
<meta property="og:site_name" content="chromium" />
<script type="application/ld+json">
{"@type":"WebPage","url":"/chromium/support.html","headline":"Support","description":"Run a portable Chromium using dotnet 6 and nuget.","@context":"https://schema.org"}</script>
<!-- End Jekyll SEO tag -->
</head>
<body>
<!-- HEADER -->
<div id="header_wrap" class="outer">
<header class="inner">
<a id="forkme_banner" href="https://github.com/devlooped/chromium">View on GitHub</a>
<h1 id="project_title">chromium</h1>
<h2 id="project_tagline">Run a portable Chromium using dotnet 6 and nuget.</h2>
</header>
</div>
<!-- MAIN CONTENT -->
<div id="main_content_wrap" class="outer">
<section id="main_content" class="inner">
<h1 id="support">Support</h1>
<p>Support is typically available thorugh GitHub Discussions and Issues.</p>
<p><strong>Found a bug? File an issue.</strong> If you found something that isn’t working as expected and you can reproduce it, go to the repo Issues tab and file an issue.</p>
<p><strong>Want a new feature? Start a discussion.</strong> It’s always good to start a discussion (Discussion tab in the project, Ideas category) to explain the problem you’re trying to solve before jumping in with the pull request. We may already have a solution in place or have an idea on ways to solve that issue. After the details are nailed down, we will migrate the discussion to a proper Issue (with the <code class="language-plaintext highlighter-rouge">enhancement</code>) label. At that point, we’d love to see your PRs :).</p>
<p>Consider <a href="https://github.com/sponsors/devlooped">sponsoring</a> the project to get priority support and many other perks!</p>
</section>
</div>
<!-- FOOTER -->
<div id="footer_wrap" class="outer">
<footer class="inner">
<p class="copyright">chromium maintained by <a href="https://github.com/devlooped">devlooped</a></p>
<p>Published with <a href="https://pages.github.com">GitHub Pages</a></p>
</footer>
</div>
</body>
</html>