Please consider add Pixexid https://pixexid.com is a free image community with features like visual crop and 360 panoramas. (custom license)

I tried the doc about nested block

file "base":

===
{% block a %}{% endblock %}
===

file "child"

{% if not Standalone %} {% extends "base" %}{% endif %}
{% for item in ("a","b","c") %}
  {% set int = loop.index %}
  {% block a scoped %}
  {{ int }} : {{ item }}
  {% endblock %}  
{% endfor %}      

301-servicebus-namespace-vnet

Issue Details

Readme points to docs at https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-service-endpoints, which show how to create firewall rules by creating a "Microsoft.ServiceBus/namespaces/networkruleset" resource. However the template

Hello!

I was reading this post: SwiftGen/SwiftGen#228

Seems like one of the user was able to generate .imagestack from the Asset.assets. However when I tried it was only able to generate .imageset files.

Maybe I am missing something? My script is the same as the example one on Github for Assets.

Or is this not supported anymore?

Thanks!

I've been using Sourcery to generate documentation automatically for GitHub wiki (i.e. generate markdown files based on types & annotations), as it's pretty user friendly on there (as in "easy to read") and also very easy to do in templates thanks to Sourcery's capability to generate files on the fly.

However, using annotations is not very "coder-friendly" though, as it gets hard to maintain be

It will be informative if the default directory structure with file types and look up and processing order is added to the documentation.

Assemble's highly modular nature makes it difficult to discover methods that are added via mixins or inheritance. For example, .use and .define are provided by Base and implicitely added through Templates.

It would be a huge help to have some basic, generated JSDocs that incorporate all of the default packages. JSDoc provides the @mixinand [`@mix

It should involve things such as description, s/w requirements, h/w requirements, schematics, usage etc.

Refer to the various Arduino project documentations for assistance.

Thanks for the easy-to-follow tutorial!

A few minor discrepancies between the tutorial and actual response for update (totally not urgent, these did not prevent any functionality -- just wanted to help keep things current):

On http://yeoman.io/codelab/scaffold-app.html
the following options in the CLI are missing from the tutorial page:

"Which Continuous Integration platform do you want? (Pre

Problem

https://github.com/blockstack/blockstack/blob/master/engineering/README.md

This document is far too large and contains manual steps (error-prone, must be remembered).

The process should be "build-in" to tools. As an example, the github-issue-tracker is not capable to model a more complex workflow.

If you favor "Sprints", use a tool where you can file the sprints.

If you f

What is the PR? please refer to ant design pro.

Contributing:

1. Fork ant-design-landing and git clone.
2. Create a branch starting at master and name it as translation-[xxx]
3. npm install && npm start.
4. Find Markdown files and the docs/*.md and docs/*/*.md use d

Spring v3 functions look great! However it looks like current (non v3) versions of Helm are pinned to Sprig v2. Some kind of note that the documentation is for v3 and not v2 would be useful. Having v2 documentation also available online would be nice, too. And I would also recommend a practice of having "introduced in version" notes on new functions going forward, or perhaps an outlink to a Ch

The link to Django version compatibility 1.7 in the README's Development status section is broken, it looks like this version is not supported anymore: https://docs.djangoproject.com/en/1.7/ref/templates/builtins/

I suggest to either include a reference of actually implemented filters in your project's documentation, or ensure support for Django 1.8 or higher so you can link to their document

Expected Behavior

When visiting the Shards UI demo page, using the left and right tooltip/popover examples places the info on the opposite of the expected side of the element.

Using data-placement="left" should place elements on the left. Similarly data-placement="right" should place elements on the right.

Current Behavior

Example screenshots:

![Screenshot_20190626-135428](http

Which naming convention should be used for template names? Should it be snake_case, camelCase, PascalCase or something else?
This should be specified in documentation of syntax.

The current tufte-book documentation has no guidance on the how to display epigraphs. Use of the \epigraph package seems incongruous with the general style and theme of the tufte-book class. Could guidance be given on a way to display quotes at the beginning of a chapter?

@jezdez I just like to let you know that I requested access for the Codacy app on GitHub on probably the entire jazzband organization. What I intended was just for this repository.

Background: I'm about to phase out the Landscape service for monitoring our code quality and use Codacy instead. I'm also replacing the related badge at the top of the README.

I hope that's fine.

Hi,

Shouldn't the README say

// First set or import your overrides
$text-color: #000;

instead of

// First set or import your overrides
$textColor: #000;

?