django-apollo Documentation
About
The best way to prove an idea is to test it. Whether you want to test a new feature in an existing application or prove an entirely new concept, django-apollo helps you quickly add a landing page to your existing Django site or create a new landing page based MVP site.
Usage
Installation
pip install django-apollo
Dependencies
In addition to Django, the following python packages are required by this package, and should be installed automatically by pip:
django-ckeditor >= 4.4
django-widget-tweaks >= 1.3
Bootstrap 3 and jQuery are also required, but because there are so many ways to add these to your project, they have not been made dependencies.
Settings
Add ‘apollo’ to your INSTALLED_APPS
Create a list of LANDING_PAGE_TEMPLATES that will be used in your landing pages. You must create at least one. Typically these will be in your site’s root template directory.
Admin Configuration
Configure your Site as appropriate.
Create a Page including key and landing template.
Add Question if needed.
Templates
The templates include a flexible layout scheme that allows you to define named blocks in your template file and type the content into the Page using the Django Admin.
Here is an example landing page template that you can include in your Django Site:
{% extends "base.html" %}
{% block content %}
<div class="jumbotron">
<div class="container">
{{ content.main|safe }}
</div>
</div>
{% include "apollo/buttons.html" %}
{% endblock %}
This assumes that you have a base.html template that defines your overall site layout and contains a content block.
Save this to a file landing1.html in your templates directory and then configure LANDING_PAGE_TEMPLATES:
LANDING_PAGE_TEMPLATES = (
('landing1.html', 'Landing Page One'),
)
Variable Page Content
Note the content.main template variable in the above example. Any Page Content that you add in the Django Admin for the Page will be added with the key into this content dictionary. You can arrange these in your landing page templates however you’d like, then easily update them in the admin site.
In addition to regular variables, you can expose a list by ending your keys with an index. For example use keys in the format ideas[0], ideas[1]… to create a template that iterates over a variable content.ideas:
{% for i in content.ideas %}
...
{% endfor %}
1 maintainer
Metadata
1 maintainer
Release files for django-apollo 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-apollo-0.2.1.tar.gz | 7.2 kB | Without provenance | Details |
Release files / django-apollo-0.2.1.tar.gz
| Download URL | django-apollo-0.2.1.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b0babf13e88db4713b3e01a1717de676ab4446e1347366a7ff0d07239ddf7855
|
|
BLAKE2b-256 checksum How to use checksums |
8b5de8d6d4bd5e94b7288376035552d67e8242da5649b28e03098342c62f4d2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-apollo 0.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
