I18nize views/pages (#18771)
This commit is contained in:
yheuhtozr
GitHub
parent
14b28a1a9c
commit
ce23832988
67 changed files with 1196 additions and 46 deletions
21
app/views/credits/_pricing.en.html.erb
Normal file
21
app/views/credits/_pricing.en.html.erb
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
<div class="credit-price" data-num="1">
|
||||
<div class="credit-amount" data-num="1">1+</div>
|
||||
$5/per credit
|
||||
</div>
|
||||
<div class="credit-price" data-num="10">
|
||||
<div class="credit-amount" data-num="10">10+</div>
|
||||
$4/per credit</div>
|
||||
<div class="credit-price" data-num="100">
|
||||
<div class="credit-amount" data-num="100">
|
||||
100+
|
||||
</div>
|
||||
$3/per credit</div>
|
||||
<div class="credit-price" data-num="1000">
|
||||
<div class="credit-amount" data-num="1000">
|
||||
1000+
|
||||
</div>
|
||||
$2.50/per credit
|
||||
</div>
|
||||
<br />
|
||||
</div>
|
||||
<p class="bulk-description"><em>Contact <%= contact_link(additional_info: { subject: "Custom Bulk Pricing/Partnerships" }) %> for custom bulk pricing and partnerships.</em></p>
|
||||
21
app/views/credits/_pricing.fr.html.erb
Normal file
21
app/views/credits/_pricing.fr.html.erb
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
<div class="credit-price" data-num="1">
|
||||
<div class="credit-amount" data-num="1">1+</div>
|
||||
$5/per credit
|
||||
</div>
|
||||
<div class="credit-price" data-num="10">
|
||||
<div class="credit-amount" data-num="10">10+</div>
|
||||
$4/per credit</div>
|
||||
<div class="credit-price" data-num="100">
|
||||
<div class="credit-amount" data-num="100">
|
||||
100+
|
||||
</div>
|
||||
$3/per credit</div>
|
||||
<div class="credit-price" data-num="1000">
|
||||
<div class="credit-amount" data-num="1000">
|
||||
1000+
|
||||
</div>
|
||||
$2.50/per credit
|
||||
</div>
|
||||
<br />
|
||||
</div>
|
||||
<p class="bulk-description"><em>Contact <%= contact_link(additional_info: { subject: "Custom Bulk Pricing/Partnerships" }) %> for custom bulk pricing and partnerships.</em></p>
|
||||
24
app/views/credits/_purchase_faq.en.html.erb
Normal file
24
app/views/credits/_purchase_faq.en.html.erb
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
<details>
|
||||
<summary>
|
||||
How many credits does one listing cost?
|
||||
</summary>
|
||||
<div>
|
||||
<p>
|
||||
All listings cost <strong>1 credit</strong>, except:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
<strong>products/tools: 5 credits</strong>
|
||||
</li>
|
||||
<li>
|
||||
<strong>job listings: 25 credits</strong>
|
||||
</li>
|
||||
</ul>
|
||||
<p>
|
||||
Buying more credits upfront makes listings more cost-effective.
|
||||
</p>
|
||||
<p>
|
||||
25 credits purchased today costs $100. 25 credits purchased individually will cost $125, etc.
|
||||
</p>
|
||||
</div>
|
||||
</details>
|
||||
24
app/views/credits/_purchase_faq.fr.html.erb
Normal file
24
app/views/credits/_purchase_faq.fr.html.erb
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
<details>
|
||||
<summary>
|
||||
How many credits does one listing cost?
|
||||
</summary>
|
||||
<div>
|
||||
<p>
|
||||
All listings cost <strong>1 credit</strong>, except:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
<strong>products/tools: 5 credits</strong>
|
||||
</li>
|
||||
<li>
|
||||
<strong>job listings: 25 credits</strong>
|
||||
</li>
|
||||
</ul>
|
||||
<p>
|
||||
Buying more credits upfront makes listings more cost-effective.
|
||||
</p>
|
||||
<p>
|
||||
25 credits purchased today costs $100. 25 credits purchased individually will cost $125, etc.
|
||||
</p>
|
||||
</div>
|
||||
</details>
|
||||
|
|
@ -24,54 +24,12 @@
|
|||
|
||||
<script src="https://js.stripe.com/v3/"></script>
|
||||
|
||||
<p class="hook-description">Credits are used for <a href="/listings"><%= community_name %> listings</a> as well as upcoming products and services.</p>
|
||||
<p class="hook-description"><%= t("views.credits.new.hook.text_html", listings: link_to(t("views.credits.new.hook.listings", community: community_name), listings_path)) %></p>
|
||||
|
||||
<div style="margin-top: 30px; text-align: center">
|
||||
<div class="credit-price" data-num="1">
|
||||
<div class="credit-amount" data-num="1">1+</div>
|
||||
$5/per credit
|
||||
</div>
|
||||
<div class="credit-price" data-num="10">
|
||||
<div class="credit-amount" data-num="10">10+</div>
|
||||
$4/per credit</div>
|
||||
<div class="credit-price" data-num="100">
|
||||
<div class="credit-amount" data-num="100">
|
||||
100+
|
||||
</div>
|
||||
$3/per credit</div>
|
||||
<div class="credit-price" data-num="1000">
|
||||
<div class="credit-amount" data-num="1000">
|
||||
1000+
|
||||
</div>
|
||||
$2.50/per credit
|
||||
</div>
|
||||
<br />
|
||||
</div>
|
||||
<p class="bulk-description"><em>Contact <%= contact_link(additional_info: { subject: "Custom Bulk Pricing/Partnerships" }) %> for custom bulk pricing and partnerships.</em></p>
|
||||
<details>
|
||||
<summary>
|
||||
How many credits does one listing cost?
|
||||
</summary>
|
||||
<div>
|
||||
<p>
|
||||
All listings cost <strong>1 credit</strong>, except:
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
<strong>products/tools: 5 credits</strong>
|
||||
</li>
|
||||
<li>
|
||||
<strong>job listings: 25 credits</strong>
|
||||
</li>
|
||||
</ul>
|
||||
<p>
|
||||
Buying more credits upfront makes listings more cost-effective.
|
||||
</p>
|
||||
<p>
|
||||
25 credits purchased today costs $100. 25 credits purchased individually will cost $125, etc.
|
||||
</p>
|
||||
</div>
|
||||
</details>
|
||||
<%= render "pricing" %>
|
||||
|
||||
<%= render "purchase_faq" %>
|
||||
<details>
|
||||
<summary>
|
||||
<%= params[:organization_id].present? ? t("views.credits.new.status.subtitle.org", name: @purchaser.name) : t("views.credits.new.status.subtitle.user") %>
|
||||
|
|
|
|||
51
app/views/pages/_coc_text.fr.html.erb
Normal file
51
app/views/pages/_coc_text.fr.html.erb
Normal file
|
|
@ -0,0 +1,51 @@
|
|||
<p>All participants of <%= community_name %> are expected to abide by our Code of Conduct, both online and during in-person events that are hosted and/or associated with <%= community_name %>.</p>
|
||||
<h2>Our Pledge</h2>
|
||||
<p>In the interest of fostering an open and welcoming environment, we as moderators of
|
||||
<% if creator_settings_form? %>
|
||||
<%= community_name %> pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
||||
<% else %>
|
||||
<a href="<%= app_url %>"><%= community_name %></a> pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
||||
<% end %>
|
||||
</p>
|
||||
<h2>Our Standards</h2>
|
||||
<p>Examples of behavior that contributes to creating a positive environment include:</p>
|
||||
<ul>
|
||||
<li>Using welcoming and inclusive language</li>
|
||||
<li>Being respectful of differing viewpoints and experiences</li>
|
||||
<li>Referring to people by their preferred pronouns and using gender-neutral pronouns when uncertain</li>
|
||||
<li>Gracefully accepting constructive criticism</li>
|
||||
<li>Focusing on what is best for the community</li>
|
||||
<li>Showing empathy towards other community members</li>
|
||||
</ul>
|
||||
<p>Examples of unacceptable behavior by participants include:</p>
|
||||
<ul>
|
||||
<li>The use of sexualized language or imagery and unwelcome sexual attention or advances</li>
|
||||
<li>Trolling, insulting/derogatory comments, and personal or political attacks</li>
|
||||
<li>Public or private harassment</li>
|
||||
<li>Publishing others' private information, such as a physical or electronic address, without explicit permission</li>
|
||||
<li>Other conduct which could reasonably be considered inappropriate in a professional setting</li>
|
||||
<li>Dismissing or attacking inclusion-oriented requests</li>
|
||||
</ul>
|
||||
<p>We pledge to prioritize marginalized people’s safety over privileged people’s comfort. We will not act on complaints regarding:</p>
|
||||
<ul>
|
||||
<li>‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’</li>
|
||||
<li>Reasonable communication of boundaries, such as 'leave me alone,' 'go away,' or 'I’m not discussing this with you.'</li>
|
||||
<li>Someone’s refusal to explain or debate social justice concepts</li>
|
||||
<li>Criticisms of racist, sexist, cissexist, or otherwise oppressive behavior or assumptions</li>
|
||||
</ul>
|
||||
<h2>Enforcement</h2>
|
||||
<p>Violations of the Code of Conduct may be reported by contacting the team via the
|
||||
<% if creator_settings_form? %>
|
||||
abuse report form or by sending an email to <%= contact_link %>. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Further details of specific enforcement policies may be posted separately.
|
||||
<% else %>
|
||||
<a href="<%= app_url("/report-abuse") %>">abuse report form</a> or by sending an email to <%= contact_link %>. All reports will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Further details of specific enforcement policies may be posted separately.
|
||||
<% end %>
|
||||
</p>
|
||||
<p>Moderators have the right and responsibility to remove comments or other contributions that are not aligned to this Code of Conduct, or to suspend temporarily or permanently any members for other behaviors that they deem inappropriate, threatening, offensive, or harmful.</p>
|
||||
<h2>Attribution</h2>
|
||||
<p>This Code of Conduct is adapted from:</p>
|
||||
<ul>
|
||||
<li><a href="http://contributor-covenant.org/version/1/4">Contributor Covenant, version 1.4</a></li>
|
||||
<li><a href="http://www.writespeakcode.com/code-of-conduct.html">Write/Speak/Code</a></li>
|
||||
<li><a href="https://geekfeminism.org/about/code-of-conduct">Geek Feminism</a></li>
|
||||
</ul>
|
||||
27
app/views/pages/_editor_frontmatter_help.fr.html.erb
Normal file
27
app/views/pages/_editor_frontmatter_help.fr.html.erb
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
<div id="editor-frontmatter-help">
|
||||
<div class="text-styles">
|
||||
<div class="crayons-notice crayons-notice--info" aria-live="polite">
|
||||
<p><strong>We have two editor versions</strong>. If you'd prefer to edit title and tags etc. as separate fields, switch to the "rich + markdown" option in <a href="<%= user_settings_path(tab: :customization) %>">Settings » UX</a>. Otherwise, continue...</p>
|
||||
</div>
|
||||
|
||||
<ul>
|
||||
<li>This editor is a markdown editor that uses <a href="https://jekyllrb.com/docs/frontmatter">Jekyll front matter</a>.</li>
|
||||
<li>Most of the time, you can write inline HTML directly into your posts.</li>
|
||||
<li>We support native Liquid tags and created some fun custom ones, too! Trying embedding a Tweet or GitHub issue in your post.</li>
|
||||
<li>Links to unpublished posts are shareable for feedback/review.</li>
|
||||
<li>When you're ready to publish, set the published variable to <strong>true.</strong></li>
|
||||
</ul>
|
||||
|
||||
<h3>Front Matter</h3>
|
||||
<p>Custom variables set for each post, located between the triple-dashed lines in your editor. Here is a list of possibilities:</p>
|
||||
<ul>
|
||||
<li><strong>title:</strong> the title of your article</li>
|
||||
<li><strong>published:</strong> boolean that determines whether or not your article is published</li>
|
||||
<li><strong>description:</strong> description area in Twitter cards and open graph cards</li>
|
||||
<li><strong>tags:</strong> max of four tags, needs to be comma-separated</li>
|
||||
<li><strong>canonical_url:</strong> link for the canonical version of the content</li>
|
||||
<li><strong>cover_image:</strong> cover image for post, accepts a URL. <br>The best size is 1000 x 420.</li>
|
||||
<li><strong>series:</strong> post series name.</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
6
app/views/pages/_editor_guide_h3.fr.html.erb
Normal file
6
app/views/pages/_editor_guide_h3.fr.html.erb
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
<h3 id="<%= id %>" class="permalink-heading">
|
||||
<strong><%= title %></strong>
|
||||
<a href="#<%= id %>" aria-label="permalink for <%= title %>">
|
||||
<%= crayons_icon_tag("small-link", aria_hidden: true) %>
|
||||
</a>
|
||||
</h3>
|
||||
148
app/views/pages/_editor_guide_text.fr.html.erb
Normal file
148
app/views/pages/_editor_guide_text.fr.html.erb
Normal file
|
|
@ -0,0 +1,148 @@
|
|||
<style>
|
||||
.permalink-heading svg {
|
||||
fill: currentColor;
|
||||
visibility: hidden;
|
||||
}
|
||||
|
||||
.permalink-heading a:focus svg,
|
||||
.permalink-heading:hover svg {
|
||||
visibility: visible;
|
||||
}
|
||||
|
||||
.container .body pre {
|
||||
margin-bottom: 1em;
|
||||
}
|
||||
</style>
|
||||
|
||||
<main class="container article" id="editor-help-guide">
|
||||
<article id="main-content" class="body">
|
||||
<h1 style="font-size: 57px; font-weight: 700; line-height: 73px;">Editor Guide 🤓</h1>
|
||||
|
||||
<% if version == "1" %>
|
||||
<%= render "pages/v1_editor_guide_preamble" %>
|
||||
<% else %>
|
||||
<p>
|
||||
<em>
|
||||
<strong>Our editor has two versions</strong>.
|
||||
If you prefer Jekyll-style "frontmatter", switch to "basic markdown" in
|
||||
<a href="<%= user_settings_path(:customization) %>">Settings → Customization</a>.
|
||||
</em>
|
||||
</p>
|
||||
|
||||
<h2 style="font-size:2.8em" id="#things-to-know" class="permalink-heading">
|
||||
<strong>Things to Know</strong>
|
||||
<a href="#things-to-know" aria-label="permalink for Things to know">
|
||||
<%= crayons_icon_tag("small-link", aria_hidden: true) %>
|
||||
</a>
|
||||
</h2>
|
||||
<ul>
|
||||
<li>Use <a href="#markdown"><strong>markdown</strong></a> to write and format <a href="<%= root_path %>"><%= community_name %></a> posts.</li>
|
||||
<li>Most of the time, you can write inline HTML directly into your posts.</li>
|
||||
<li>You can use <strong><a href="#liquidtags">Liquid tags</a></strong> to make add rich content such as tweets and videos.</li>
|
||||
<li>Links to unpublished posts are shareable for feedback/review.</li>
|
||||
<li>The best size for your <b>cover image</b> is 1000 X 420.</li>
|
||||
</ul>
|
||||
<% end %>
|
||||
|
||||
<h2 style="font-size:2.8em" id="markdown" class="permalink-heading">
|
||||
<strong>✍ Markdown Basics</strong>
|
||||
<a href="#markdown" aria-label="permalink for Markdown">
|
||||
<%= crayons_icon_tag("small-link", aria_hidden: true) %>
|
||||
</a>
|
||||
</h2>
|
||||
<p>Below are some examples of commonly used markdown syntax. If you want to dive deeper, check out
|
||||
<a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet" target="_blank" rel="noopener">this cheat sheet.</a>
|
||||
</p>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "markdown-bold-and-italic", title: "Bold & Italic" } %>
|
||||
<p><em>Italics</em>: <code>*asterisks*</code> or <code>_underscores_</code></p>
|
||||
<p><strong>Bold</strong>: <code>**double asterisks**</code> or <code>__double underscores__</code></p>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "markdown-links", title: "Links" } %>
|
||||
<p><a href="<%= app_url %>">I'm an inline link</a>: <code>[I'm an inline link](put-link-here)</code></p>
|
||||
<p><a name="anchored">Anchored links</a> (For things like a Table of Contents)</p>
|
||||
<pre>
|
||||
## Table Of Contents
|
||||
* [Chapter 1](#chapter-1)
|
||||
* [Chapter 2](#chapter-2)
|
||||
|
||||
### Chapter 1 <%= "<a name=\"chapter-1\"></a>" %>
|
||||
</pre>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "markdown-inline-images", title: "Inline Images" } %>
|
||||
<p>
|
||||
When adding GIFs to posts and comments, please note that there is a limit of 200 megapixels per frame/page.
|
||||
<img src="https://res.cloudinary.com/practicaldev/image/fetch/s--OsLaFSo9--/c_fill,f_auto,fl_progressive,h_220,q_auto,w_220/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/31047/af153cd6-9994-4a68-83f4-8ddf3e13f0bf.jpg" alt="example image, with sloan" loading="lazy" />
|
||||
</p>
|
||||
<pre></pre>
|
||||
<figure>
|
||||
<img src="https://res.cloudinary.com/practicaldev/image/fetch/s--OsLaFSo9--/c_fill,f_auto,fl_progressive,h_50,q_auto,w_50/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/31047/af153cd6-9994-4a68-83f4-8ddf3e13f0bf.jpg" alt="example image, with sloan" loading="lazy" />
|
||||
<figcaption>You can even add a caption using the HTML <code>figcaption</code> tag!</figcaption>
|
||||
</figure>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "markdown-headers", title: "Headings" } %>
|
||||
<p>Add a heading to your post with this syntax:</p>
|
||||
<pre># One '#' for a h1 heading<br>## Two '#'s for a h2 heading<br>...<br>###### Six '#'s for a h6 heading</pre>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "author-notes", title: "Author Notes/Comments" } %>
|
||||
<p>Add some hidden notes/comments to your article with this syntax:</p>
|
||||
<pre><!-- This won't show up in the content! --></pre>
|
||||
|
||||
<h2 style="font-size:2.8em" id="accessibility" class="permalink-heading">
|
||||
<strong>Accessibility</strong>
|
||||
<a href="#accessibility" aria-label="permalink for Accessibility"><%= crayons_icon_tag("small-link", aria_hidden: true) %></a>
|
||||
</h2>
|
||||
<p>People access online content in all kinds of different ways, and there are a few things you can do to make your posts more easily understood by a broad range of users. You can find out more about web accessibility at <a href="https://www.w3.org/WAI/fundamentals/accessibility-intro/">W3C's Introduction to Web Accessibility</a>, but there are two main ways you can make your posts more accessible: providing alternative descriptions of any images you use, and adding appropriate headings.</p>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "alt-text-for-images", title: "Providing alternative descriptions for images" } %>
|
||||
<p>Some users might not be able to see or easily process images that you use in your posts. Providing an alternative description for an image helps make sure that everyone can understand your post, whether they can see the image or not.</p>
|
||||
<p>When you upload an image in the editor, you will see the following text to copy and paste into your post:</p>
|
||||
<pre></pre>
|
||||
<p>Replace the "Image description" in square brackets with a description of your image - for example:</p>
|
||||
<pre></pre>
|
||||
<p>By doing this, if someone reads your post using an assistive device like a screen reader (which turns written content into spoken audio) they will hear the description you entered.</p>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "accessible-headings", title: "Providing headings" } %>
|
||||
<p>Headings provide an outline of your post to readers, including people who can't see the screen well. Many assistive technologies (like screen readers) allow users to skip directly to a particular heading, helping them find and understand the content of your post with ease.</p>
|
||||
<p><a href="#markdown-headers">Headings can be added in levels 1 - 6</a>. Avoid using a level one heading (i.e., '# Heading text'). When you create a post, your post title automatically becomes a level one heading and serves a special role on the page, much like the headline of a newspaper article. Similar to how a newspaper article only has one headline, it can be confusing if multiple level one headings exist on a page.</p>
|
||||
<p>In your post content, start with level two headings for each section (e.g. '## Section heading text'), and increase the heading level by one when you'd like to add a sub-section, for example:</p>
|
||||
<pre>## Fun facts about sloths</br></br>### Speed</br></br>Sloths move at a maximum speed of 0.27 km/h!</pre>
|
||||
|
||||
<%= render partial: "liquid_tag_section_intro", locals: { styles: "font-size:2.8em;" } %>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "supported-url-embeds-list", title: "Supported URL Embeds" } %>
|
||||
|
||||
<%= render partial: "supported_url_embeds_list" %>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "supported-nonurl-embeds-list", title: "Supported Non-URL Embeds" } %>
|
||||
|
||||
<%= render partial: "supported_nonurl_embeds_list" %>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "parsing-liquid-tags-as-code-example", title: "Parsing Liquid Tags as a Code Example" } %>
|
||||
<p>To parse Liquid tags as code, simply wrap it with a single backtick or triple backticks.</p>
|
||||
<pre>`{% mytag %}{{ site.SOMETHING }}{% endmytag %}`</pre>
|
||||
<p>One specific edge case is with using the <code>raw</code> tag. To properly escape it, use this format:
|
||||
</p>
|
||||
<pre>`{% raw %}{{site.SOMETHING }} {% ``endraw`` %}`</pre>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "common-gotchas", title: "Common Gotchas" } %>
|
||||
<p>
|
||||
Lists are written just like any other Markdown editor.
|
||||
If you're adding an image in between numbered list, though, be sure to tab the image,
|
||||
otherwise it'll restart the number of the list.
|
||||
Here's an example of what to do:
|
||||
<img
|
||||
src="https://res.cloudinary.com/practicaldev/image/fetch/s--HjVUshkb--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/8l29vxiir8k5d097o9o8.png"
|
||||
alt="example image of writing lists with images in Markdown"
|
||||
loading="lazy" />
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet" target="_blank" rel="noopener">
|
||||
<strong>Here's the Markdown cheatsheet again for reference.</strong>
|
||||
</a>
|
||||
</p>
|
||||
|
||||
<p>Happy posting! 📝</p>
|
||||
</article>
|
||||
</main>
|
||||
76
app/views/pages/_editor_liquid_help.fr.html.erb
Normal file
76
app/views/pages/_editor_liquid_help.fr.html.erb
Normal file
|
|
@ -0,0 +1,76 @@
|
|||
<div id="editor-liquid-help">
|
||||
<div class="text-styles">
|
||||
<h3>Supported URL Embeds</h3>
|
||||
|
||||
<ul class="crayons-card grid gap-2 grid-cols-2 p-4 list-disc">
|
||||
<li class="ml-4"><%= community_name %> Comment</li>
|
||||
<li class="ml-4"><%= community_name %> Link</li>
|
||||
<li class="ml-4"><%= community_name %> Link</li>
|
||||
<li class="ml-4"><%= community_name %> Listing</li>
|
||||
<li class="ml-4"><%= community_name %> Organization</li>
|
||||
<li class="ml-4"><%= community_name %> Podcast Episode</li>
|
||||
<li class="ml-4"><%= community_name %> Tag</li>
|
||||
<li class="ml-4"><%= community_name %> User Profile</li>
|
||||
<li class="ml-4">asciinema</li>
|
||||
<li class="ml-4">CodePen</li>
|
||||
<li class="ml-4">CodeSandbox</li>
|
||||
<li class="ml-4">DotNetFiddle</li>
|
||||
<li class="ml-4">GitHub Gist, Issue or Repository</li>
|
||||
<li class="ml-4">Glitch</li>
|
||||
<li class="ml-4">Instagram</li>
|
||||
<li class="ml-4">JSFiddle</li>
|
||||
<li class="ml-4">JSitor</li>
|
||||
<li class="ml-4">Loom</li>
|
||||
<li class="ml-4">Kotlin</li>
|
||||
<li class="ml-4">Medium</li>
|
||||
<li class="ml-4">Next Tech</li>
|
||||
<li class="ml-4">Reddit</li>
|
||||
<li class="ml-4">Replit</li>
|
||||
<li class="ml-4">Slideshare</li>
|
||||
<li class="ml-4">Speaker Deck</li>
|
||||
<li class="ml-4">SoundCloud</li>
|
||||
<li class="ml-4">Spotify</li>
|
||||
<li class="ml-4">StackBlitz</li>
|
||||
<li class="ml-4">Stackery</li>
|
||||
<li class="ml-4">Stack Exchange or Stack Overflow</li>
|
||||
<li class="ml-4">Twitch</li>
|
||||
<li class="ml-4">Twitter</li>
|
||||
<li class="ml-4">Twitter timeline</li>
|
||||
<li class="ml-4">Wikipedia</li>
|
||||
<li class="ml-4">Vimeo</li>
|
||||
<li class="ml-4">YouTube</li>
|
||||
</ul>
|
||||
|
||||
<hr />
|
||||
|
||||
<h3>Supported Non-URL Embeds</h3>
|
||||
|
||||
<h4>Details</h4>
|
||||
<p>You can embed a <code>details</code> HTML element by using details, spoiler, or collapsible. The <em>summary</em> will be what the dropdown title displays. The <em>content</em> will be the text hidden behind the dropdown. This is great for when you want to hide text (i.e. answers to questions) behind a user action/intent (i.e. a click).</p>
|
||||
<p><code>{% details summary %} content {% enddetails %}</code></p>
|
||||
<p><code>{% spoiler summary %} content {% endspoiler %}</code></p>
|
||||
<p><code>{% collapsible summary %} content {% endcollapsible %}</code></p>
|
||||
|
||||
<h4>KaTex</h4>
|
||||
<p>Place your mathematical expression within a KaTeX liquid block, as follows:</p>
|
||||
<pre>{% katex %}<br> c = \pm\sqrt{a^2 + b^2}<br>{% endkatex %}<br></pre>
|
||||
<p>To render KaTeX inline add the "inline" option:</p>
|
||||
<pre>{% katex inline %}<br> c = \pm\sqrt{a^2 + b^2}<br>{% endkatex %}<br></pre>
|
||||
|
||||
<h4>RunKit</h4>
|
||||
<p>Put executable code within a runkit liquid block, as follows:</p>
|
||||
<pre>{% runkit<br>// hidden setup JavaScript code goes in this preamble area<br>const hiddenVar = 42<br>%}<br>// visible, reader-editable JavaScript code goes here<br>console.log(hiddenVar)<br>{% endrunkit %}<br></pre>
|
||||
|
||||
<% if @user_approved_liquid_tags.include? UserSubscriptionTag %>
|
||||
<h4><%= community_name %> User Subscriptions</h4>
|
||||
<p class="fs-s fw-bold">This embed can only be created within posts by Admins.</p>
|
||||
<p>You can add call-to-action text that will show above the subscribe button:</p>
|
||||
<code>{% user_subscription If you'd like to receive future updates, subscribe below! %}</code>
|
||||
<p class="fs-s">
|
||||
If a reader is signed out, the button will prompt them to sign in first
|
||||
to subscribe. If the reader is signed in, the button will prompt them
|
||||
to subscribe.
|
||||
</p>
|
||||
<% end %>
|
||||
</div>
|
||||
</div>
|
||||
57
app/views/pages/_editor_markdown_help.fr.html.erb
Normal file
57
app/views/pages/_editor_markdown_help.fr.html.erb
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
<div id="editor-markdown-help">
|
||||
<div class="text-styles">
|
||||
<p>Below are some examples of commonly used markdown syntax. If you want to dive deeper, check out
|
||||
<a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet" target="_blank" rel="noopener">this cheat sheet.</a>
|
||||
</p>
|
||||
|
||||
<h3>Bold & Italic</h3>
|
||||
<p><em>Italics</em>: <code>*asterisks* or _underscores_</code></p>
|
||||
<p><strong>Bold</strong>: <code>**double asterisks** or __double underscores__</code></p>
|
||||
|
||||
<h3>Links</h3>
|
||||
<p><a href="<%= app_url %>">I'm an inline link</a>: <code>[I'm an inline link](put-link-here)</code></p>
|
||||
<p><a name="anchored">Anchored links</a> (For things like a Table of Contents)</p>
|
||||
<pre>
|
||||
## Table Of Contents
|
||||
* [Chapter 1](#chapter-1)
|
||||
* [Chapter 2](#chapter-2)
|
||||
|
||||
### Chapter 1 <%= "<a name=\"chapter-1\"></a>" %>
|
||||
</pre>
|
||||
|
||||
<h3>Inline Images</h3>
|
||||
<p>
|
||||
When adding GIFs to posts and comments, please note that there is a limit of 200 megapixels per frame/page.
|
||||
<img src="https://res.cloudinary.com/practicaldev/image/fetch/s--OsLaFSo9--/c_fill,f_auto,fl_progressive,h_220,q_auto,w_220/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/31047/af153cd6-9994-4a68-83f4-8ddf3e13f0bf.jpg" alt="example image, with sloan" loading="lazy" />
|
||||
</p>
|
||||
<pre></pre>
|
||||
<figcaption> You can even add a caption using the HTML <code>figcaption</code> tag!</figcaption>
|
||||
|
||||
<h3>Headers</h3>
|
||||
<p>Add a header to your post with this syntax:</p>
|
||||
<pre># One '#' for a h1 header<br>## Two '#'s for a h2 header<br>...<br>###### Six '#'s for a h6 header</pre>
|
||||
<h1>One '#' for a h1 header</h1>
|
||||
<h2>Two '#'s for a h2 header</h2>
|
||||
<h3>Three '#'s for a h3 header</h3>
|
||||
<h4>Four '#'s for a h4 header</h4>
|
||||
<h5>Five '#'s for a h5 header</h5>
|
||||
<h6>Six '#'s for a h6 header</h6>
|
||||
|
||||
<h3>Author Notes/Comments</h3>
|
||||
<p>Add some hidden notes/comments to your article with this syntax:</p>
|
||||
<pre><!-- This won't show up in the content! --></pre>
|
||||
|
||||
<h3>Common Gotchas</h3>
|
||||
<p>
|
||||
Lists are written just like any other Markdown editor.
|
||||
If you're adding an image in between numbered list, though, be sure to tab the image,
|
||||
otherwise it'll restart the number of the list.
|
||||
Here's an example of what to do:
|
||||
<img src="https://res.cloudinary.com/practicaldev/image/fetch/s--HjVUshkb--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/8l29vxiir8k5d097o9o8.png"
|
||||
alt="example image of writing lists with images in Markdown" loading="lazy" />
|
||||
</p>
|
||||
<p>
|
||||
Here's the <a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet" target="_blank" rel="noopener">Markdown cheatsheet</a> again for reference.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
8
app/views/pages/_liquid_tag_section_intro.fr.html.erb
Normal file
8
app/views/pages/_liquid_tag_section_intro.fr.html.erb
Normal file
|
|
@ -0,0 +1,8 @@
|
|||
<h2 style="<%= styles %>" id="liquidtags" class="permalink-heading">
|
||||
<strong>🌊 Liquid Tags</strong>
|
||||
<a href="#liquidtags" aria-label="permalink for Liquid Tags"><%= crayons_icon_tag("small-link", aria_hidden: true) %></a>
|
||||
</h2>
|
||||
<p>
|
||||
We support native <a href="https://shopify.github.io/liquid" target="_blank" rel="noopener">Liquid tags</a> in our editor, but have created our own custom tags as well. A list of supported custom embeds appears below. To create a custom embed, use the complete URL:<br />
|
||||
<code>{% embed https://... %}</code>
|
||||
</p>
|
||||
9
app/views/pages/_placeholder.fr.html.erb
Normal file
9
app/views/pages/_placeholder.fr.html.erb
Normal file
|
|
@ -0,0 +1,9 @@
|
|||
<% title "#{title} #{community_name}" %>
|
||||
|
||||
<div class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0"><%= title %></h1>
|
||||
|
||||
<p>The production <%= title %> page is a page generated at <a href="<%= admin_pages_path %>"><%= admin_pages_path %></a>! This one is just a placeholder.</p>
|
||||
</div>
|
||||
</div>
|
||||
144
app/views/pages/_privacy_text.fr.html.erb
Normal file
144
app/views/pages/_privacy_text.fr.html.erb
Normal file
|
|
@ -0,0 +1,144 @@
|
|||
<p>Effective Dec 20, 2018</p>
|
||||
<p>This policy covers <%= community_name %>.</p>
|
||||
<h3> What information <%= community_name %> collects and Why </h3>
|
||||
<p>In order to give you the best possible experience using <%= community_name %>, we collect information from your interactions with our network. We use common internet technologies, such as cookies and web server logs. We collect this basic information from everybody, whether they have an account or not.</p>
|
||||
<p>The information we collect about all visitors to our website includes:</p>
|
||||
<ul>
|
||||
<li>The visitor’s browser type</li>
|
||||
<li>Referring site</li>
|
||||
<li>The date and time of each visitor request</li>
|
||||
<li>We also collect potentially personally-identifying information like Internet Protocol (IP) addresses.</li>
|
||||
</ul>
|
||||
<p>We use this information to:</p>
|
||||
<ul>
|
||||
<li>Provide, test, improve, promote and personalize <%= community_name %> Services</li>
|
||||
<li>Fight spam and other forms of abuse</li>
|
||||
<li>Generate aggregate, non-identifying information about how people use <%= community_name %> Services</li>
|
||||
</ul>
|
||||
<p>In order for you to create an account on <%= community_name %> and use our Services, we need to collect and process certain information. Depending on your use of the Services, that may include:</p>
|
||||
<ul>
|
||||
<li>Communications you send to us (for example, when you ask for support, send us questions or comments, or report a problem);</li>
|
||||
<li>Information that you submit on or to <%= community_name %> in the form of reactions, comments, or messages to other users;</li>
|
||||
<li>The email address associated with your Twitter account, if you choose to sign up using your Twitter credentials. <%= community_name %> will also request permission to access additional information (these permissions are governed by Twitter’s privacy policies and can be managed through your Twitter privacy settings). We never post anything to your Twitter without your permission.</li>
|
||||
<li>The email address associated with your GitHub account, if you choose to sign up using your Github credentials. <%= community_name %> will also request permission to access additional information (these permissions are governed by GitHub’s privacy policies and can be managed through your GitHub privacy settings). We never post anything to your GitHub without your permission.</li>
|
||||
<li>You also have the option to give us more information if you want to, and this may include “User Personal Information.”</li>
|
||||
</ul>
|
||||
<h3>Information Disclosure</h3>
|
||||
<p>We do not share, sell, rent, or trade User Personal Information with third parties for commercial purposes.
|
||||
<br>
|
||||
<br>
|
||||
We do share certain aggregated, non-personally identifying information with others about how our users, collectively, use <%= community_name %>. For example, we may share information pertaining to the popularity of different programming languages for advertising partners.
|
||||
<br>
|
||||
<br>
|
||||
We do host first-party advertising on <%= community_name %>. We do not run any code from advertisers and all ad images are hosted on managed <%= community_name %> servers. For more details, see our section on Advertising Details.
|
||||
<br>
|
||||
<br>
|
||||
We may use User Personal Information with your permission, so we can perform services you have authorized.
|
||||
<br>
|
||||
<br>
|
||||
We may share User Personal Information with a limited number of third party vendors who process it on our behalf to provide or improve our service, and who have agreed to privacy restrictions similar to our own Privacy Statement. Our third party vendors are listed below.
|
||||
</p>
|
||||
<h3>Advertising Details</h3>
|
||||
<p>We target advertisements based solely upon:</p>
|
||||
<ul>
|
||||
<li>Details of the page where the advertisement is shown, including:
|
||||
<ul>
|
||||
<li>The name and keywords associated with the page or article being viewed
|
||||
<ul>
|
||||
<li>We allow advertisers to target ads to a list of keywords advertising.</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
</ul>
|
||||
<p>We may place ads in:</p>
|
||||
<ul>
|
||||
<li>Sidebars</li>
|
||||
<li>Below articles</li>
|
||||
<li>On search result pages</li>
|
||||
<li>On tag pages</li>
|
||||
</ul>
|
||||
<p>All registered members have the ability to disable advertisements — where reasonable — through their Settings page. For instance, it’s not feasible to disable certain advertisements in the form of recognition posts, site-wide contests, dedicated sponsorship page, etc.</p>
|
||||
<h3>Third Party Vendors</h3>
|
||||
<p>
|
||||
<strong>We may share your account information with third parties in some circumstances, including:</strong> (1) with your consent; (2) to a service provider or partner who meets our data protection standards; (3) for survey or research purposes, after aggregation, anonymization, or pseudonymization; (4) when we have a good faith belief it is required by law, such as pursuant to a subpoena or other legal process; (5) when we have a good faith belief that doing so will help prevent imminent harm to someone.
|
||||
</p>
|
||||
<p><strong>Data Storage</strong>
|
||||
<br>
|
||||
<%= community_name %> uses third-party vendors and hosting partners for hardware, software, networking, storage, and related technology we need to run <%= community_name %>. By using <%= community_name %> Services, you authorize <%= community_name %> to transfer, store, and use your information in the United States and any other country where we operate. All service providers and third-party vendors are required to meet our data protection standards.
|
||||
</p>
|
||||
<p><strong>Site monitoring</strong>
|
||||
<br>
|
||||
<%= community_name %> uses a variety of third-party services to diagnose errors and improve the performance of our site. We aim to minimize the amount of personal information shared, but the information may include your IP address or other identifying information. All service providers and third-party vendors are required to meet our data protection standards.
|
||||
</p>
|
||||
<p><strong>Payment processing</strong>
|
||||
<br>
|
||||
<%= community_name %> does not process payments directly — we rely on third-party services such as Stripe, Shopify, and Paypal to receive payments and store any payment information.
|
||||
</p>
|
||||
<p><strong>Third-Party Embeds</strong>
|
||||
<br>
|
||||
Some of the content that you see displayed on <%= community_name %> is not hosted by <%= community_name %>. These
|
||||
“embeds” are hosted by a third-party and embedded in <%= community_name %>. For example: YouTube videos, Codepens,
|
||||
Twitter tweets, or GitHub code that appear within a <%= community_name %> post. These files send data to the hosted
|
||||
site just as if you were visiting that site directly (for example, when you load a <%= community_name %> post page with
|
||||
a YouTube video embedded in it, YouTube receives data about your activity). <%= community_name %> does not control what
|
||||
data third parties collect in cases like this, or what they will do with it. Third-party embeds on <%= community_name %>
|
||||
are not covered by this privacy policy; they are covered by the privacy policy of the third-party service. Be mindful
|
||||
when interacting with these services.
|
||||
</p>
|
||||
<p><strong>Tracking & Cookies</strong>
|
||||
<br>
|
||||
We use browser cookies and similar technologies to recognize you when you return to our Services. Third-party vendors may also use cookies for various reasons.
|
||||
<br>
|
||||
<br>
|
||||
<%= community_name %> uses a specific cookie in order to facilitate the use of Google Universal Analytics for users
|
||||
logged-in to the Applications or the Platforms (“Logged-In User). If you are a Logged-In User, <%= community_name %>
|
||||
may use your <%= community_name %> user ID in combination with Google Universal Analytics and Google Analytics to track
|
||||
and analyze the pages of the Services you visit. We do this only to better understand how you use the Website and the
|
||||
other Services, with a view to offering improvements for all <%= community_name %> users; and to tailor our business
|
||||
and marketing activities accordingly, both generally and specifically to you. Google Analytics cookies do not provide
|
||||
<%= community_name %> with any Personal Information.You can prevent Google Analytics from recognizing you on return
|
||||
visits to this site by disabling cookies on your browser.
|
||||
<br>
|
||||
<br>
|
||||
You may opt-out of this feature by installing the Google Analytics Opt-out Browser Add-on, by setting your web browser to refuse cookies, or by setting your browser to alert you when cookies are being sent. If you do so, note that some parts of the Site may not function properly.
|
||||
</p>
|
||||
<p><strong>Data Security</strong>
|
||||
<br>
|
||||
We use encryption (HTTPS/TLS) to protect data transmitted to and from our site. However, no data transmission over the Internet is 100% secure, so we can’t guarantee security. You use the Service at your own risk, and you’re responsible for taking reasonable measures to secure your account.
|
||||
</p>
|
||||
<p><strong>Administrative Emails from <%= community_name %></strong>
|
||||
<br>
|
||||
Sometimes we’ll send you emails about your account, service changes or new policies. You can’t opt out of this type of “transactional” email (unless you delete your account).
|
||||
<br>
|
||||
<br>
|
||||
When you interact with a transactional email sent from <%= community_name %> (such as opening an email or clicking on a particular link in an email), we may receive information about that interaction.
|
||||
</p>
|
||||
<p><strong>Non-administrative Emails from <%= community_name %></strong>
|
||||
<br>
|
||||
Upon creating a <%= community_name %> account, you will be opted into the <%= community_name %> Newsletter and other non-administrative email. Your email address and user profile information may be stored by a third-party email provider such as MailChimp or Sendgrid. You can opt out of non-administrative emails such as digests, newsletters, and activity notifications through your account’s “Settings” page and at the link of the footer in any non-administrative email you receive from us.
|
||||
<br>
|
||||
<br>
|
||||
When you interact with a non-administrative email sent from <%= community_name %> (such as opening an email or clicking on a particular link in an email), we may receive information about that interaction.
|
||||
</p>
|
||||
<p><strong>Deleting Your Personal Information</strong>
|
||||
<br>
|
||||
You may request deletion of your personal information and account by emailing <%= contact_link %>.
|
||||
<br>
|
||||
<br>
|
||||
To protect information from accidental or malicious destruction, we may maintain residual copies for a brief time period. But, if you delete your account, your information and content will be unrecoverable after that time.
|
||||
</p>
|
||||
<p><strong>Data Portability</strong>
|
||||
<br>
|
||||
If you would like to request a copy of your user data, please email <%= contact_link %>.</p>
|
||||
<p><strong>Business Transfers</strong>
|
||||
<br>
|
||||
If we are involved in a merger, acquisition, bankruptcy, reorganization or sale of assets such that your information would be transferred or become subject to a different privacy policy, we’ll notify you in advance of any such change.
|
||||
</p>
|
||||
<p><strong>Changes to this Policy</strong>
|
||||
<br>
|
||||
We reserve the right to revise this Privacy Policy at any time. If we change this Privacy Policy in the future, we will post the revised Privacy Policy and update the “Effective Date,” above, to reflect the date of the changes.
|
||||
</p>
|
||||
<p><strong>Questions</strong>
|
||||
<br>
|
||||
We welcome feedback about this policy at <%= contact_link %>.</p>
|
||||
31
app/views/pages/_supported_nonurl_embeds_list.fr.html.erb
Normal file
31
app/views/pages/_supported_nonurl_embeds_list.fr.html.erb
Normal file
|
|
@ -0,0 +1,31 @@
|
|||
<% @user_approved_liquid_tags = Users::ApprovedLiquidTags.call(@user) %>
|
||||
|
||||
<h4>Details</h4>
|
||||
<p>You can embed a <code>details</code> HTML element by using details, spoiler, or collapsible. The <em>summary</em> will be what the dropdown title displays. The <em>content</em> will be the text hidden behind the dropdown. This is great for when you want to hide text (i.e. answers to questions) behind a user action/intent (i.e. a click).</p>
|
||||
<pre>
|
||||
<code>{% details summary %} content {% enddetails %}</code>
|
||||
<code>{% spoiler summary %} content {% endspoiler %}</code>
|
||||
<code>{% collapsible summary %} content {% endcollapsible %}</code>
|
||||
</pre>
|
||||
|
||||
<h4>KaTex</h4>
|
||||
<p>Place your mathematical expression within a KaTeX liquid block, as follows:</p>
|
||||
<pre>{% katex %}<br> c = \pm\sqrt{a^2 + b^2}<br>{% endkatex %}<br></pre>
|
||||
<p>To render KaTeX inline add the "inline" option:</p>
|
||||
<pre>{% katex inline %}<br> c = \pm\sqrt{a^2 + b^2}<br>{% endkatex %}<br></pre>
|
||||
|
||||
<h4>RunKit</h4>
|
||||
<p>Put executable code within a runkit liquid block, as follows:</p>
|
||||
<pre>{% runkit<br>// hidden setup JavaScript code goes in this preamble area<br>const hiddenVar = 42<br>%}<br>// visible, reader-editable JavaScript code goes here<br>console.log(hiddenVar)<br>{% endrunkit %}<br></pre>
|
||||
|
||||
<% if @user_approved_liquid_tags.include? UserSubscriptionTag %>
|
||||
<h4><%= community_name %> User Subscriptions</h4>
|
||||
<p class="fs-s fw-bold">This embed can only be created within posts by Admins.</p>
|
||||
<p>You can add call-to-action text that will show above the subscribe button:</p>
|
||||
<code>{% user_subscription If you'd like to receive future updates, subscribe below! %}</code>
|
||||
<p class="fs-s">
|
||||
If a reader is signed out, the button will prompt them to sign in first
|
||||
to subscribe. If the reader is signed in, the button will prompt them
|
||||
to subscribe.
|
||||
</p>
|
||||
<% end %>
|
||||
38
app/views/pages/_supported_url_embeds_list.fr.html.erb
Normal file
38
app/views/pages/_supported_url_embeds_list.fr.html.erb
Normal file
|
|
@ -0,0 +1,38 @@
|
|||
<ul class="crayons-card grid gap-2 grid-cols-1 s:grid-cols-2 p-4 list-disc">
|
||||
<li class="ml-4"><%= community_name %> Comment</li>
|
||||
<li class="ml-4"><%= community_name %> Link</li>
|
||||
<li class="ml-4"><%= community_name %> Link</li>
|
||||
<li class="ml-4"><%= community_name %> Listing</li>
|
||||
<li class="ml-4"><%= community_name %> Organization</li>
|
||||
<li class="ml-4"><%= community_name %> Podcast Episode</li>
|
||||
<li class="ml-4"><%= community_name %> Tag</li>
|
||||
<li class="ml-4"><%= community_name %> User Profile</li>
|
||||
<li class="ml-4">asciinema</li>
|
||||
<li class="ml-4">CodePen</li>
|
||||
<li class="ml-4">CodeSandbox</li>
|
||||
<li class="ml-4">DotNetFiddle</li>
|
||||
<li class="ml-4">GitHub Gist, Issue or Repository</li>
|
||||
<li class="ml-4">Glitch</li>
|
||||
<li class="ml-4">Instagram</li>
|
||||
<li class="ml-4">JSFiddle</li>
|
||||
<li class="ml-4">JSitor</li>
|
||||
<li class="ml-4">Loom</li>
|
||||
<li class="ml-4">Kotlin</li>
|
||||
<li class="ml-4">Medium</li>
|
||||
<li class="ml-4">Next Tech</li>
|
||||
<li class="ml-4">Reddit</li>
|
||||
<li class="ml-4">Replit</li>
|
||||
<li class="ml-4">Slideshare</li>
|
||||
<li class="ml-4">Speaker Deck</li>
|
||||
<li class="ml-4">SoundCloud</li>
|
||||
<li class="ml-4">Spotify</li>
|
||||
<li class="ml-4">StackBlitz</li>
|
||||
<li class="ml-4">Stackery</li>
|
||||
<li class="ml-4">Stack Exchange or Stack Overflow</li>
|
||||
<li class="ml-4">Twitch</li>
|
||||
<li class="ml-4">Twitter</li>
|
||||
<li class="ml-4">Twitter timeline</li>
|
||||
<li class="ml-4">Wikipedia</li>
|
||||
<li class="ml-4">Vimeo</li>
|
||||
<li class="ml-4">YouTube</li>
|
||||
</ul>
|
||||
140
app/views/pages/_terms_text.fr.html.erb
Normal file
140
app/views/pages/_terms_text.fr.html.erb
Normal file
|
|
@ -0,0 +1,140 @@
|
|||
<h3 id="terms-text">
|
||||
1. Terms
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
By accessing this web site, you are agreeing to be bound by these
|
||||
web site Terms and Conditions of Use, our
|
||||
<a href="<%= app_url("/privacy") %>">Privacy Policy</a>, all applicable laws and regulations,
|
||||
and agree that you are responsible for compliance with any applicable local
|
||||
laws. If you do not agree with any of these terms, you are prohibited from
|
||||
using or accessing this site. The materials contained in this web site are
|
||||
protected by applicable copyright and trade mark law.
|
||||
</p>
|
||||
|
||||
<h3 id="use-licence">
|
||||
2. Use License
|
||||
</h3>
|
||||
|
||||
<ol type="a">
|
||||
<li>
|
||||
Permission is granted to temporarily download one copy of the materials
|
||||
(information or software) on <%= community_name %>'s web site for personal,
|
||||
non-commercial transitory viewing only. This is the grant of a license,
|
||||
not a transfer of title, and under this license you may not:
|
||||
|
||||
<ol type="i">
|
||||
<li>modify or copy the materials;</li>
|
||||
<li>use the materials for any commercial purpose, or for any public display (commercial or non-commercial);</li>
|
||||
<li>attempt to decompile or reverse engineer any software contained on <%= community_name %>'s web site;</li>
|
||||
<li>remove any copyright or other proprietary notations from the materials; or</li>
|
||||
<li>transfer the materials to another person or "mirror" the materials on any other server.</li>
|
||||
</ol>
|
||||
</li>
|
||||
<li>
|
||||
This license shall automatically terminate if you violate any of these restrictions and may be terminated by <%= community_name %> at any time. Upon terminating your viewing of these materials or upon the termination of this license, you must destroy any downloaded materials in your possession whether in electronic or printed format.
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<h3 id="disclaimer">
|
||||
3. Disclaimer
|
||||
</h3>
|
||||
|
||||
<ol type="a">
|
||||
<li>
|
||||
The materials on <%= community_name %>'s web site are provided "as is". <%= community_name %> makes no warranties, expressed or implied, and hereby disclaims and negates all other warranties, including without limitation, implied warranties or conditions of merchantability, fitness for a particular purpose, or non-infringement of intellectual property or other violation of rights.
|
||||
Further, <%= community_name %> does not warrant or make any representations concerning the accuracy, likely results, or reliability of the use of the materials on its Internet web site or otherwise relating to such materials or on any sites linked to this site.
|
||||
</li>
|
||||
</ol>
|
||||
|
||||
<h3 id="limitations">
|
||||
4. Limitations
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
In no event shall <%= community_name %> or its suppliers be liable for any damages (including, without limitation, damages for loss of data or profit, or due to business interruption,) arising out of the use or inability to use the materials on <%= community_name %>'s Internet site,
|
||||
even if <%= community_name %> or an authorized representative has been notified orally or in writing of the possibility of such damage. Because some jurisdictions do not allow limitations on implied warranties, or limitations of liability for consequential or incidental damages, these limitations may not apply to you.
|
||||
</p>
|
||||
|
||||
<h3 id="revisions-and-errata">
|
||||
5. Revisions and Errata
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
The materials appearing on <%= community_name %>'s web site could include technical, typographical, or photographic errors. <%= community_name %> does not warrant that any of the materials on its web site are accurate, complete, or current.
|
||||
<%= community_name %> may make changes to the materials contained on its web site at any time without notice. <%= community_name %> does not, however, make any commitment to update the materials.
|
||||
</p>
|
||||
|
||||
<h3 id="links">
|
||||
6. Links
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
<%= community_name %> has not reviewed all of the sites linked to its Internet web site and is not responsible for the contents of any such linked site. The inclusion of any link does not imply endorsement by <%= community_name %> of the site. Use of any such linked web site is at the user's own risk.
|
||||
</p>
|
||||
|
||||
<h3 id="copyright-takedown">
|
||||
7. Copyright / Takedown
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
Users agree and certify that they have rights to share all content that they post on <%= community_name %> — including, but not limited to, information posted in articles, discussions, and comments. This rule applies to prose, code snippets, collections of links, etc. Regardless of citation, users may not post copy and pasted content that does not belong to them. Users assume all risk for the content they post, including someone else's reliance on its accuracy, claims relating to intellectual property, or other legal rights. If you believe that a user has plagiarized content, misrepresented their identity, misappropriated work, or otherwise run afoul of DMCA regulations, please email
|
||||
<%= contact_link %>. <%= community_name %> may remove any content users post for any reason.
|
||||
</p>
|
||||
|
||||
<h3 id="site-terms-of-use-modifications">
|
||||
8. Site Terms of Use Modifications
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
<%= community_name %> may revise these terms of use for its web site at any time without notice. By using this web site you are agreeing to be bound by the then current version of these Terms and Conditions of Use.
|
||||
</p>
|
||||
|
||||
<h3 id="dev-trademarks-and-logo-policy">
|
||||
9. <%= community_name %> Trademarks and Logos Policy
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
All uses of the <%= community_name %> logo, <%= community_name %> badges, brand slogans, iconography, and the like, may only be used with express permission from <%= community_name %>.
|
||||
<%= community_name %> reserves all rights, even if certain assets are included in <%= community_name %> open source projects. Please contact <%= contact_link %> with any questions or to request permission.
|
||||
</p>
|
||||
|
||||
<h3 id="reserved-names">
|
||||
10. Reserved Names
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
<%= community_name %> has the right to maintain a list of reserved names which will not be made publicly available. These reserved names may be set aside for purposes of proactive trademark protection, avoiding user confusion, security measures, or any other reason (or no reason).
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Additionally, <%= community_name %> reserves the right to change any already-claimed name at its sole discretion. In such cases, <%= community_name %> will make reasonable effort to find a suitable alternative and assist with any transition-related concerns.
|
||||
</p>
|
||||
|
||||
<h3 id="content-policy">
|
||||
11. Content Policy
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
The following policy applies to comments, articles, and all other works shared on the <%= community_name %> platform:
|
||||
<ul><li>Users must make a good-faith effort to share content that is on-topic, of high-quality, and is not designed primarily for the purposes of promotion or creating backlinks.
|
||||
</li>
|
||||
<li>Posts must contain substantial content — they may not merely reference an external link that contains the full post.</li>
|
||||
<li>If a post contains affiliate links, that fact must be clearly disclosed. For instance, with language such as: “This post includes affiliate links; I may receive compensation if you purchase products or services from the different links provided in this article.”</li></ul>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<%= community_name %> reserves the right to remove any content that it deems to be in violation of this policy at its sole discretion. Additionally, <%= community_name %> reserves the right to restrict any user’s ability to participate on the platform at its sole discretion.
|
||||
</p>
|
||||
|
||||
<h3 id="governing-law">
|
||||
12. Governing Law
|
||||
</h3>
|
||||
|
||||
<p>
|
||||
Any claim relating to <%= community_name %>'s web site shall be governed by the laws of the State of New York without regard to its conflict of law provisions.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
General Terms and Conditions applicable to Use of a Web Site.
|
||||
</p>
|
||||
34
app/views/pages/_v1_editor_guide_preamble.fr.html.erb
Normal file
34
app/views/pages/_v1_editor_guide_preamble.fr.html.erb
Normal file
|
|
@ -0,0 +1,34 @@
|
|||
<style>
|
||||
.permalink-heading svg {
|
||||
fill: currentColor;
|
||||
visibility: hidden;
|
||||
}
|
||||
|
||||
.permalink-heading a:focus svg,
|
||||
.permalink-heading:hover svg {
|
||||
visibility: visible;
|
||||
}
|
||||
|
||||
</style>
|
||||
<h1 id="things-to-know" class="permalink-heading"><strong>Things to Know</strong><a href="#things-to-know" aria-label="permalink for Things to know"><%= crayons_icon_tag("small-link", aria_hidden: true) %></a></h1>
|
||||
<ul>
|
||||
<li>We use a markdown editor that uses <a href="https://jekyllrb.com/docs/frontmatter">Jekyll front matter</a>.</li>
|
||||
<li>Most of the time, you can write inline HTML directly into your posts.</li>
|
||||
<li>We support native Liquid tags and created some fun custom ones, too! Trying embedding a Tweet or GitHub issue in your post, using the complete URL: <code>{% embed https://... %}</code>.</li>
|
||||
<li>Links to unpublished posts are shareable for feedback/review.</li>
|
||||
<li>When you're ready to publish, set the published variable to <strong>true.</strong></li>
|
||||
</ul>
|
||||
|
||||
<p><em><b>We have two editor versions</b>. If you'd prefer to edit title and tags etc. as separate fields, switch to the "rich + markdown" option in <a href="<%= user_settings_path(:customization) %>">Settings → Customization</a>. Otherwise, continue:</em></p>
|
||||
|
||||
<h2 id="front-matter" class="permalink-heading"><u><strong>Front Matter</strong></u><a href="#front-matter" aria-label="permalink for Front matter"><%= crayons_icon_tag("small-link", aria_hidden: true) %></a></h2>
|
||||
<p>Custom variables set for each post, located between the triple-dashed lines in your editor Here is a list of possibilities:</p>
|
||||
<ul>
|
||||
<li><strong>title:</strong> the title of your article</li>
|
||||
<li><strong>published:</strong> boolean that determines whether or not your article is published</li>
|
||||
<li><strong>description:</strong> description area in Twitter cards and open graph cards</li>
|
||||
<li><strong>tags:</strong> max of four tags, needs to be comma-separated</li>
|
||||
<li><strong>canonical_url:</strong> link for the canonical version of the content</li>
|
||||
<li><strong>cover_image:</strong> cover image for post, accepts a URL. <br>The best size is 1000 x 420.</li>
|
||||
<li><strong>series:</strong> post series name.</li>
|
||||
</ul>
|
||||
1
app/views/pages/about.fr.html.erb
Normal file
1
app/views/pages/about.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "About" } %>
|
||||
1
app/views/pages/about_listings.fr.html.erb
Normal file
1
app/views/pages/about_listings.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "About #{community_name} Listings" } %>
|
||||
1
app/views/pages/bounty.fr.html.erb
Normal file
1
app/views/pages/bounty.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "Reporting Vulnerabilities" } %>
|
||||
22
app/views/pages/code_of_conduct.fr.html.erb
Normal file
22
app/views/pages/code_of_conduct.fr.html.erb
Normal file
|
|
@ -0,0 +1,22 @@
|
|||
<% title "#{community_name} Code of Conduct" %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url(code_of_conduct_path) %>" />
|
||||
<meta name="description" content="<%= community_name %> Code of Conduct">
|
||||
<%= meta_keywords_default %>
|
||||
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="<%= app_url(code_of_conduct_path) %>" />
|
||||
<meta property="og:title" content="<%= community_name %> Code of Conduct" />
|
||||
<meta property="og:site_name" content="<%= community_name %>" />
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@<%= Settings::General.social_media_handles["twitter"] %>">
|
||||
<meta name="twitter:title" content="<%= community_name %> Code of Conduct">
|
||||
<% end %>
|
||||
|
||||
<main id="main-content" class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0">Code of Conduct</h1>
|
||||
<%= Page.render_safe_html_for(slug: Page::CODE_OF_CONDUCT_SLUG) { render "pages/coc_text" } %>
|
||||
</div>
|
||||
</main>
|
||||
1
app/views/pages/community_moderation.fr.html.erb
Normal file
1
app/views/pages/community_moderation.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "Community Moderation Guide" } %>
|
||||
45
app/views/pages/contact.fr.html.erb
Normal file
45
app/views/pages/contact.fr.html.erb
Normal file
|
|
@ -0,0 +1,45 @@
|
|||
<% title "Contact #{community_name}" %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url("/contact") %>" />
|
||||
<meta name="description" content="Contact #{community_name}">
|
||||
<%= meta_keywords_default %>
|
||||
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="<%= app_url("/contact") %>" />
|
||||
<meta property="og:title" content="Contact #{community_name}" />
|
||||
<meta property="og:image" content="<%= Settings::General.main_social_image %>" />
|
||||
<meta property="og:description" content="<%= community_name %> is great!" />
|
||||
<meta property="og:site_name" content="<%= community_name %>" />
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@<%= Settings::General.social_media_handles["twitter"] %>">
|
||||
<meta name="twitter:title" content="Contact #{community_name}">
|
||||
<meta name="twitter:description" content="<%= community_name %> is great!">
|
||||
<meta name="twitter:image:src" content="<%= Settings::General.main_social_image %>">
|
||||
<% end %>
|
||||
|
||||
<div class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0">Contacts</h1>
|
||||
|
||||
<p>
|
||||
<%= community_name %> would love to hear from you!
|
||||
</p>
|
||||
<p>
|
||||
Email: <%= contact_link %> 😁
|
||||
</p>
|
||||
<p>
|
||||
Twitter: <a href="http://twitter.com/<%= Settings::General.social_media_handles["twitter"] %>">@<%= Settings::General.social_media_handles["twitter"] %></a> 👻
|
||||
</p>
|
||||
<p>
|
||||
Report a vulnerability: <a href="https://dev.to/security">dev.to/security</a> 🐛
|
||||
</p>
|
||||
<p>
|
||||
To report a bug, please create <a href="https://github.com/forem/forem/issues/new/choose">a bug report</a> in our open source repository.
|
||||
</p>
|
||||
<p>
|
||||
To request a feature, please <a href="https://github.com/forem/forem/discussions">start a new GitHub Discussion</a> in the Forem repo!
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
10
app/views/pages/editor_guide.fr.html.erb
Normal file
10
app/views/pages/editor_guide.fr.html.erb
Normal file
|
|
@ -0,0 +1,10 @@
|
|||
<% title "Editor Guide" %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url("/p/editor_guide") %>" />
|
||||
<meta name="description" content="<%= community_name %> | editor guideline">
|
||||
<%= meta_keywords_default %>
|
||||
<% end %>
|
||||
|
||||
<div class="blank-space"></div>
|
||||
<%= render "editor_guide_text", version: "1" %>
|
||||
1
app/views/pages/faq.fr.html.erb
Normal file
1
app/views/pages/faq.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "FAQ" } %>
|
||||
8
app/views/pages/forbidden.fr.html.erb
Normal file
8
app/views/pages/forbidden.fr.html.erb
Normal file
|
|
@ -0,0 +1,8 @@
|
|||
<h2>Forbidden</h2>
|
||||
|
||||
<p>
|
||||
Your account has been suspended and has limited access.
|
||||
Your ability to post and comment may be limited.
|
||||
</p>
|
||||
|
||||
<p>For more information, you may send a message to <%= contact_link %>.</p>
|
||||
62
app/views/pages/markdown_basics.fr.html.erb
Normal file
62
app/views/pages/markdown_basics.fr.html.erb
Normal file
|
|
@ -0,0 +1,62 @@
|
|||
<% title "Markdown Basics" %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url("/p/markdown_basics") %>" />
|
||||
<meta name="description" content="dev.to | markdown basics">
|
||||
<%= meta_keywords_default %>
|
||||
<% end %>
|
||||
|
||||
<div class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0">Markdown Basics 🤓</h1>
|
||||
|
||||
<p>Below are some examples of commonly used markdown syntax. If you want to dive deeper, check out
|
||||
<a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet" target="_blank" rel="noopener">this cheat sheet.</a>
|
||||
</p>
|
||||
|
||||
<h3><strong>Bold & Italic</strong></h3>
|
||||
<p><em>Italics</em>: <code>*asterisks* or _underscores_</code></p>
|
||||
<p><strong>Bold</strong>: <code>**double asterisks** or __double underscores__</code></p>
|
||||
|
||||
<h3><strong>Links</strong></h3>
|
||||
<p><a href="https://dev.to">I'm an inline link</a>: <code>[I'm an inline link](put-link-here)</code></p>
|
||||
|
||||
<h3><strong>Inline Images</strong></h3>
|
||||
<p>
|
||||
<img src="https://res.cloudinary.com/practicaldev/image/fetch/s--OsLaFSo9--/c_fill,f_auto,fl_progressive,h_220,q_auto,w_220/https://thepracticaldev.s3.amazonaws.com/uploads/user/profile_image/31047/af153cd6-9994-4a68-83f4-8ddf3e13f0bf.jpg" alt="example image, with sloan" loading="lazy" />
|
||||
<code></code>
|
||||
</p>
|
||||
|
||||
<h3><strong>Headers</strong></h3>
|
||||
<p>Add a header to your post with this syntax:</p>
|
||||
<pre>
|
||||
<code><br>#One '#' for a h1 header<br>##Two '#'s for a h2 header<br>...<br>######Six '#'s for a h6 header</code>
|
||||
</pre>
|
||||
<h1>One '#' for a h1 header</h1>
|
||||
<h2>Two '#'s for a h2 header</h2>
|
||||
<h6>Six '#'s for a h6 header</h6>
|
||||
|
||||
<hr />
|
||||
|
||||
<%= render partial: "liquid_tag_section_intro", locals: { styles: "font-size:2.4em;" } %>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "supported-url-embeds-list", title: "Supported URL Embeds" } %>
|
||||
|
||||
<%= render partial: "supported_url_embeds_list" %>
|
||||
|
||||
<%= render partial: "editor_guide_h3", locals: { id: "supported-nonurl-embeds-list", title: "Supported Non-URL Embeds" } %>
|
||||
|
||||
<%= render partial: "supported_nonurl_embeds_list" %>
|
||||
|
||||
<h3><strong>Parsing Liquid Tags as a Code Example</strong></h3>
|
||||
<p>To parse Liquid tags as code, simply wrap it with a single backtick or triple backticks.</p>
|
||||
<p><code>`{% mytag %}{{ site.SOMETHING }}{% endmytag %}`</code></p>
|
||||
<p>One specific edge case is with using the <code>raw</code> tag. To properly escape it, use this format:</p>
|
||||
<p><code>`{% raw %}{{site.SOMETHING }} {% ``endraw`` %}`</code></p>
|
||||
|
||||
<h4>
|
||||
<a href="https://github.com/adam-p/markdown-here/wiki/Markdown-Here-Cheatsheet" target="_blank" rel="noopener">Here's the Markdown cheatsheet again for reference.</a>
|
||||
</h4>
|
||||
Happy posting! 📝
|
||||
</div>
|
||||
</div>
|
||||
1
app/views/pages/post_a_job.fr.html.erb
Normal file
1
app/views/pages/post_a_job.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "Posting a Job on #{community_name} Listings" } %>
|
||||
27
app/views/pages/privacy.fr.html.erb
Normal file
27
app/views/pages/privacy.fr.html.erb
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
<% title("Privacy Policy for #{community_name}") %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url("/privacy") %>" />
|
||||
<meta name="description" content="Privacy Policy for <%= community_name %>">
|
||||
<%= meta_keywords_default %>
|
||||
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="<%= app_url("/privacy") %>" />
|
||||
<meta property="og:title" content="Privacy Policy for <%= community_name %>" />
|
||||
<meta property="og:image" content="<%= Settings::General.main_social_image %>" />
|
||||
<meta property="og:description" content="<%= community_name %> is great!" />
|
||||
<meta property="og:site_name" content="<%= community_name %>" />
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@<%= Settings::General.social_media_handles["twitter"] %>">
|
||||
<meta name="twitter:title" content="Privacy Policy for <%= community_name %>">
|
||||
<meta name="twitter:description" content="<%= community_name %> is great!">
|
||||
<meta name="twitter:image:src" content="<%= Settings::General.main_social_image %>">
|
||||
<% end %>
|
||||
|
||||
<main id="main-content" class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0">Privacy Policy</h1>
|
||||
<%= render "privacy_text" %>
|
||||
</div>
|
||||
</main>
|
||||
46
app/views/pages/publishing_from_rss_guide.fr.html.erb
Normal file
46
app/views/pages/publishing_from_rss_guide.fr.html.erb
Normal file
|
|
@ -0,0 +1,46 @@
|
|||
<% title "Editor Guide - Publishing from RSS or Atom" %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url(publishing_from_rss_guide_path) %>" />
|
||||
<meta name="description" content="<%= community_name %> | Publishing from RSS or Atom guidelines">
|
||||
<%= meta_keywords_default %>
|
||||
<% end %>
|
||||
|
||||
<main class="container article" id="main-content">
|
||||
<div class="title help-guide-title">
|
||||
<h1>Publishing from RSS or Atom</h1>
|
||||
</div>
|
||||
|
||||
<div class="body">
|
||||
<h2>Front Matter</h2>
|
||||
|
||||
<p>Our feed reader converts some elements from the RSS or Atom feeds to tags for the editor's front matter:</p>
|
||||
<ul>
|
||||
<li>
|
||||
<code><title></code>: <strong>title</strong>, the title of the post
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<code><category></code>: <strong>tags</strong>, only the first four <code><category></code> elements
|
||||
can be used in a post on <%= community_name %> per each item in the feed.
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<code><link></code>: <strong>canonical_url</strong>, only used if the "Mark the RSS source as canonical URL by default"
|
||||
option is enabled in the <%= link_to "RSS Settings", user_settings_path(:extensions) %>.
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<h2>Post Content</h2>
|
||||
|
||||
<p>
|
||||
The post content is prioritized in this order: <code><content></code>, <code><summary></code>, or
|
||||
<code><description></code>.
|
||||
</p>
|
||||
|
||||
<p>The HTML will be converted to Markdown as the body of the <%= community_name %> post.</p>
|
||||
|
||||
<p>If you're using Medium RSS feed all its tweet links, YouTube, and Gist iframes will be converted to Liquid tags.</p>
|
||||
<div class="blank-space"></div>
|
||||
</div>
|
||||
</main>
|
||||
29
app/views/pages/report_abuse.fr.html.erb
Normal file
29
app/views/pages/report_abuse.fr.html.erb
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
<% title t("core.report_abuse") %>
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url("/report-abuse") %>" />
|
||||
<meta name="description" content="<%= t("core.report_abuse") %>">
|
||||
<%= meta_keywords_default %>
|
||||
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="<%= app_url("/report-abuse") %>" />
|
||||
<meta property="og:title" content="<%= t("core.report_abuse") %>" />
|
||||
<meta property="og:site_name" content="<%= community_name %>" />
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@<%= Settings::General.social_media_handles["twitter"] %>">
|
||||
<meta name="twitter:title" content="<%= t("core.report_abuse") %>">
|
||||
<% end %>
|
||||
|
||||
<div class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0"><%= t("core.report_abuse") %></h1>
|
||||
|
||||
<p>
|
||||
Thank you for reporting any abuse that violates our <a href="/code-of-conduct">code of conduct</a> or
|
||||
<a href="/terms">terms and conditions</a>. We continue to try to make this environment a great one for everybody.
|
||||
</p>
|
||||
|
||||
<div class="crayons-card crayons-card--secondary p-4 m:p-6">
|
||||
<%= render "feedback_messages/form", feedback_message: @feedback_message %>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
44
app/views/pages/show.fr.html.erb
Normal file
44
app/views/pages/show.fr.html.erb
Normal file
|
|
@ -0,0 +1,44 @@
|
|||
<% title @page.title %>
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url(@page.path) %>" />
|
||||
<meta name="description" content="<%= @page.title %> — <%= community_name %>">
|
||||
<%= meta_keywords_default %>
|
||||
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="<%= app_url(@page.path) %>" />
|
||||
<meta property="og:title" content="<%= @page.title %> — <%= community_name %>" />
|
||||
<meta property="og:image" content="<%= Settings::General.main_social_image %>">
|
||||
<meta property="og:description" content="<%= @page.description %>" />
|
||||
<meta property="og:site_name" content="<%= community_name %>" />
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@<%= Settings::General.social_media_handles["twitter"] %>">
|
||||
<meta name="twitter:title" content="<%= @page.title %> — <%= community_name %>">
|
||||
<meta name="twitter:description" content="<%= @page.description %>">
|
||||
<meta name="twitter:image:src" content="<%= Settings::General.main_social_image %>">
|
||||
<% end %>
|
||||
|
||||
<main id="main-content">
|
||||
<% if @page.template == "contained" %>
|
||||
<div class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0"><%= @page.title %></h1>
|
||||
|
||||
<%= @page.processed_html.html_safe %>
|
||||
</div>
|
||||
</div>
|
||||
<% elsif @page.template == "nav_bar_included" %>
|
||||
<div class="crayons-layout crayons-layout--2-cols">
|
||||
<div class="hidden m:block">
|
||||
<%= render "articles/sidebar" %>
|
||||
</div>
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0"><%= @page.title %></h1>
|
||||
<%= @page.processed_html.html_safe %>
|
||||
</div>
|
||||
</div>
|
||||
<% else %>
|
||||
<%= @page.processed_html.html_safe %>
|
||||
<% end %>
|
||||
</main>
|
||||
<div id="IS_CENTERED_PAGE"></div>
|
||||
1
app/views/pages/tag_moderation.fr.html.erb
Normal file
1
app/views/pages/tag_moderation.fr.html.erb
Normal file
|
|
@ -0,0 +1 @@
|
|||
<%= render partial: "placeholder", locals: { title: "Tag Moderation Guide" } %>
|
||||
27
app/views/pages/terms.fr.html.erb
Normal file
27
app/views/pages/terms.fr.html.erb
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
<% title("Terms of Use for #{community_name}") %>
|
||||
|
||||
<%= content_for :page_meta do %>
|
||||
<link rel="canonical" href="<%= app_url("/terms") %>" />
|
||||
<meta name="description" content="Terms of Use for <%= community_name %>">
|
||||
<%= meta_keywords_default %>
|
||||
|
||||
<meta property="og:type" content="article" />
|
||||
<meta property="og:url" content="<%= app_url("/terms") %>" />
|
||||
<meta property="og:title" content="Terms of Use for <%= community_name %>" />
|
||||
<meta property="og:image" content="<%= Settings::General.main_social_image %>" />
|
||||
<meta property="og:description" content="<%= community_name %> is great!" />
|
||||
<meta property="og:site_name" content="<%= community_name %>" />
|
||||
|
||||
<meta name="twitter:card" content="summary_large_image">
|
||||
<meta name="twitter:site" content="@<%= Settings::General.social_media_handles["twitter"] %>">
|
||||
<meta name="twitter:title" content="Terms of Use for <%= community_name %>">
|
||||
<meta name="twitter:description" content="<%= community_name %> is great!">
|
||||
<meta name="twitter:image:src" content="<%= Settings::General.main_social_image %>">
|
||||
<% end %>
|
||||
|
||||
<main id="main-content" class="crayons-layout crayons-layout--limited-l">
|
||||
<div class="crayons-card text-styles text-padding">
|
||||
<h1 class="fs-3xl s:fs-4xl l:fs-5xl fw-bold s:fw-heavy lh-tight mb-4 mt-0">Web Site Terms and Conditions of Use</h1>
|
||||
<%= Page.render_safe_html_for(slug: Page::TERMS_SLUG) { render "terms_text" } %>
|
||||
</div>
|
||||
</main>
|
||||
|
|
@ -19,6 +19,9 @@ en:
|
|||
meta:
|
||||
title: Purchase Credits
|
||||
heading: Purchase credits for @%{name}
|
||||
hook:
|
||||
text_html: Credits are used for %{listings} as well as upcoming products and services.
|
||||
listings: "%{community} listings"
|
||||
form:
|
||||
amount:
|
||||
label: Amount to Purchase
|
||||
|
|
|
|||
|
|
@ -19,6 +19,9 @@ fr:
|
|||
meta:
|
||||
title: Purchase Credits
|
||||
heading: Purchase credits for @%{name}
|
||||
hook:
|
||||
text_html: Credits are used for %{listings} as well as upcoming products and services.
|
||||
listings: "%{community} listings"
|
||||
form:
|
||||
amount:
|
||||
label: Amount to Purchase
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue