Developing Themes
A guide to creating and distributing custom themes.
!!! Note
If you are looking for existing third party themes, they are listed in the
MkDocs [community wiki]. If you want to share a theme you create, you
should list it on the Wiki.
When creating a new theme, you can either follow the steps in this guide to
create one from scratch or you can download the mkdocs-basic-theme
as a
basic, yet complete, theme with all the boilerplate required. You can find
this base theme on GitHub. It contains detailed comments in
the code to describe the different features and their usage.
Creating a custom theme
The bare minimum required for a custom theme is a main.html
Jinja2
template file which is placed in a directory that is not a child of the
docs_dir. Within mkdocs.yml
, set the theme.custom_dir
option to the path of the directory containing main.html
. The path should be
relative to the configuration file. For example, given this example project
layout:
mkdocs.yml
docs/
index.md
about.md
custom_theme/
main.html
...
… you would include the following settings in mkdocs.yml
to use the custom theme
directory:
theme:
name: null
custom_dir: 'custom_theme/'
!!! Note
Generally, when building your own custom theme, the theme.[name]
configuration setting would be set to `null`. However, if the
theme.[custom_dir] configuration value is used in combination with an
existing theme, the theme.[custom_dir] can be used to replace only specific
parts of a built-in theme. For example, with the above layout and if you set
`name: "mkdocs"` then the `main.html` file in the theme.[custom_dir] would
replace the file of the same name in the `mkdocs` theme but otherwise the
`mkdocs` theme would remain unchanged. This is useful if you want to make
small adjustments to an existing theme.
For more specific information, see [Customizing Your Theme].
!!! Warning
A theme's [configuration] defined in a `mkdocs_theme.yml` file is not loaded
from `theme.custom_dir`. When an entire theme exists in `theme.custom_dir`
and `theme.name` is set to `null`, then the entire theme configuration must
be defined in the [theme] configuration option in the `mkdocs.yml` file.
However, when a theme is [packaged] up for distribution, and loaded using
the `theme.name` configuration option, then a `mkdocs_theme.yml` file
is required for the theme.
Basic theme
The simplest main.html
file is the following:
<!DOCTYPE html>

<title>{% if page.title %}{{ page.title }} - {% endif %}{{ config.site_name }}</title>

{{ page.content }}

The body content from each page specified in mkdocs.yml
is inserted using the
{{ page.content }}
tag. Style-sheets and scripts can be brought into this
theme as with a normal HTML file. Navbars and tables of contents can also be
generated and included automatically, through the nav
and toc
objects,
respectively. If you wish to write your own theme, it is recommended to start
with one of the built-in themes and modify it accordingly.
!!! Note
As MkDocs uses [Jinja] as its template engine, you have access to all the
power of Jinja, including [template inheritance]. You may notice that the
themes included with MkDocs make extensive use of template inheritance and
blocks, allowing users to easily override small bits and pieces of the
templates from the theme [custom_dir]. Therefore, the built-in themes are
implemented in a `base.html` file, which `main.html` extends. Although not
required, third party template authors are encouraged to follow a similar
pattern and may want to define the same [blocks] as are used in the built-in
themes for consistency.
Theme Files
There are various files which a theme treats special in some way. Any other
files are simply copied from the theme directory to the same path in the
site_dir
when the site it built. For example image and CSS files have no
special significance and are copied as-is. Note, however, that if the user
provides a file with the same path in their docs_dir
, then the user’s file
will replace the theme file.
Template Files
Any files with the .html
extension are considered to be template files and are
not copied from the theme directory or any subdirectories. Also, any files
listed in static_templates are treated as templates regardless of their file
extension.
Theme Meta Files
The various files required for packaging a theme are also ignored. Specifically,
the mkdocs_theme.yml
configuration file and any Python files.
Dot Files
Theme authors can explicitly force MkDocs to ignore files by starting a file or directory name with a dot. Any of the following files would be ignored:
.ignored.txt
.ignored/file.txt
foo/.ignored.txt
foo/.ignored/file.txt
Documentation Files
All documentation files are ignored. Specifically, any Markdown files (using any of the file extensions supported by MKDocs). Additionally, any README files which may exist in the theme directories are ignored.
Template Variables
Each template in a theme is built with a template context. These are the variables that are available to themes. The context varies depending on the template that is being built. At the moment templates are either built with the global context or with a page specific context. The global context is used for HTML pages that don’t represent an individual Markdown document, for example a 404.html page or search.html.
Global Context
The following variables are available globally on any template.
config
The config
variable is an instance of MkDocs’ config object generated from the
mkdocs.yml
config file. While you can use any config option, some commonly
used options include:
- config.site_name
- config.site_url
- config.site_author
- config.site_description
- config.theme.locale (See also Theme Configuration below)
- config.extra_javascript
- config.extra_css
- config.repo_url
- config.repo_name
- config.copyright
- config.google_analytics
nav
The nav
variable is used to create the navigation for the documentation. The
nav
object is an iterable of navigation objects as
defined by the nav configuration setting.
In addition to the iterable of navigation objects, the
nav
object contains the following attributes:
nav.homepage
The page object for the homepage of the site.
nav.pages
A flat list of all page objects contained in the navigation. This list is not necessarily a complete list of all site pages as it does not contain pages which are not included in the navigation. This list does match the list and order of pages used for all “next page” and “previous page” links. For a list of all pages, use the pages template variable.
Nav Example
Following is a basic usage example which outputs the first and second level navigation as a nested list.
{% if nav|length>1 %}

{% for nav_item in nav %}
{% if nav_item.children %}

{{ nav_item.title }}

{% for nav_item in nav_item.children %}

{{ nav_item.title }}

{% endfor %}

{% else %}

{{ nav_item.title }}

{% endif %}
{% endfor %}

{% endif %}
base_url
The base_url
provides a relative path to the root of the MkDocs project. While
this can be used directly by prepending it to a local relative URL, it is best
to use the url template filter, which is smarter about how it applies
base_url
.
mkdocs_version
Contains the current MkDocs version.
build_date_utc
A Python datetime object that represents the date and time the documentation was built in UTC. This is useful for showing how recently the documentation was updated.
pages
A flat list of File
objects for all pages in the project. This list can
contain pages not included in the global navigation and may not match
the order of pages within that navigation. The page object for each
File
can be accessed from file.page
.
page
In templates which are not rendered from a Markdown source file, the page
variable is None
. In templates which are rendered from a Markdown source file,
the page
variable contains a page
object. The same page
objects are used
as page
navigation objects in the global
navigation and in the pages template variable.
All page
objects contain the following attributes:
page.title
Contains the Title for the current page.
page.content
The rendered Markdown as HTML, this is the contents of the documentation.
page.toc
An iterable object representing the Table of contents for a page. Each item in
the toc
is an AnchorLink
which contains the following attributes:
AnchorLink.title
: The text of the item.AnchorLink.url
: The hash fragment of a URL pointing to the item.AnchorLink.level
: The zero-based level of the item.AnchorLink.children
: An iterable of any child items.
The following example would display the top two levels of the Table of Contents for a page.

{% for toc_item in page.toc %}

{{ toc_item.title }}

{% for toc_item in toc_item.children %}

{{ toc_item.title }}

{% endfor %}
{% endfor %}

page.meta
A mapping of the metadata included at the top of the markdown page. In this
example we define a source
property above the page title.
source: generics.py
mixins.py
# Page title
Content...
A template can access this metadata for the page with the meta.source
variable. This could then be used to link to source files related to the
documentation page.
{% for filename in page.meta.source %}

{{ filename }}

{% endfor %}
page.url
The URL of the page relative to the MkDocs site_dir
. It is expected that this
be used with the url filter to ensure the URL is relative to the current
page.
{{ page.title }}
page.abs_url
The absolute URL of the page from the server root as determined by the value
assigned to the site_url configuration setting. The value includes any
subdirectory included in the site_url
, but not the domain. base_url should
not be used with this variable.
For example, if site_url: https://example.com/
, then the value of
page.abs_url
for the page foo.md
would be /foo/
. However, if
site_url: https://example.com/bar/
, then the value of page.abs_url
for the
page foo.md
would be /bar/foo/
.
page.canonical_url
The full, canonical URL to the current page as determined by the value assigned
to the site_url configuration setting. The value includes the domain and any
subdirectory included in the site_url
. base_url should not be used with this
variable.
page.edit_url
The full URL to the source page in the source repository. Typically used to provide a link to edit the source page. base_url should not be used with this variable.
page.is_homepage
Evaluates to True
for the homepage of the site and False
for all other
pages. This can be used in conjunction with other attributes of the page
object to alter the behavior. For example, to display a different title
on the homepage:
{% if not page.is_homepage %}{{ page.title }} - {% endif %}{{ site_name }}
page.previous_page
The page object for the previous page or None
. The value will be None
if the
current page is the first item in the site navigation or if the current page is
not included in the navigation at all. When the value is a page object, the
usage is the same as for page
.
page.next_page
The page object for the next page or None
. The value will be None
if the
current page is the last item in the site navigation or if the current page is
not included in the navigation at all. When the value is a page object, the
usage is the same as for page
.
page.parent
The immediate parent of the page in the site navigation. None
if the
page is at the top level.
page.children
Pages do not contain children and the attribute is always None
.
page.active
When True
, indicates that this page is the currently viewed page. Defaults
to False
.
page.is_section
Indicates that the navigation object is a “section” object. Always False
for
page objects.
page.is_page
Indicates that the navigation object is a “page” object. Always True
for
page objects.
page.is_link
Indicates that the navigation object is a “link” object. Always False
for
page objects.
Navigation Objects
Navigation objects contained in the nav template variable may be one of section objects, page objects, and link objects. While section objects may contain nested navigation objects, pages and links do not.
Page objects are the full page object as used for the current page with all of the same attributes available. Section and Link objects contain a subset of those attributes as defined below:
Section
A section
navigation object defines a named section in the navigation and
contains a list of child navigation objects. Note that sections do not contain
URLs and are not links of any kind. However, by default, MkDocs sorts index
pages to the top and the first child might be used as the URL for a section if a
theme chooses to do so.
The following attributes are available on section
objects:
section.title
The title of the section.
section.parent
The immediate parent of the section or None
if the section is at the top
level.
section.children
An iterable of all child navigation objects. Children may include nested sections, pages and links.
section.active
When True
, indicates that a child page of this section is the current page and
can be used to highlight the section as the currently viewed section. Defaults
to False
.
section.is_section
Indicates that the navigation object is a “section” object. Always True
for
section objects.
section.is_page
Indicates that the navigation object is a “page” object. Always False
for
section objects.
section.is_link
Indicates that the navigation object is a “link” object. Always False
for
section objects.
Link
A link
navigation object contains a link which does not point to an internal
MkDocs page. The following attributes are available on link
objects:
link.title
The title of the link. This would generally be used as the label of the link.
link.url
The URL that the link points to. The URL should always be an absolute URLs and
should not need to have base_url
prepended.
link.parent
The immediate parent of the link. None
if the link is at the top level.
link.children
Links do not contain children and the attribute is always None
.
link.active
External links cannot be “active” and the attribute is always False
.
link.is_section
Indicates that the navigation object is a “section” object. Always False
for
link objects.
link.is_page
Indicates that the navigation object is a “page” object. Always False
for
link objects.
link.is_link
Indicates that the navigation object is a “link” object. Always True
for
link objects.
Extra Context
Additional variables can be passed to the template with the
extra
configuration option. This is a
set of key value pairs that can make custom templates far more flexible.
For example, this could be used to include the project version of all pages
and a list of links related to the project. This can be achieved with the
following extra
configuration:
extra:
version: 0.13.0
links:
- https://github.com/mkdocs
- https://docs.readthedocs.org/en/latest/builds.html#mkdocs
- https://www.mkdocs.org/
And then displayed with this HTML in the custom theme.
{{ config.extra.version }}
{% if config.extra.links %}

{% for link in config.extra.links %}

{{ link }}

{% endfor %}

{% endif %}
Template Filters
In addition to Jinja’s default filters, the following custom filters are available to use in MkDocs templates:
url
Normalizes a URL. Absolute URLs are passed through unaltered. If the URL is relative and the template context includes a page object, then the URL is returned relative to the page object. Otherwise, the URL is returned with base_url prepended.
{{ page.title }}
tojson
Safety convert a Python object to a value in a JavaScript script.

Search and themes
As of MkDocs version 0.17 client side search support has been added to MkDocs
via the search
plugin. A theme needs to provide a few things for the plugin to
work with the theme.
While the search
plugin is activated by default, users can disable the plugin
and themes should account for this. It is recommended that theme templates wrap
search specific markup with a check for the plugin:
{% if 'search' in config['plugins'] %}
search stuff here...
{% endif %}
At its most basic functionality, the search plugin will simply provide an index file which is no more than a JSON file containing the content of all pages. The theme would need to implement its own search functionality client-side. However, with a few settings and the necessary templates, the plugin can provide a complete functioning client-side search tool based on lunr.js.
The following HTML needs to be added to the theme so that the provided JavaScript is able to properly load the search scripts and make relative links to the search results from the current page.

With properly configured settings, the following HTML in a template will add a full search implementation to your theme.

Search Results

<form action="search.html">
<input name="q" id="mkdocs-search-query" type="text" >
</form>

Sorry, page not found.

The JavaScript in the plugin works by looking for the specific ID’s used in the
above HTML. The form input for the user to type the search query must be
identified with id="mkdocs-search-query"
and the div where the results will be
placed must be identified with id="mkdocs-search-results"
.
The plugin supports the following options being set in the theme’s
configuration file, mkdocs_theme.yml
:
include_search_page
Determines whether the search plugin expects the theme to provide a dedicated
search page via a template located at search/search.html
.
When include_search_page
is set to true
, the search template will be built
and available at search/search.html
. This method is used by the readthedocs
theme.
When include_search_page
is set to false
or not defined, it is expected that
the theme provide some other mechanisms for displaying search results. For
example, the mkdocs
theme displays results on any page via a modal.
search_index_only
Determines whether the search plugin should only generate a search index or a complete search solution.
When search_index_only
is set to false
, then the search plugin modifies the
Jinja environment by adding its own templates
directory (with a lower
precedence than the theme) and adds its scripts to the extra_javascript
config
setting.
When search_index_only
is set to true
or not defined, the search plugin
makes no modifications to the Jinja environment. A complete solution using the
provided index file is the responsibility of the theme.
The search index is written to a JSON file at search/search_index.json
in the
site_dir. The JSON object contained within the file may contain up to three
objects.
{
config: {...},
data: [...],
index: {...}
}
If present, the config
object contains the key/value pairs of config options
defined for the plugin in the user’s mkdocs.yml
config file under
plugings.search
. The config
object was new in MkDocs version 1.0.
The data
object contains a list of document objects. Each document object is
made up of a location
(URL), a title
, and text
which can be used to create
a search index and/or display search results.
If present, the index
object contains a pre-built index which offers
performance improvements for larger sites. Note that the pre-built index is only
created if the user explicitly enables the prebuild_index config option.
Themes should expect the index to not be present, but can choose to use the
index when it is available. The index
object was new in MkDocs version 1.0.
Packaging Themes
MkDocs makes use of Python packaging to distribute themes. This comes with a few requirements.
To see an example of a package containing one theme, see the MkDocs Bootstrap theme and to see a package that contains many themes, see the MkDocs Bootswatch theme.
!!! Note
It is not strictly necessary to package a theme, as the entire theme
can be contained in the `custom_dir`. If you have created a "one-off theme,"
that should be sufficient. However, if you intend to distribute your theme
for others to use, packaging the theme has some advantages. By packaging
your theme, your users can more easily install it, they can rely on a default
[configuration] being defined, and they can then take advantage of the
[custom_dir] to make tweaks to your theme to better suit their needs.
Package Layout
The following layout is recommended for themes. Two files at the top level
directory called MANIFEST.in
and setup.py
beside the theme directory which
contains an empty __init__.py
file, a theme configuration file
(mkdocs-theme.yml
), and your template and media files.
.
|-- MANIFEST.in
|-- theme_name
| |-- __init__.py
| |-- mkdocs-theme.yml
| |-- main.html
| |-- styles.css
`-- setup.py
The MANIFEST.in
file should contain the following contents but with
theme_name updated and any extra file extensions added to the include.
recursive-include theme_name *.ico *.js *.css *.png *.html *.eot *.svg *.ttf *.woff
recursive-exclude * __pycache__
recursive-exclude * *.py[co]
The setup.py
should include the following text with the modifications
described below.
from setuptools import setup, find_packages
VERSION = '0.0.1'
setup(
name="mkdocs-themename",
version=VERSION,
url='',
license='',
description='',
author='',
author_email='',
packages=find_packages(),
include_package_data=True,
entry_points={
'mkdocs.themes': [
'themename = theme_name',
]
},
zip_safe=False
)
Fill in the URL, license, description, author and author email address.
The name should follow the convention mkdocs-themename
(like mkdocs-
bootstrap
and mkdocs-bootswatch
), starting with MkDocs, using hyphens to
separate words and including the name of your theme.
Most of the rest of the file can be left unedited. The last section we need to change is the entry_points. This is how MkDocs finds the theme(s) you are including in the package. The name on the left is the one that users will use in their mkdocs.yml and the one on the right is the directory containing your theme files.
The directory you created at the start of this section with the main.html file
should contain all of the other theme files. The minimum requirement is that
it includes a main.html
for the theme. It must also include a
__init__.py
file which should be empty, this file tells Python that the
directory is a package.
Theme Configuration
A packaged theme is required to include a configuration file named
mkdocs_theme.yml
which is placed in the root of your template files. The file
should contain default configuration options for the theme. However, if the
theme offers no configuration options, the file is still required and can be
left blank. A theme which is not packaged does not need a mkdocs_theme.yml
file as that file is not loaded from theme.custom_dir
.
The theme author is free to define any arbitrary options deemed necessary and
those options will be made available in the templates to control behavior.
For example, a theme might want to make a sidebar optional and include the
following in the mkdocs_theme.yml
file:
show_sidebar: true
Then in a template, that config option could be referenced:
{% if config.theme.show_sidebar %}

...

{% endif %}
And the user could override the default in their project’s mkdocs.yml
config
file:
theme:
name: themename
show_sidebar: false
In addition to arbitrary options defined by the theme, MkDocs defines a few special options which alters its behavior:
!!! block “”
#### locale
This option mirrors the [theme] config option of the same name. If this
value is not defined in the `mkdocs_theme.yml` file and the user does not
set it in `mkdocs.yml` then it will default to `en` (English). The value
is expected to match the language used in the text provided by the theme
(such a "next" and "previous" links) and should be used as the value of
the `<html>` tag's `lang` attribute. See [Supporting theme localization/
translation](#supporting-theme-localizationtranslation) for more
information.
Note that during configuration validation, the provided string is converted
to a `Locale` object. The object contains `Locale.language` and
`Locale.territory` attributes and will resolve as a string from within a
template. Therefore, the following will work fine:

If the locale was set to `fr_CA` (Canadian French), then the above template
would render as:

If you did not want the territory attribute to be included, then reference
the `language` attribute directly:

That would render as:

#### static_templates
This option mirrors the [theme] config option of the same name and allows
some defaults to be set by the theme. Note that while the user can add
templates to this list, the user cannot remove templates included in the
theme's config.
#### extends
Defines a parent theme that this theme inherits from. The value should be
the string name of the parent theme. Normal Jinja inheritance rules apply.
Plugins may also define some options which allow the theme to inform a plugin about which set of plugin options it expects. See the documentation for any plugins you may wish to support in your theme.
Distributing Themes
With the above changes, your theme should now be ready to install. This can be
done with pip, using pip install .
if you are still in the same directory as
the setup.py.
Most Python packages, including MkDocs, are distributed on PyPI. To do this, you should run the following command.
python setup.py register
If you don’t have an account setup, you should be prompted to create one.
For a much more detailed guide, see the official Python packaging documentation for Packaging and Distributing Projects.
Supporting theme Localization/Translation
While the built-in themes provide support for localization/translation of
templates, custom themes and third-party themes may choose not to. Regardless,
the locale
setting of the theme
configuration option is always
present and is relied upon by other parts of the system. Therefore, it is
recommended that all third-party themes use the same setting for designating a
language regardless of the system they use for translation. In that way, users
will experience consistent behavior regardless of the theme they may choose.
The method for managing translations is up to the developers of a theme. However, if a theme developer chooses to use the same mechanisms used by the built-in themes, the sections below outline how to enable and make use of the same commands utilized by MkDocs.
Enabling the Localization/Translation commands
MkDocs includes some helper commands which are light wrappers around pybabel’s
commands. To use the commands on your own theme, add the following to
your theme’s setup.py
script:
from mkdocs.commands.setup import babel_cmdclass
setup(
...
cmdclass=babel_cmdclass
)
Note that cmdclass=babel_cmdclass
was added an a parameter passed to
the setup
function.
!!! warning
As pybabel is not installed by default and most users will not have
pybabel installed, theme developers and/or translators should make sure to
have installed the necessary dependencies
(using pip install mkdocs[i18n]
) in order for the commands to be
available for use.
Using the Localization/Translation commands
Since the translation commands are embedded in the setup.py
script of your
custom theme they should be called from the root of your theme’s working
tree as follows:
python setup.py <command_name> [OPTIONS]
Each command provides a detailed list of options available with the -h/--help
option.
For an overview of the workflow used by MkDocs to translate the built-in themes, see the appropriate section of the Contributing Guide and the Translation Guide.
Default values for many of the options to the commands can be defined in a
setup.cfg
file. Create a section using the command name as the section name,
and the long option name as the key. See MkDocs’ own setup.cfg file for an
example.
A summary of changes/additions to the behavior and options of the upstream pybabel commands are summarized below.
compile_catalog
The -t/--theme
option has been added to this command. The theme
specified
must be a theme
defined as a entry point in the same setup.py
script. Other
themes will not be recognized. If only one theme
has been defined as an entry
point, then that theme
will be used as the default if none is specified by
this option. If more than one theme
is defined as entry points, then no
default is set and a theme
must be specified by this option. The command only
operates on one theme at a time. Therefore, the command needs to be run once
for each theme included in a package.
When a theme
is specified, the directory of that theme
as defined in the
entry point is used to define a default value of the -d/--directory
option.
The --directory
option is set to {theme_dir}/locales
. If a directory
is
passed to the --directory
option, then the theme
option is ignored.
extract_messages
The -t/--theme
option has been added to this command. The theme
specified
must be a theme
defined as a entry point in the same setup.py
script. Other
themes will not be recognized. If only one theme
has been defined as an entry
point, then that theme
will be used as the default if none is specified by
this option. If more than one theme
is defined as entry points, then no
default is set and a theme
must be specified by this option. The command only
operates on one theme at a time. Therefore, the command needs to be run once
for each theme included in a package.
When a theme
is specified, the directory of that theme
as defined in the
entry point is used to define a default value for the --input-dirs
and
--output-file
options. The --input-dirs
option is set to the theme
directory and --output-file
is set to {theme_dir}/{domain}.pot
. If a path
is provided to either option, then the theme
option is ignored for that
option.
The --domain
option has been added to this command and can be used to
override the domain
used for the output-file
based on the theme
.
Defaults to messages
.
The -F/--mapping-file
option defaults to the mapping file used by MkDocs’
built-in themes. However, if that mapping file does not meet your theme’s needs
to can override it by providing your own and passing the path of that file into
the option.
init_catalog
The -t/--theme
option has been added to this command. The theme
specified
must be a theme
defined as a entry point in the same setup.py
script. Other
themes will not be recognized. If only one theme
has been defined as an entry
point, then that theme
will be used as the default if none is specified by
this option. If more than one theme
is defined as entry points, then no
default is set and a theme
must be specified by this option. The command only
operates on one theme at a time. Therefore, the command needs to be run once
for each theme included in a package.
When a theme
is specified, the directory of that theme
as defined in the
entry point is used to define a default value for the -i/--input-file
and
-d/--output-dir
options. The --input-file
option is set to
{theme_dir}/{domain}.pot
(domain
defaults to messages
) and --output-dir
is set to {theme_dir}/locales
. If a path is provided to either option, then
the theme
option is ignored for that option.
update_catalog
The -t/--theme
option has been added to this command. The theme
specified
must be a theme
defined as a entry point in the same setup.py
script. Other
themes will not be recognized. If only one theme
has been defined as an entry
point, then that theme
will be used as the default if none is specified by
this option. If more than one theme
is defined as entry points, then no
default is set and a theme
must be specified by this option. The command only
operates on one theme at a time. Therefore, the command needs to be run once
for each theme included in a package.
When a theme
is specified, the directory of that theme
as defined in the
entry point is used to define a default value for the -i/--input-file
and
-d/--output-dir
options. The --input-file
option is set to
{theme_dir}/{domain}.pot
(domain
defaults to messages
) and --output-dir
is set to {theme_dir}/locales
. If a path is provided to either option, then
the theme
option is ignored for that option.
Example custom theme Localization/Translation workflow
!!! note
If your theme inherits from an existing theme which already provides
translation catalogs, your theme's translations will be merged with the
parent theme's translations during a MkDocs build.
This means that you only need to concentrate on the added translations.
Yet, you will still benefit from the translations of the parent theme. At
the same time, you may override any of parent theme's translations!
Let’s suppose that you’re working on your own fork of the mkdocs-basic-theme and want to add translations to it.
You would first modify the setup.py
like this:
--- a/setup.py
+++ b/setup.py
@@ -1,4 +1,5 @@
from setuptools import setup, find_packages
+from mkdocs.commands.setup import babel_cmdclass
VERSION = '1.1'
@@ -18,5 +19,6 @@ setup(
'basictheme = basic_theme',
]
},
- zip_safe=False
+ zip_safe=False,
+ cmdclass=babel_cmdclass
)
Next, you would edit the templates by wrapping text in your HTML sources with
{% trans %}
and {% endtrans %}
as follows:
--- a/basic_theme/base.html
+++ b/basic_theme/base.html
@@ -88,7 +88,7 @@

-
This is an example theme for MkDocs.

+
{% trans %}This is an example theme for MkDocs.{% endtrans %}

It is designed to be read by looking at the theme HTML which is heavily
Then you would follow the Translation Guide as usual to get your translations running.
Packaging Translations with your theme
While the Portable Object Template (pot
) file created by the
extract_messages
command and the Portable Object (po
) files created by the
init_catalog
and update_catalog
commands are useful for creating and
editing translations, they are not used by MkDocs directly and do not need to
be included in a packaged release of a theme. When MkDocs builds a site with
translations, it only makes use of the binary mo
files(s) for the specified
locale. Therefore, when packaging a theme, you would need to make the
following addition to your MANIFEST.in
file:
recursive-include theme_name *.mo
Then, before building your Python package, you will want to ensure that the
binary mo
file for each locale is up-to-date by running the compile_catalog
command for each locale. MkDocs expects the binary mo
files to be located at
locales/<locale>/LC_MESSAGES/messages.mo
, which the compile_catalog
command automatically does for you. See Testing theme translations for
details.
!!! note
As outlined in our [Translation Guide], the MkDocs project has chosen to
include the `pot` and `po` files in our code repository, but not the
`mo` files. This requires us to always run `compile_catalog` before
packaging a new release regardless of whether any changes were made to a
translation or not. However, you may chose an alternate workflow for your
theme. At a minimum, you need to ensure that up-to-date `mo` files are
included at the correct location in each release. However, you may use a
different process for generating those `mo` files if you chose to do so.


Generator helpers
ikki has several built-in helpers. (named after Japanese historical cities)
1. Kyoto
Kyoto
takes event-driven approach. And you don't have to care about the generator which is relatively new in JavaScript.
var kyoto = require('ikki/lib/kyoto.es')
var HELLO = ['Hello', 'こんにちは', '你好', 'Salut', 'Hallo']
this.hello = kyoto(function(push, path, query, param) {
push(\{ message: 'Click me!', btns: ['Next'] })
}, {
'click': (push, data) => \{
push(\{ message: HELLO[n = ++n % HELLO.length] + '!' })
}
})
2. Edo
On the other hand, edo
is the generator based flow-controler. If you need serial/branching interactions with user's input, this will be a perfect solution.
var edo = require('ikki/lib/edo.es')
this.dialog = edo('click', function* direction(path, query, param) \{
yield \{ message: 'Good morning!', btns: ['Hi'] }
let fruit = yield \{ message: 'Which do you like?', btns: ['apple', 'banana'] }
yield \{ message: "OK, I'll give you this " + fruit + '.', btns: ['Thanks'] }
yield \{ message: 'See you!', btns: ['Bye'] }
})


Bargellinator is a generative* bargello* pattern designer.
*Generative here means that we're giving computers a small set of constrained inputs and seeing what it kicks out at the end!
*Bargello is an embroidery technique that uses yarn on canvas mesh.

Bargello is a 17th century needlework technique that uses brightly colored yarn on canvas or plastic mesh to create repetitive patterns.
The technique had a resurgence in popularity in the 1960s, but has fallen out of favor in the intervening decades. Because of bargello's waning popularity, there simply aren't as many patterns available to the modern stitcher as there are for other fiber arts, like knitting, cross-stitch, embroidery, or weaving.
This site my personal attempt to decode what makes bargello patterns so fun and unique, while hopefully providing inspiration to other stitchers. (It's a remarkably mathematical art form!
If you're interested in how the Bargellinator works, you can peek at the raw (but annotated!) Javascript code here.
Love,
Austin


In Immunity Debugger, set where mona will be logging all of its output
!mona config -set workingfolder c:\logs\%p
Now we need to generate a byte array for comparison. In Immunity, run the command:
!mona bytearray -b "\x00" #I always exclude null byte
(look at manual for other flags)
Go to logging directory set in the first step and copy list of bad characters generated in 'bytearray.txt' to your exploit. Please note that exploit MUST match 'bytearray.txt' for this to work properly.
Run exploit and make sure it's 'badchars' variable matches 'bytearray.txt'
Exploit may crash, run the command in Immunity:
!mona compare -f C:\logs\program_name\bytearray.bin -a <badchars_start_address>
This will compare chars in 'bytearray.txt' with those in memory (pushed by the exploit) and split ones that cause the program to act funny. Please note that the memory address needes to be accurate. If 'badchars' in exploit start 2 bytes after left-hand side address in Immunity, you'd need to increment that by two bytes in the above command
Rinse and repeat
!mona compare -f C:\Users\Offsec\Desktop\offsec_pwk_srv\bytearray.bin -a 002AED14


{{ block title }} PART 3 {{ endblock }} {{ block content }} {{ include Constants.instforgame_template }}
| The Other Participants | |||
|---|---|---|---|
| If less than 4 people choose Option B | If 4 or more people choose Option B | ||
| You | Option A | 8 ECU | 8 ECU |
| Option B | 2 ECU | 24 ECU |
Your group consist of 6 people: Mustafa, Zeynep, Ahmet, Emine, Elif, and Ayşe.
You are Elif.
Please try to guess your group member's choice. If your estimations are correct, you will earn 2 ECU (1 TL) for each correct guess.
{{formfields}} {{ next_button }} {{ endblock }}


--- title: South Staffordshire and Shropshire Healthcare NHS Foundation Trust layout: gb ---
| Resource | Fetch | Format | Columns | Data | Valid | Entries | Oldest | Latest | Total (GBP) | |
|---|---|---|---|---|---|---|---|---|---|---|
| Spend over £25,000 South Staffordshire and Shropshire Healthcare NHS Foundation Trust | ||||||||||
| 2010 April - September | ✔ | ✘ | ✘ | ✘ | ✘ | 0 | ||||
| 2011 November | ✘ | ✘ | ✘ | ✘ | ✘ | 0 | ||||
| 2011 September | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2011 May | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2010 December | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2011 June | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2011 December | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2010 November | ✘ | ✘ | ✘ | ✘ | ✘ | 0 | ||||
| 2011 August | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2011 January | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2012 February | ✔ | ✔ | ✔ | ✔ | ✔ | 25 | 2012-02-02 | 2012-02-29 | 3193172.59 | |
| 2011 July | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2010 October | ✔ | ✔ | ✔ | ✔ | ✔ | 26 | 2010-10-04 | 2010-10-31 | 2130849.03 | |
| 2011 October | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2011 March | ✔ | ✔ | ✔ | ✔ | ✔ | 41 | 2011-03-04 | 2011-03-31 | 6512326.51 | |
| 2011 February | ✔ | ✔ | ✔ | ✔ | ✘ | 0 | ||||
| 2012 January | ✔ | ✔ | ✔ | ✔ | ✔ | 28 | 2012-01-05 | 2012-01-31 | 5103881.07 | |
| 2011 April | ✔ | ✔ | ✔ | ✔ | ✔ | 29 | 2011-04-05 | 2011-04-28 | 2318292.43 |
| Resource/Stage | Error | |
| 2010 April - September | ||
| extract | HTML file detected |


All folding packages include folding, putting away and hanging of already washed and dried clothes.
All Ironing garments must be clean and be 96% cotton and 67% polyster or greater.
A folding package must be purchased with this package and A is Carte ironing item
(Lightly ironed)
All ironing items must be created than 96% cotton. A folding package must be purchased with this package
(Lightly ironed)
All ironing items must be created than 96% cotton. A folding package must be purchased with this package
Do you have a folding preference and will there be anything off limits? If so, please remove it before we begin service or specify details below.
Please set aside the clothing you want to be hung and notify your Cesta Laundress. Have a specific instructions, please detail below.
Please note that you are expected to provide your own hangers
Please set aside and notify your Laundress of any delicate garments and or air dry only garments. Have specific washing instructions, and or how you want your clothes separated, please detail below.
Please note that you are expected to provide your own hangers


Mitchell leads Santa Clara past Cal Poly 77-63
by The Associated PressSANTA CLARA, Calif. (AP) — DJ Mitchell had 18 points as Santa Clara defeated Cal Poly 77-63 on Friday night.
The Broncos led 33-26 at halftime, pushed their lead to double-digits early in the second half and maintained at least a 10-point advantage throughout most of the final period.
Guglielmo Caruso and Tahj Eaddy added 15 points each for the Broncos. Caruso also had 10 rebounds for the Broncos.
Josip Vrankic had 14 points for Santa Clara (2-0).
Junior Ballard had 17 points for the Mustangs (0-1). Kyle Colvin added 11 points and seven rebounds. Keith Smith had seven rebounds.
Santa Clara had the edge in points of turnovers (17-10) and fast break points (19-5).
Santa Clara faces Washington State at home on Tuesday. Cal Poly faces North Dakota State on the road on Monday.
___
For more AP college basketball coverage: https://apnews.com/Collegebasketball and http://twitter.com/AP_Top25
___
This was generated by Automated Insights, http://www.automatedinsights.com/ap, using data from STATS LLC, https://www.stats.com
The Associated Press


Disclaimer
Grown out of a personal script, this calculator tries to tell you the amount of taxes you have to pay when you order something online and import it to Switzerland. It is entirely possible that this tool is wrong for many reasons, so there is no guarantee that the shown price is actually what you'll pay.
Variables
Result
🥳 Yay, looks like you do not have to pay import taxes!
Your total value of goods (price + shipping) is 0.00,
which does not exceed 0.00 limit.


|
|
|
|
|
|
|
BIRTHRATE
AND MORTALITY : Fertility
and Mortality in the United States, 1800-1980
Fertility and Mortality:
Birthratea
|
|
Year
|
White
|
Blackb
|
|
1800
|
55.0
|
|
|
1810
|
54.3
|
|
|
1820
|
52.8
|
|
|
1830
|
51.4
|
|
|
1840
|
48.3
|
|
|
1850
|
43.3
|
58.6c
|
|
1860
|
41.4
|
55.0d
|
|
1870
|
38.3
|
55.4e
|
|
1880
|
35.2
|
51.9f
|
|
1890
|
31.5
|
48.1
|
|
1900
|
30.1
|
44.4
|
|
1910
|
29.2
|
38.5
|
|
1920
|
26.9
|
35.0
|
|
1930
|
20.6
|
27.5
|
|
1940
|
18.6
|
26.7
|
|
1950
|
23.0
|
33.3
|
|
1960
|
22.7
|
32.1
|
|
1970
|
17.4
|
25.1
|
|
1980
|
14.9
|
22.1
|
a. Births per 1000 population per annum.
b. Black and other population for 1920 and later.
c. Average for 1850-1859.
d. Average for 1860-1869.
e. Average for 1870-1879.
f. Average for 1880-1884.
Sources: U.S. Bureau of the Census, Historical Statistics
of the United States (U.S. Government Printing Office, 1975); U.S.
Bureau of the Census, Statistical Abstract of the United States, 1988
(U.S. Government Printing Office, 1987); Ansley J. Coale and Melvin
Zelnick, New Estimates of Fertility and Population in the United States
(Princeton University Press, 1963); Ansley J. Coale and Norfleet W. Rives,
"A Statistical Reconstruction of the Black Population of the United
States, 1880-1970: Estimates of True Numbers by Age and Sex, Birth Rates,
and Total Fertility," Population Index 39, no. 1 (Jan. 1973):
3-36; Michael R. Haines, "The Use of Model Life Tables to Estimate
Mortality for the United States in the Late Nineteenth Century," Demography
16, no. 2 (May 1979): 289-312.
|


26 June 1997
Disease Outbreak Reported
Two more deaths from acute viral myocarditits occurred on 24 June bringing the total number of deaths to 29, all in children aged from 5 months to 6 years. A total of over 600 children has been admitted to the observation wards in hospitals in Sarawak State and 66 remained under observation on 26 June. The number of cases being admitted to hospital for observation has declined since 20 June.
Teams from WHO and the Centers for Disease Control and Prevention are working with the Ministry of Health and national laboratories to establish the cause of the outbreak which may be an enterovirus. Laboratory investigations on specimens from fatal cases of myocarditis and from cases of hand, foot and mouth disease have been collected for virus isolation in tissue culture, for PCR and other techniques. Preliminary results from the virological studies should be available shortly.


Piyush Chauhan
Technical Lead
Shivansh Shukla
Technical Lead
Shreyansh Anand
Design Lead
Harsh Jindal
Lead
(Web Department)
Bhumika Shivani
Lead
(Web Department)
Pranay Kumar Gupta
Lead
(Web Department)
Shashwat Mahajan
Lead
(Web Department)
Amartya Mondal
Lead
(Mobile Society)
Somenath Sarkar
Lead
(Mobile Society)
Anubhav Jangra
Lead
(Machine Learning)
Joshika
Lead
(Machine Learning)
Hit Vardhan
Lead
(Blockchain and Cryptocurrency)
Pritam Singh
Lead
(Blockchain and Cryptocurrency)
Arya Das
Lead
(IoT Department)
Pranshu Kapri
Lead
(IoT Department)
Akash Das
Lead
(IoT Department)
Deepanjan Datta
Lead
(Cloud and API Department)
Ritwiz Sinha
Lead
(Cloud and API Department)
V S Subhang
Lead
(Cloud and API Department)
Abhipray Singh
Lead
(Aviation Society)
Nischal A
Lead
(Aviation Society)
Shreya Sinha
Female Representative


Tab Memory Purge
title :
url :
If you are clicked on this page, this page is jumped to the page of the url.


Have an account already? Click the button below to sign up or log in.
By age 40, about 50% of the population will have or have had a mental illness.
Suicide accounts for 24% of all deaths among 15-24 year olds and 16% among 25-44 year olds.
The mortality rate due to suicide among men is four times the rate among women.
Once depression is recognized, help can make a difference for 80% of people who are affected, allowing them to get back to their regular activities.
It can be hard to talk to people about how you feel. You may be worried that they won't take your feelings seriously. You may also be worried about what will happen after you tell them your problems. If you don't talk about your problems, you may find your pent-up tensions or feelings burst out in a way that is embarrassing or inappropriate. You might also find that things may get worse if you don’t try to get on top of them straight away.
Learning that it's okay to talk about our problems can feel a bit like a trip to the dentist. You know that the discomfort will stop once you get the tooth fixed, but you don't want to go though the process because it hurts too. And sometimes, with emotional issues, you may be embarrassed to share what's really going on for you. That's why it's so important to talk with someone who is comforting and nonjudgmental.
You may think that you are alone in this world, but in reality many people are suffering from the same problems you are. Meet these people, talk to these people and help each other overcome their problems in life.
If you think your life has no value, you are beyond wrong. There are many people in this world that need you and you don't even know. Help others and help yourself by exploring your options with other people on our platform. Everyone reaches a lowpoint in their life, it's important that we learn from these experiences and help others who are experiencing the same things.


BLUE RAIN
Play games
Learn a new language
Escape rooms
Philosophical thoughts
Contact us
First Name
Last Name
Country
I
Canada
USA
Subject


In the spirit of ideas worth spreading, TEDx is a program of local, self-organized events that bring people together to share a TED-like experience. At a TEDx event, TED Talks video and live speakers combine to spark deep discussion and connection. These local, self-organized events are branded TEDx, where x = independently organized TED event. The TED Conference provides general guidance for the TEDx program, but individual TEDx events are self-organized. (Subject to certain rules and regulations.)
TED is a nonprofit organization devoted to Ideas Worth Spreading. Started as a four-day conference in California 30 years ago, TED has grown to support its mission with multiple initiatives. The two annual TED Conferences invite the world's leading thinkers and doers to speak for 18 minutes or less. Many of these talks are then made available, free, at TED.com. TED speakers have included Bill Gates, Jane Goodall, Elizabeth Gilbert, Sir Richard Branson, Nandan Nilekani, Philippe Starck, Ngozi Okonjo-Iweala, Sal Khan and Daniel Kahneman.
The annual TED Conference takes place each spring in Vancouver, British Columbia. TED's media initiatives include TED.com, where new TED Talks are posted daily; the Open Translation Project, which provides subtitles and interactive transcripts as well as translations from volunteers worldwide; the educational initiative TED-Ed. TED has established the annual TED Prize, where exceptional individuals with a wish to change the world get help translating their wishes into action; TEDx, which supports individuals or groups in hosting local, self- organized TED-style events around the world, and the TED Fellows program, helping world-changing innovators from around the globe to amplify the impact of their remarkable projects and activities.
Design Team- Gilbert, Manas, Prachin, Neha, Shivam, Mehak, and Sahithi
Communications Team- Rohan, Riddhima,and Sahithi
Masters of Ceremonies - Anubhav, Riddhima, Shreya, and Gaurav
Art Team- Shivam, Prachin, Yagyata, Raj, Avneesh, and Mehak
Our Guides- Mr Sanjay Punjabi and Ms Gagan Brar


The second annual Science Fiction Festival will come to the Arlington Planetarium March 18–20. Go here to find out more and to make reservations, which are highly recommended for this popular event.
Here are a few notes on what we are planning for the weekend:
On Friday evening we are showing a science fiction mini film festival, including the Arlington premiere of two short full-dome films by artist Diana Reichenbach and other short subjects.
On Sunday afternoon come see a panel discussion on “Predicting the Future: How Well Does Speculative Fiction Anticipate Future Technology?” Science fiction experts will ponder the questions: How accurate will the predictions of today's science fiction turn out to be? How has it fared in the past?
Our second show on Sunday will be the Arlington premiere of the European Southern Observatory’s new full dome film, “From Earth to the Universe.” In 30 minutes this film will treat the history of astronomy and the capabilities of today’s most advanced telescopes.
Between Sunday’s presentations there will be an opportunity for some hands-on mathematics: make your own hexaflexagon!
At last year’s Science Fiction Festival, we were surprised by several visitors from other galaxies. We don’t know exactly what’s in store for us this year, but it’s bound to be strange and memorable.
To receive advance notice of Friends of the Planetarium events and to help support the Planetarium and make it possible for us to keep putting together our special weekends, please consider joining.


Tools to determine DNA profile Weight of Evidence. For further information see the 'likeLTD' guide provided, Balding, D.J. (2013) <doi:10.1073/pnas.1219739110>, or Steele, C.D. et al. (2016) <doi:10.1515/sagmb-2016-0038>.
| Version: | 6.3.0 |
| Depends: | R (≥ 2.10), DEoptim, ggplot2, gtools, rtf |
| Imports: | gdata, tools, tcltk |
| Suggests: | svUnit, scales |
| Published: | 2018-02-09 |
| Author: | David Balding, Adrian Timpson, Christopher Steele, Mayeul d'Avezac, James Hetherington. |
| Maintainer: | Christopher Steele <c.steele.11 at ucl.ac.uk> |
| License: | GPL-3 |
| URL: | https://sites.google.com/site/baldingstatisticalgenetics/ |
| NeedsCompilation: | yes |
| Citation: | likeLTD citation info |
| CRAN checks: | likeLTD results |
| Reference manual: | likeLTD.pdf |
| Vignettes: |
Using the likeLTD peak heights model |
| Package source: | likeLTD_6.3.0.tar.gz |
| Windows binaries: | r-devel: likeLTD_6.3.0.zip, r-release: likeLTD_6.3.0.zip, r-oldrel: likeLTD_6.3.0.zip |
| OS X binaries: | r-release: likeLTD_6.3.0.tgz, r-oldrel: likeLTD_6.3.0.tgz |
| Old sources: | likeLTD archive |
Please use the canonical form https://CRAN.R-project.org/package=likeLTD to link to this page.


aaaaaaa
bbbbbbb
ccccccc
ddddddd
eeeeeee
fffffff
ggggggg
hhhhhhh
iiiiiii
jjjjjjj
kkkkkkk
lllllll
mmmmmmm
nnnnnnn
ooooooo
ppppppp
qqqqqqq
rrrrrrr
sssssss
ttttttt
uuuuuuu
vvvvvvv
wwwwwww
xxxxxxx
yyyyyyy
zzzzzzz
aaaaaaa
bbbbbbb
ccccccc
ddddddd
eeeeeee
fffffff
ggggggg
hhhhhhh
iiiiiii
jjjjjjj
kkkkkkk
lllllll
mmmmmmm
nnnnnnn
ooooooo
ppppppp
qqqqqqq
rrrrrrr
sssssss
ttttttt
uuuuuuu
vvvvvvv
wwwwwww
xxxxxxx
yyyyyyy
zzzzzzz
aaaaaaa
bbbbbbb
ccccccc
ddddddd
eeeeeee
fffffff
ggggggg
hhhhhhh
iiiiiii
jjjjjjj
kkkkkkk
lllllll
mmmmmmm
nnnnnnn
ooooooo
ppppppp
qqqqqqq
rrrrrrr
sssssss
ttttttt
uuuuuuu
vvvvvvv
wwwwwww
xxxxxxx
yyyyyyy
zzzzzzz


An advantage of the structure provided by the combination of R, Rstudio, and knitr is that the text generating a report and the code generating the results and plots can be combined into a single file that, along with the data used, can then allow someone else to reproduce the results or modify them with new data or a new analysis approach. As an example, see the program file and resulting memo included in the ’RSessions/Session1’ directory as CONTRASTcalAOA.Rnw and CONTRASTcalAOA.pdf. I’ll use those next to give an overview of how this can be used.
Characteristics of this file to note:
Text is intermixed with R code in this file. R code ’chunks’ begin with a header line <<chunk-name>>= and end with @. Results from the R code can be incorporated into subsequent parts of the text.
The chunks provide a way to structure your program and to skip to appropriate sections of the code.
The text will have references to the R results in the form of ’\Sexpr{x}’ where x is an R variable. (Sexpr is a remnant from R’s origin in S; Sexpr = S expression.)
If a figure is generated in an R chunk, it appears in the text document after the place where the R chunk appears.
I have emphasized reproducibility and have included a section on how to use the file with other data and a table on reproducibility at the end of the memo. That table contains:
the location of the source file
the name of a zip-format archive containing all the information needed to repeat the production of the memo
the original data used. (Only the subset of the data used here is saved in the archive to keep the size of these archive files small.)
This will be the subject of a later session in this series, but the goal of facilitating reproducibility can be motivation to continue along this path.


Conference Program Invited Speakers Accepted Papers Workshops Organization Student Grants Call for Papers Call for Workshops Important Dates Documents Past Conferences


What Is Emotional Intelligence?
Emotional intelligence (EI) refers to the ability to perceive, control, and evaluate emotions. Some researchers suggest that emotional intelligence can be learned and strengthened, while others claim it's an inborn characteristic.
The ability to express and control emotions is essential, but so is the ability to understand, interpret, and respond to the emotions of others. Imagine a world in which you could not understand when a friend was feeling sad or when a co-worker was angry. Psychologists refer to this ability as emotional intelligence, and some experts even suggest that it can be more important than IQ in your overall success in life.
Components
Researchers suggest that there are four different levels of emotional intelligence including emotional perception, the ability to reason using emotions, the ability to understand emotions, and the ability to manage emotions.1
- Perceiving emotions: The first step in understanding emotions is to perceive them accurately. In many cases, this might involve understanding nonverbal signals such as body language and facial expressions.
- Reasoning with emotions: The next step involves using emotions to promote thinking and cognitive activity. Emotions help prioritize what we pay attention and react to; we respond emotionally to things that garner our attention.
- Understanding emotions:The emotions that we perceive can carry a wide variety of meanings. If someone is expressing angry emotions, the observer must interpret the cause of the person's anger and what it could mean. For example, if your boss is acting angry, it might mean that they are dissatisfied with your work, or it could be because they got a speeding ticket on their way to work that morning or that they've been fighting with their partner.
- Managing emotions: The ability to manage emotions effectively is a crucial part of emotional intelligence and the highest level. Regulating emotions and responding appropriately as well as responding to the emotions of others are all important aspects of emotional management.
The four branches of this model are arranged by complexity with the more basic processes at the lower levels and the more advanced processes at the higher levels. For example, the lowest levels involve perceiving and expressing emotion, while higher levels require greater conscious involvement and involve regulating emotions.
Impact of Emotional Intelligence
Interest in teaching and learning social and emotional intelligence has grown in recent years. Social and emotional learning (SEL) programs have become a standard part of the curriculum for many schools.
The goal of these initiatives is not only to improve health and well-being but also to help students succeed academically and prevent bullying. There are many examples of how emotional intelligence can play a role in daily life.
Thinking Before Reacting
Emotionally intelligent people know that emotions can be powerful, but also temporary. When a highly charged emotional event happens, such as becoming angry with a co-worker, the emotionally intelligent response would be to take some time before responding. This allows everyone to calm their emotions and think more rationally about all the factors surrounding the argument.
Greater Self-Awareness
Emotionally intelligent people are not only good at thinking about how other people might feel but they are also adept at understanding their own feelings. Self-awareness allows people to consider the many different factors that contribute to their emotions.
 This often involves considering how you would respond if you were in the same situation.
People who have strong emotional intelligence are able to consider the perspectives, experiences, and emotions of other people and use this information to explain why people behave the way that they do.
How to Use
Emotional intelligence can be used in many different ways in your daily life. Some different ways to practice emotional intelligence include:
- Being able to accept criticism and responsibility
- Being able to move on after making a mistake
- Being able to say no when you need to
- Being able to share your feelings with others
- Being able to solve problems in ways that work for everyone
- Having empathy for other people
- Having great listening skills
- Knowing why you do the things you do
- Not being judgemental of others
Emotional intelligence is essential for good interpersonal communication. Some experts believe that this ability is more important in determining life success than IQ alone. Fortunately, there are things that you can do to strengthen your own social and emotional intelligence.
Understanding emotions can be the key to better relationships, improved well-being, and stronger communication skills.
Tips for Improving EI
Being emotionally intelligent is important, but what steps can you take to improve your own social and emotional skills? Here are some tips.
Listen
If you want to understand what other people are feeling, the first step is to pay attention. Take the time to listen to what people are trying to tell you, both verbally and non-verbally. Body language can carry a great deal of meaning. When you sense that someone is feeling a certain way, consider the different factors that might be contributing to that emotion.
Empathize
Picking up on emotions is critical, but you also need to be able to put yourself into someone else's shoes in order to truly understand their point of view. Practice empathizing with other people. Imagine how you would feel in their situation. Such activities can help you build an emotional understanding of a specific situation as well as develop stronger emotional skills in the long-term.
Reflect
The ability to reason with emotions is an important part of emotional intelligence. Consider how your own emotions influence your decisions and behaviors. When you are thinking about how other people respond, assess the role that their emotions play.
Why is this person feeling this way? Are there any unseen factors that might be contributing to these feelings? How to your emotions differ from theirs? As you explore such questions, you may find that it becomes easier to understand the role that emotions play in how people think and behave.


This method will scroll node with id = id into view. If no node specified, then selected node will be
scrolled into view. The sidebar node is identified by the .id property.
it will search the entire sidebar including all its nested nodes. The method returns the number of nodes it removes.
If you have sidebar defined in the following way:
You can:


About Our Division
UCSD Circle K is a part of Paradise Division, one of the eight divisions in Cal-Nev-Ha (see District tab). Our current Lieutenant Governor is San Diego State University's Gerald Biando. Our division
comprises seven schools that range in location from California to Hawaii.
Paradise Clubs
- Palomar College
- Grossmont College
- California State University San Marcos
- Hawaii Pacific University
- San Diego State University
- University of California, San Diego
- University of Hawaii, Hilo
- University of Hawaii, Manoa


---
layout: portal
category: reject
tags: reject
id: 37
imgurl: https://lh5.ggpht.com/WzdIQa0MQPwomp6PldG4Lly2mLF84KwkWg8kt3t2EPi49V7YkQTSnThbcRf-f9C0cG6jIpWMZUkNOEDdgXtfrg
portalname: 寿橋
sentdate: Fri Mar 06 01:31:12 JST 2015
title: 37 - 寿橋
---
From: Ingress Operations<EMAIL_ADDRESS>Date: 2015年3月6日(金) 午前0:58
Subject: Ingress Portal Rejected: 寿橋
To: **
Thank you for your Portal submission. However, this Portal candidate does not meet the criteria required for approval.
Please refer to New Portal Submission criteria at our Help Center for further information.


temperature threshold ice climate sea probability Greenland level exceeding Arctic sheet increase sensitivity global estimated summer rise mean thresholds Fig. policy probabilities temperatures used {border-style (i.e., TEs actual px;} #ffffff;} target PDF distribution pathways Clim response Change lower melting time tipping .–. Antarctic PDFs impact using (see Sci associated loss potential assumed different function range study However, IAM ICA-RUS Table century density emission higher increases Levermann based change coastal confidence estimation framework ranges sea-ice state years °C, (.) (.)% (Fig. (IPCC ./pnas. Acad Lenton Natl Proc USA assessment crossing domain elements emissions equilibrium estimate exposure future ice-free impacts linear px; set sheet. studies uncertainty {font-family BaU Climate Mengel Nat Ocean Therefore, Winkelmann considered following font-size integrated inundated major model noted projections scenarios shown simulations temperature. thermal uniform °C. ./nclimate ./s--- Accessed Aug Environmental SLR areas case century, choices contribution did double; end given glaciers greater high ice-sheet indicates joint large obtain passing population preindustrial present probabilistic relatively research threshold, threshold. warming year (Lenton (Step Abe-Ouchi Appendix Figure Future Screen Takahashi Williamson addition, analysis assumption assumptions border-color border-width bound computed critical does exceed including indicate lines nearly obtained parameters period points result, results risk scenario sheet, solid; strategies temperature, trends values {font-style {font-weight (Arctic (Su (e.g., (i) (ii) Bank Elevation Figs. GDP Global Holland Kanae Kriegler Lontzek National Probability Report Res Research Robinson Schellnhuber TEs. World [], according area assessments assuming blue bold changes choice considering correspond courier; described em; example, exceeded expansion fixed functions goal highest ice. incorporation increase, increases. indicated long-term maximum millennial minimum performed population, potentially presented pt;} reaches regard regression relative represent respectively. risks sensitivities setting shortest showed shows similar special study, suggested support surface targets thresholds, timescale transition upper various


My name is Saijo George, I am an SEO Consultant from Melbourne, Australia. You can also usually find me at the local SEO Meetup in Melbourne. Big thanks to these guys for making this possible: Mukesh, the idea for this site from TheStocks.im, hosting by Git Pages and the Xenon Bootstrap template by Laborator. Our privacy policy.


To preface my report I have tripped on ayahuasca 2 times before to varying degrees but this experience was the only time I feel I obtained the full medicinal value of the drug.
[time is measured in minutes]
T=0: I swallow the tea in two large gulps, it tastes very bitter so I mask it by sucking a lemon. I am in a dark room with my brother, who is much more experienced than I am with the drug, he sips it over the course of a half hour.
T=10: As always when I take the drug my stomach becomes immediately queasy. For some reason I am convinced I will not trip.
T=20: To soothe the come-up I get the guitar out and begin to play music, almost immediately the notes become 3-dimensional and immerse me. I become the music, my brother becomes the music.
T=30: My brother has finished his dose and is beginning to feel it, rather, I am beginning to feel as though he can feel it. I play the guitar more, singing my favorite songs to play (Karma Police, Styrofoam Boots, Third Planet, and Float On. Yeah, lots of Modest Mouse). I feel like the music could be so much more if my brother would sing along and as soon as the thought crosses my mind he begins singing.
T=45: The body feeling is peaking, I know the purge will come soon so I leave my brother in the room and walk downstairs. Sitting on the sofa I begin to feel awful, my hands begin to swell, my nose begins to run and my mouth starts watering: I am about to purge myself so I move to the toilet. I sit there, knowing that soon it will be over and this horrible pain across my whole body will disappear and the world will be new once again. I wait, but nothing comes. The pain is excruciating and I am sweating and sobbing, wishing for it to leave but it won't yet.
T=60: My muscles, joints, eyes, everything I feel with utmost detail, however, it is all pain. No matter what I do I cannot force the purge. I am beginning to think that this is death, that my body is dying and that my spirit is going to force its way out and into the ethereal world, leaving me like this forever. Then it comes: it is forgiving. As vomit wrenches my body I am literally thrown forward as every last bit of substance from my stomach is purged.  I still feel horrible. I cry more and feel old uncried tears finally escape. I am finished with this part, now it is time for the rest.
I begin to clean up and evacuate my bladder and bowels. I have been given the ability to move muscles I didnt know I could and am positive that all the waste in my body is gone. I feel absolutely pure and as I clean the residual vomit and mucus from my face I am embraced by the world. All of a sudden the experience has changed from the most horrible sickness of my life to the most peaceful feeling I have ever had. I walk outside and can do nothing but look up at the night sky and cry with joy.
T=100: Two of my friends have joined me and I am being unusually positive. I decide that it is ok to drink one beer as it just feels right. After halfway I feel the alcohol and am done drinking (which is very odd on account of I usually drink 5 beers to feel the alcohol). I think to myself that I would like to smoke some herb and as soon as I have the thought my brother comes down and says 'It's in my jacket pocket'.
T=120: The marijuana taste so good, it feels like I am inhaling healing smoke into my lungs and I don't feel so much 'stoned' as pleasant and more comfortable.
The rest of the experience was uneventful and irritating. As with the other ayahuasca experiences I have done the pleasantness fades and I start having internal dialogues which become VERY irritating after awhile because it turns from conversation to thoughts like 'Now I am wishing that I wasn't thinking about everything I'm doing' and shortly thereafter 'Oh I did it again, I wish I would stop' and so on until I am so fed up with myself that I just want to sleep, which I did.
In retrospect it was positive overall, but will be my last experience as I cannot handle the internal dialogue anymore.
 Literally everything that happened to me that month came forward in my experience. I had planned for it weeks in advance and still don't think I was fully prepared.
With that I will let you go!!
good luck and safe trips
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Deployments
- List Deployments
- Create a Deployment
- Update a Deployment
- List Deployment Statuses
- Create a Deployment Status
Deployments are a request for a specific ref (branch, SHA, tag) to be deployed. GitHub then dispatches deployment events that external services can listen for and act on. This enables developers and organizations to build loosely-coupled tooling around deployments, without having to worry about implementation details of delivering different types of applications (e.g., web, native).
Deployment Statuses allow external services to mark deployments with a
'success', 'failure', 'error', or 'pending' state, which can then be consumed
by any system listening for deployment_status
events.
Deployment Statuses can also include an optional description
and target_url
, and
we highly recommend providing them as they make deployment statuses much more
useful. The target_url
would be the full URL to the deployment output, and
the description
would be the high level summary of what happened with the
deployment.
Deployments and Deployment Statuses both have associated repository events when they're created. This allows webhooks and 3rd party integrations to respond to deployment requests as well as update the status of a deployment as progress is made.
 It's up to your 3rd party integration to interact with deployment events. This allows for GitHub integrations as well as running your own systems depending on your use case. Multiple systems can listen for deployment events, and it's up to each of those systems to decide whether or not they're responsible for pushing the code out to your servers, building native code, etc.
Note that the repo_deployment
OAuth scope grants
targeted access to Deployments and Deployment Statuses without
granting access to repository code, while the repo
scope grants permission to code
as well.
List Deployments
Simple filtering of deployments is available via query parameters:
GET /repos/:owner/:repo/deployments
| Name | Type | Description |
|---|---|---|
sha |
string |
The SHA that was recorded at creation time. Default: none
|
ref |
string |
The name of the ref. This can be a branch, tag, or SHA. Default: none
|
task |
string |
The name of the task for the deployment. e.g. deploy or deploy:migrations . Default: none
|
environment |
string |
The name of the environment that was deployed to. e.g. staging or production . Default: none
|
Response
Status: 200 OK
Link: <https://api.github.com/resource?page=2>; rel="next",
<https://api.github.com/resource?page=5>; rel="last"
[
{
"url": "https://api.github.com/repos/octocat/example/deployments/1",
"id": 1,
"sha": "a84d88e7554fc1fa21bcbc4efae3c782a70d2b9d",
"ref": "master",
"task": "deploy",
"payload": {
"task": "deploy:migrate"
},
"environment": "production",
"description": "Deploy request from hubot",
"creator": {
"login": "octocat",
"id": 1,
"avatar_url": "https://github.com/images/error/octocat_happy.gif",
"gravatar_id": "",
"url": "https://api.github.com/users/octocat",
"html_url": "https://github.com/octocat",
"followers_url": "https://api.github.com/users/octocat/followers",
"following_url": "https://api.github.com/users/octocat/following{/other_user}",
"gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
"starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
"subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
"organizations_url": "https://api.github.com/users/octocat/orgs",
"repos_url": "https://api.github.com/users/octocat/repos",
"events_url": "https://api.github.com/users/octocat/events{/privacy}",
"received_events_url": "https://api.github.com/users/octocat/received_events",
"type": "User",
"site_admin": false
},
"created_at": "2012-07-20T01:19:13Z",
"updated_at": "2012-07-20T01:19:13Z",
"statuses_url": "https://api.github.com/repos/octocat/example/deployments/1/statuses",
"repository_url": "https://api.github.com/repos/octocat/example"
}
]
Create a Deployment
Deployments offer a few configurable parameters with sane defaults.
The ref
parameter can be any named branch, tag, or SHA. At GitHub we often
deploy branches and verify them before we merge a pull request.
The environment
parameter allows deployments to be issued to different
runtime environments. Teams often have multiple environments for verifying
their applications, like 'production', 'staging', and 'qa'. This allows for
easy tracking of which environments had deployments requested. The default
environment is 'production'.
The auto_merge
parameter is used to ensure that the requested ref is not
behind the repository's default branch. If the ref is behind the default
branch for the repository, we will attempt to merge it for you. If the merge
succeeds, the API will return a successful merge commit. If merge conflicts
prevent the merge from succeeding, the API will return a failure response.
By default, commit statuses for every submitted context
must be in a 'success' state. The required_contexts
parameter allows you to
specify a subset of contexts that must be "success", or to specify contexts
that have not yet been submitted.  If you do not require any contexts or create any commit statuses,
the deployment will always succeed.
The payload
parameter is available for any extra information that a
deployment system might need. It is a JSON text field that will be passed on
when a deployment event is dispatched.
The task
parameter is used by the deployment system to allow different
execution paths. In the web world this might be 'deploy:migrations' to run
schema changes on the system. In the compiled world this could be a flag to
compile an application with debugging enabled.
Users with repo
or repo_deployment
scopes can create a deployment for a given ref:
POST /repos/:owner/:repo/deployments
Parameters
| Name | Type | Description |
|---|---|---|
ref |
string |
Required. The ref to deploy. This can be a branch, tag, or SHA. |
task |
string |
Optional parameter to specify a task to execute, e.g. deploy or deploy:migrations . Default: deploy
|
auto_merge |
boolean |
Optional parameter to merge the default branch into the requested ref if it is behind the default branch. Default: true
|
required_contexts |
Array |
Optional array of status contexts verified against commit status checks. If this parameter is omitted from the parameters then all unique contexts will be verified before a deployment is created. To bypass checking entirely pass an empty array. Defaults to all unique contexts. |
payload |
string |
Optional JSON payload with extra information about the deployment. Default: ""
|
environment |
string |
Optional name for the target deployment environment (e.g., production, staging, qa). Default: "production"
|
description |
string |
Optional short description. Default: ""
|
transient_environment |
boolean |
Optionally specifies if the given environment is specific to the deployment and will no longer exist at some point in the future. Default: false This parameter requires a custom media type to be specified. Please see more in the alert below.
|
production_environment |
boolean |
Optionally specifies if the given environment is one that end-users directly interact with. Default: true when environment is "production" and false otherwise. This parameter requires a custom media type to be specified. Please see more in the alert below.
|
The new transient_environment
and production_environment
parameters are currently available for developers to preview. During the preview period, the API may change without advance notice. Please see the blog post for full details.
To access the API during the preview period, you must provide a custom media type in the Accept
header:
application/vnd.github.ant-man-preview+json
Simple Example
A simple example putting the user and room into the payload to notify back to chat networks.
{
"ref": "topic-branch",
"payload": "{\"user\":\"atmos\",\"room_id\":123456}",
"description": "Deploying my sweet branch"
}
Successful response
Status: 201 Created
Location: https://api.github.com/repos/octocat/example/deployments/1
{
"url": "https://api.github.com/repos/octocat/example/deployments/1",
"id": 1,
"sha": "a84d88e7554fc1fa21bcbc4efae3c782a70d2b9d",
"ref": "master",
"task": "deploy",
"payload": {
"task": "deploy:migrate"
},
"environment": "production",
"description": "Deploy request from hubot",
"creator": {
"login": "octocat",
"id": 1,
"avatar_url": "https://github.com/images/error/octocat_happy.gif",
"gravatar_id": "",
"url": "https://api.github.com/users/octocat",
"html_url": "https://github.com/octocat",
"followers_url": "https://api.github.com/users/octocat/followers",
"following_url": "https://api.github.com/users/octocat/following{/other_user}",
"gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
"starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
"subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
"organizations_url": "https://api.github.com/users/octocat/orgs",
"repos_url": "https://api.github.com/users/octocat/repos",
"events_url": "https://api.github.com/users/octocat/events{/privacy}",
"received_events_url": "https://api.github.com/users/octocat/received_events",
"type": "User",
"site_admin": false
},
"created_at": "2012-07-20T01:19:13Z",
"updated_at": "2012-07-20T01:19:13Z",
"statuses_url": "https://api.github.com/repos/octocat/example/deployments/1/statuses",
"repository_url": "https://api.github.com/repos/octocat/example"
}
Advanced Example
A more advanced example specifying required commit statuses and bypassing auto-merging.
{
"ref": "topic-branch",
"auto_merge": false,
"payload": "{\"user\":\"atmos\",\"room_id\":123456}",
"description": "Deploying my sweet branch",
"required_contexts": [
"ci/janky",
"security/brakeman"
]
}
Successful response
Status: 201 Created
Location: https://api.github.com/repos/octocat/example/deployments/1
{
"url": "https://api.github.com/repos/octocat/example/deployments/1",
"id": 1,
"sha": "a84d88e7554fc1fa21bcbc4efae3c782a70d2b9d",
"ref": "master",
"task": "deploy",
"payload": {
"task": "deploy:migrate"
},
"environment": "production",
"description": "Deploy request from hubot",
"creator": {
"login": "octocat",
"id": 1,
"avatar_url": "https://github.com/images/error/octocat_happy.gif",
"gravatar_id": "",
"url": "https://api.github.com/users/octocat",
"html_url": "https://github.com/octocat",
"followers_url": "https://api.github.com/users/octocat/followers",
"following_url": "https://api.github.com/users/octocat/following{/other_user}",
"gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
"starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
"subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
"organizations_url": "https://api.github.com/users/octocat/orgs",
"repos_url": "https://api.github.com/users/octocat/repos",
"events_url": "https://api.github.com/users/octocat/events{/privacy}",
"received_events_url": "https://api.github.com/users/octocat/received_events",
"type": "User",
"site_admin": false
},
"created_at": "2012-07-20T01:19:13Z",
"updated_at": "2012-07-20T01:19:13Z",
"statuses_url": "https://api.github.com/repos/octocat/example/deployments/1/statuses",
"repository_url": "https://api.github.com/repos/octocat/example"
}
Merge conflict response
This error happens when the auto_merge
option is enabled and when the default branch (in this case master
), can't be merged into the branch that's being deployed (in this case topic-branch
), due to merge conflicts.
Status: 409 Conflict
{
"message": "Conflict merging master into topic-branch"
}
Failed commit status checks
This error happens when the required_contexts
parameter indicates that one or more contexts need to have a success
status for the commit to be deployed, but one or more of the required contexts do not have a state of success
.
Status: 409 Conflict
{
"message": "Conflict: Commit status checks failed for topic-branch."
}
Update a Deployment
Once a deployment is created, it cannot be updated. Information relating to the success or failure of a deployment is handled through Deployment Statuses.
Deployment Statuses
List Deployment Statuses
Users with pull access can view deployment statuses for a deployment:
GET /repos/:owner/:repo/deployments/:id/statuses
Parameters
| Name | Type | Description |
|---|---|---|
id |
integer |
Required. The Deployment ID to list the statuses from. |
Response
Status: 200 OK
Link: <https://api.github.com/resource?page=2>; rel="next",
<https://api.github.com/resource?page=5>; rel="last"
[
{
"url": "https://api.github.com/repos/octocat/example/deployments/42/statuses/1",
"id": 1,
"state": "success",
"creator": {
"login": "octocat",
"id": 1,
"avatar_url": "https://github.com/images/error/octocat_happy.gif",
"gravatar_id": "",
"url": "https://api.github.com/users/octocat",
"html_url": "https://github.com/octocat",
"followers_url": "https://api.github.com/users/octocat/followers",
"following_url": "https://api.github.com/users/octocat/following{/other_user}",
"gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
"starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
"subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
"organizations_url": "https://api.github.com/users/octocat/orgs",
"repos_url": "https://api.github.com/users/octocat/repos",
"events_url": "https://api.github.com/users/octocat/events{/privacy}",
"received_events_url": "https://api.github.com/users/octocat/received_events",
"type": "User",
"site_admin": false
},
"description": "Deployment finished successfully.",
"target_url": "https://example.com/deployment/42/output",
"created_at": "2012-07-20T01:19:13Z",
"updated_at": "2012-07-20T01:19:13Z",
"deployment_url": "https://api.github.com/repos/octocat/example/deployments/42",
"repository_url": "https://api.github.com/repos/octocat/example"
}
]
Create a Deployment Status
Users with push access can create deployment statuses for a given deployment:
POST /repos/:owner/:repo/deployments/:id/statuses
Parameters
| Name | Type | Description |
|---|---|---|
state |
string |
Required. The state of the status. Can be one of pending , success , error , inactive , or failure The inactive state requires a custom media type to be specified. Please see more in the alert below.. |
target_url |
string |
The target URL to associate with this status. This URL should contain output to keep the user updated while the task is running or serve as historical information for what happened in the deployment. Default: ""
|
log_url |
string |
This is functionally equivalent to target_url . We will continue accept target_url to support legacy uses, but we recommend modifying this to the new name to avoid confusion. Default: "" This parameter requires a custom media type to be specified. Please see more in the alert below.
|
description |
string |
A short description of the status. Maximum length of 140 characters. Default: ""
|
environment_url |
string |
Optionally set the URL for accessing your environment. Default: "" This parameter requires a custom media type to be specified. Please see more in the alert below.
|
auto_inactive |
boolean |
Optional parameter to add a new inactive status to all non-transient, non-production environment deployments with the same repository and environment name as the created status's deployment. Default: true This parameter requires a custom media type to be specified. Please see more in the alert below.
|
The new inactive
state, rename of the target_url
parameter to log_url
and new environment_url
and auto_inactive
parameters are currently available for developers to preview. During the preview period, the API may change without advance notice. Please see the blog post for full details.
To access the API during the preview period, you must provide a custom media type in the Accept
header:
application/vnd.github.ant-man-preview+json
Example
{
"state": "success",
"target_url": "https://example.com/deployment/42/output",
"description": "Deployment finished successfully."
}
Response
Status: 201 Created
Location: https://api.github.com/repos/octocat/example/deployments/42/statuses/1
{
"url": "https://api.github.com/repos/octocat/example/deployments/42/statuses/1",
"id": 1,
"state": "success",
"creator": {
"login": "octocat",
"id": 1,
"avatar_url": "https://github.com/images/error/octocat_happy.gif",
"gravatar_id": "",
"url": "https://api.github.com/users/octocat",
"html_url": "https://github.com/octocat",
"followers_url": "https://api.github.com/users/octocat/followers",
"following_url": "https://api.github.com/users/octocat/following{/other_user}",
"gists_url": "https://api.github.com/users/octocat/gists{/gist_id}",
"starred_url": "https://api.github.com/users/octocat/starred{/owner}{/repo}",
"subscriptions_url": "https://api.github.com/users/octocat/subscriptions",
"organizations_url": "https://api.github.com/users/octocat/orgs",
"repos_url": "https://api.github.com/users/octocat/repos",
"events_url": "https://api.github.com/users/octocat/events{/privacy}",
"received_events_url": "https://api.github.com/users/octocat/received_events",
"type": "User",
"site_admin": false
},
"description": "Deployment finished successfully.",
"target_url": "https://example.com/deployment/42/output",
"created_at": "2012-07-20T01:19:13Z",
"updated_at": "2012-07-20T01:19:13Z",
"deployment_url": "https://api.github.com/repos/octocat/example/deployments/42",
"repository_url": "https://api.github.com/repos/octocat/example"
}


{% extends 'layout/base.html' %} {% load i18n %} {% load extra-tags %} {% block content %}
{% trans "Your username and password didn't match. Please try again." %}
{% trans "Your account doesn't have access to this page. To proceed, please login with an account that has access." %}


Former SABC group CEO Solly Mokoetle dies
by Riaan GroblerFormer SABC group CEO Solly Mokoetle has died.
In a statement on Friday, the public broadcaster said it had "learnt with great shock" of the passing of Mokoetle.
"He joined the SABC in 1994 as general manager and, over the years, his outstanding work ethic saw him rise through the ranks [to become] the corporation's Chief Operations Officer (COO) in 2001 until 2006.
"Mokoetle rejoined the SABC as the Group CEO in January 2010, prior to the delivery of the world's biggest football spectacle, the 2010 FIFA World Cup.
"The successful broadcast of the World Cup is testament to his commitment to fulfil the mandate of the SABC of building an informed society. Following his departure from the public service broadcaster, he joined the Department of Communications to further play an instrumental role in the development of the industry."
READ | SABC News Channel gets new editor
The SABC said Mokoetle's overall contribution to the SABC and the communication industry will continue to serve as a footprint, "particularly during this era when the broadcasting industry is drastically transforming due to technological advancements which require new policy decisions".
The SABC sent its deepest condolences to Mokoetle's family, friends and colleagues.
In June 2016, News24 reported that Mokoetle had gone missing when he left his Mount Edgecombe home for a walk, but never returned. He was later found in a Durban hospital.
Mokoetle is survived by his wife, Zola Ntuli, and their four children.


Tv Show
Application
This is my first project with CSS, HTML and Bootstraps.
Id
Name
Type
Description
Submit


WITNESS LIST
Mass Violence Prevention & Community Safety, Select Committee
November 7, 2019 - 9:00 AM
(1) Enforcement of current laws prevent transfer of firearms to felons
On:
Acuff, Cynthia (Self)
Acuff, David (Self)
Haley, Evan (Self; OHS Odessa Young Democrats High School Caucus Rep.)
Hanggi, Kristin (Permian Basin Moms Demand Action)
Hedtke, Amy (Self)
Krueger, Edna (Self)
Malone, Rachel (Gun Owners of America)
Mayberry, Aubrey (Self)
Neff, Mary (Self)
Registering, but not testifying:
On:
Haley, Rhonda (Self)
Polston, Brandon (Self)
(2) Reporting criminal history to state and federal databases
On:
Gerke, Michael (Odessa Police Department)
Griffis, Mike (Ector County Sheriff's Office)
Hanggi, Kristin (Permian Basin Moms Demand Action)
Hearn, Sklyor (DPS)
Hedtke, Amy (Self)
Herman, Seth (Midland Police Department, City of Midland, Texas)
Krueger, Edna (Self)
Mayberry, Aubrey (Self)
McCraw, Steven (Texas DPS)
Nodolf, Laura (Midland County District Attorney's Office)
Slayton, David (Office of Court Administration)
(3) Digital media/technology in collaboration law enforcement
On:
Franklin, James (Self; Come & Take It Texas)
Hanggi, Kristin (Permian Basin Moms Demand Action)
Hedtke, Amy (Self)
Krueger, Edna (Self)
Mayberry, Aubrey (Self)
Teal, Gary (Self)
(4) Workforce needs cybersecurity, mental health, law enforcement
On:
Dragun, Carmen (UTPB Student Body)
Hanggi, Kristin (Permian Basin Moms Demand Action)
1
WITNESS LIST
On:
Hedtke, Amy (Self)
Krueger, Edna (Self)
Teal, Gary (Self)
Webbs, Jacqree (UTPB Student Body)
Registering, but not testifying:
On:
Hopkins-Garcia, Sonja (Self)
(5) Extreme risk indicators used to identify potential threats
On:
Dolgener, Richard (Self)
Flores, Carlos (Self)
Haley, Evan (Self; OHS Odessa Young Democrats High School Caucus Representative)
Hanggi, Kristin (Permian Basin Moms Demand Action)
Hedtke, Amy (Self)
Krueger, Edna (Self)
Malone, Rachel (Gun Owners of America)
McCain, Brent (Self; Gun Owners of America)
McKenzie, Heather (Self)
Muri, Scott (Ector County ISD)
Neff, Mary (Self)
Novak, Robert (Self)
Roberts, Stacey (Self)
Robertson, Wesley (Self)
Teal, Gary (Self)
Wendt, Manfred (Young Conservatives of Texas)
Governor Abbott Executive Orders issue on September 5, 2019
On:
Hearn, Skylor (DPS)
McCraw, Steven (Texas DPS)
Slayton, David (Office of Court Administration)
Testimony from directly impacted by mass violence on August 31, 2019
On:
Alvarez, John (City of Odessa Fire Rescue)
Askins, Marcy (Self)
Brock, Brad (Self)
Byrne, Carla (Joe Griffith, Murder Victim)
Gerke, Michael (Odessa Police Department)
Griffis, Mike (Ector County Sheriff's Office)
Griffith, Gary (Joe Griffith, Murder Victim)
Griffith, Sharon (Joe Griffith, Murder Victim)
Herman, Seth (Midland Police Department, City of Midland, Texas)
Muri, Scott (Ector County ISD)
2
WITNESS LIST
On:
Nodolf, Laura (Midland County District Attorney's Office)
Racca, Michele (City of Odessa Public Safety Communications)
Stebbins, Rachel (Self)
Turner, David (City of Odessa)
3


Hurricane Laura
Laura is now a category 4 hurricane with winds of 140 mph as it approaches the Gulf Coast. "Unsurvivable" storm surge of up to 20' is expected. Winds are now 125 mph and it's likely to become a Cat.4 this afternoon. Storm surge could be as high as 15-20 ft. in some places. O


My name is Ryan Ellingson. I recently began transitioning to a career in web development after obtaining a degree in Chemical Engineering and working for 4 years as a process engineer in the chemical industry. Whether it be understanding and correcting a problem that resulted in a process safety incident, designing and building a new blending operation in a latex plant, or programming a cool web app from scratch, I love simultaneously using my analytical skills and creativity to solve challenging problems. Like a sculptor bringing life to a block of marble, I find there are few things in life as satisfying as taking a concept from your mind and making it a reality.
Outside of work I enjoy playing the bass, hiking, and homebrewing. In the last few years I started visiting fun parts of the country with my dad, including the Grand Canyon, Sedona, AZ, and Route 66. I also like video games, and have particularly been a fan of role-playing games like Final Fantasy, Kingdom Hearts, and Dark Souls over the years.


--- layout: page title: 'Upcoming Events' ---
{{ card_content | markdownify }}
There are currently no upcoming events. Be sure to sign up for notifications and find the Borough social media on our notifications page.


--- layout: archive title: Zulip Chat Archive permalink: /stream/113489-new-members/topic/mathlib.20dependency.html ---
I am trying to use mathlib for the first time. I successfully applied the tutorial here https://github.com/leanprover-community/mathlib/blob/master/docs/install/windows.md and also did the first steps here https://github.com/leanprover-community/mathlib/blob/master/docs/install/project.md
But when I write "import topology.basic" in a file as explained there, I get an error message in VS as
test.lean:1:0: error
file 'theory\set_theory' not found in the LEAN_PATH
test.lean:1:0: error
invalid import: theory.set_theory
could not resolve import: theory.set_theory
The mathlib files were successfully downloaded (situated in C:\Users\me\lean\alggeo\_target\deps\mathlib\src). My folder
C:\Users\me\lean\alggeo contains a file named leanpkg.path having as contents
builtin_path
path _target/deps/mathlib/src
path ./src
What needs to be done to resolve this problem? Thanks!
Did you open the C:\Users\me\lean\alggeo
folder in VS Code or just a file in it? You need to do the former, otherwise Lean will not look for dependencies in the right place.
@Jakob Scholbach Welcome!
Little Zulip hint: if you format code like this:
```lean code goes here ```
then you'll get syntax highlighting for free
@Jakob Scholbach Did you follow one of the installation tutorials? E.g. this one: https://github.com/leanprover-community/mathlib/blob/master/docs/install/windows.md ?
Where is theory.set_theory
coming from? The only place I've seen it is in another new user question like yours.
Thanks, yes I did follow the tutorial except for opening not the folder in VS, but the file. Bryan's tip helped me. Now it works.
+1 to Reid's question. It would be nice to resolve why some new users are reporting this error. Is there some error in some docs somewhere?
I saw this theory.set_theory
here https://leanprover.github.io/reference/using_lean.html#import-resolution, but the problem also arose with imports such as import topology.basic
. But again, the latter now works, so the problem is solved, thanks everyone.
Absolute imports are resolved according to the entries in the leanpkg.path file. That is, when executing import theory.set_theory, Lean looks for a file called theory/set_theory.lean in the src directories of all (transitive) dependencies as well as the current package.
This is in the Lean reference manual! It might well be the case that Lean looks for that file -- but it is not made at all clear that no such file exists in any repository we know of e.g. mathlib!
Yes, sure. Thanks.
Ha, I guess it would be helpful if that example refered to a file that actually ships with core Lean
Ooh, that doesn't make sense... because you don't need to import from core Lean
You do have to import for some stuff provided with core Lean, e.g. system.io
. You don't need to import stuff inside init
, which, admittedly, is essentially everything provided which is useful for doing math.
Last updated: Apr 24 2020 at 19:02 UTC