Posted on: {{ post_date }}

``` When the Python script that builds all the web pages runs, it passes a variable called `page_title` to the template, which gets added where `{{ page_title }}` is in that template. Same with `post_date`. There are many other features of Jinja2 templates that make them an incredibly powerful tool for automatically building a website that I won't go into here, but if you're interested in learning about them, I highly recommend reading through the [Jinja2 documentation](https://jinja.palletsprojects.com/en/stable/templates/). I have also put a lot of effort into properly commenting and describing the existing template files in the [comic\_git\_engine](https://github.com/comic-git/comic_git_engine/tree/master/templates) `/templates/` directory to help anyone who wants look through them to figure out how comic\_git works. ### List of Values Available to Jinja2 Templates Assuming you want to create your own Jinja2 templates (see [Customizing Your Website](/documentation/advanced-editing/themes.md#jinja-template-format) for guidance on how to do that), it will be helpful for you to know what data the comic\_git Python script makes available to the template whenever it builds a web page. The following is a list of all variables passed to the templates as they're being built, as well as a short description of each variable. The descriptions below assume you have basic knowledge of HTML, Jinja2, and Python data structures.

Variable	Description
`template_name`	The name of the template being loaded. E.g., `comic`
`_title`	The title of the page, as defined in the [Pages] section of the `comic_info.ini` file.
`autogenerate_warning`	A bit of text added to the top of every file when it's created to warn comic creators against trying to edit the HTML files directly. Not very useful for any other purpose.
`version`	The comic_git version, e.g. 0.2.1
`comic_title`	The comic name, as defined in the [Comic Info] section of the `comic_info.ini` file.
`comic_author`	The comic author name, as defined in the [Comic Info] section of the `comic_info.ini` file.
`comic_description`	The comic description, as defined in the [Comic Info] section of the `comic_info.ini` file.
`banner_image`	The web path of the banner image at the top of your website, as defined in the [Comic Settings] section of the `comic_info.ini` file.
`theme`	The name of the current theme that's in use.
`comic_url`	The URL of the homepage of your website, e.g. `https://ryanvilbrandt.github.io/comic_git/`. See Changing Your Website URL for information about changing this value, or you can host your webcomic from a custom domain.
`base_dir`	The base directory for your comic, aka your repository name while you're hosting from a GitHub Pages URL. It is important that all URLs that reference the root directory of your website use this variable, or have the correct root directory hardcoded in the template file.
`comic_base_dir`	The web path for the current comic being built. For the main comic, this will always be the same as `{{base_dir}}`, but for extra comics, the extra comic name will be added. e.g. `/{{base_dir}}/extra_comic`
`content_base_dir`	The web path where the your_content files are stored for the current comic being built. For the main comic, this will always be `/{(base_dir)}/your_content`, but for extra comics, the extra comic name will be added. e.g. `/base_dir/your_content/extra_comic`
`links`	The list of links that make up the Links Bar on your website, partially defined by the [Links Bar] section of the comic_info.ini file. This is a list of dictionaries, each with the format `{"name": "<link name>", "url": "<link url>"}`
`use_thumbnails`	The boolean value of the Use thumbnails option, as defined in the [Archive] section of the `comic_info.ini` file.
`storylines`	A dictionary of all the comics in the archive, grouped by their Storyline value as defined in their `info.ini` files. Any comics without a Storyline value are put into the "Uncategorized" storyline. The dictionary has the format `{"<storyline>": [<comic_dict>, <comic_dict>, <comic_dict>, ...]}`, and each comic is a dictionary of all the values comic_git needs to build a comic page, and then some. See the next table for a description of that.
`home_page_text`	The text contained in the `/your_content/home_page.txt` file. It is used by the default `index.tpl` file provided with comic_git.
`google_analytics_id`	Your Google Analytics Tracking ID, as defined in the [Google Analytics] section of the `comic_info.ini` file. If it's not defined, this value will be an empty string.
`scheduled_post_count`	The number of comic pages you have uploaded that have Post Dates set in the future, so web pages for those comics have not been built yet. Useful for teasing your audience with extra pages. This number will always be 0 if you have the `publish_all_comics` command line argument set to `True`.
`extra_comics`	A dictionary of all the extra comics defined for your site. The keys are the extra comic names, and the values are lists of the comic_data_dicts for that particular extra comic.
`use_images_in_navigation_bar`	The boolean value of the "Use images" option, as defined in the [Navigation] section of the `comic_info.ini` file.
`navigation_bar_above_comic`	The boolean value of the "Above comic" option, as defined in the [Navigation] section of the `comic_info.ini` file.
`navigation_bar_below_comic`	The boolean value of the "Below comic" option, as defined in the [Navigation] section of the `comic_info.ini` file.
`navigation_bar_below_blurb`	The boolean value of the "Below blurb" option, as defined in the [Navigation] section of the `comic_info.ini` file.
`enable_webring`	True if the Webring feature is enabled. False otherwise. See below for more variables related to the Webring feature.
`social_media`	A dictionary of OGP attributes and what values should be applied to each attribute. See the documentation on Social Media Previews for more details.

If the [Webring](/documentation/expert-editing/webring.md) feature is enabled, the following variables may also be made available, depending on your chosen config options. See the feature description for more information about webrings and what these variables do. | Variable | Description | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `webring_label` | The `label` of the webring, as returned by the endpoint. | | `webring_home` | If a `home` is defined, this will be a [dictionary](https://comic-git.gitbook.io/documentation/expert-editing/webring#comic-dictionary) of values as provided by the endpoint. | | `show_all_members` | Matches the value of the "Show all members" config option. Default False. | | `webring_members` | A list of [dictionaries](https://comic-git.gitbook.io/documentation/expert-editing/webring#comic-dictionary), one for each member of the webring, as returned by the endpoint. | | `webring_prev` | A [dictionary](https://comic-git.gitbook.io/documentation/expert-editing/webring#comic-dictionary) of values for the "previous" webring link, as returned by the endpoint. | | `webring_next` | A [dictionary](https://comic-git.gitbook.io/documentation/expert-editing/webring#comic-dictionary) of values for the "next" webring link, as returned by the endpoint. | In addition to the above information, the information for the most recent comic page is also passed to every template as it's built. The values below are specific to that comic page, and can be used for things like creating a landing page that shows the first comic image or even just the title and post date. This is also the same data provided in each `comic_dict` object in the `storylines` variable, described above.

Variable	Description
`page_name`	The unique identifier for the given comic page. This matches the name of the folder the comic is in, and the value in the URL for that comic page, e.g. `001` in `https://ryanvilbrandt.github.io/comic_git/comic/001/`
`comic_paths`	A list of the image filepaths for each comic. Each path is in the format `your_content/comics/<page_name>/`.
`thumbnail_path`	The path to find the thumbnail of the comic page, if it exists.
`escaped_alt_text`	The alt text of the comic, as defined in the comic's `info.ini` file, with all nonstandard characters replaced with HTML escape codes.
`first_id`	The `page_name` of the first comic on your site, sorted chronologically.
`previous_id`	The `page_name` of the previous comic.
`current_id`	The `page_name` of the current comic.
`next_id`	The `page_name` of the next comic.
`last_id`	The `page_name` of the latest comic.
`page_title`	The title of the comic, as defined in the comic's `info.ini` file.
`_post_date`	The post date of the comic, as defined in the comic's `info.ini` file.
`archive_post_date`	The post date of the comic, but formatted to match the date format in the [Archive] section of the `comic_info.ini` file.
`_storyline`	The storyline of the comic, as defined in the comic's `info.ini` file. If storyline is not defined, this will be `None`.
`_characters`	A list of the comic's Characters tags, as defined in the comic's `info.ini` file.
`_tags`	A list of the comic's Tags, as defined in the comic's `info.ini` file.
`post_html`	The contents of the `post.txt` file for the current comic, after being run through a Markdown parser to make it pure HTML.
`transcripts`	A dictionary of the transcripts for this comic, of the format `{{"<language>": "<transcript text>"}}`.
`_on_comic_click`	The value provided by the `On comic click` setting in your `Comic settings` section of your comic_info.ini file.

Any additional values found in the info.ini file for a particular comic will also be included in the Jinja variables. The names of these values will have all punctuation and spaces replaces with underscores, and an underscore will be prepended to the name of the value. E.g., `Inker's Home Address` will become `_inker_s_home_address` If you want to add your own custom variables to the list of global variables, you can! See `extra_global_values` in [Code Hooks](/documentation/expert-editing/code-hooks.md) for instructions. ## Adding Collaborators to your Repository When you create your own comic\_git site for the first time, you will be the only one who can edit it at first. And if you make a private repository, you'll be the only one who will even be able to see it. If you want someone else to help you with your site, or even just to look at your GitHub Actions to help figure out why your build might have broken, you will likely need to add them as a "collaborator". To do this, go to your Settings tab in your repository

Then click on Collaborators in the sidebar

GitHub may ask you to sign back in. After that's done, you'll be taken to the Collaborators page. To add a collaborator, click the Add People button.

A dialog will pop up that will let you search for a user by username, full name, or email.

Use any of those to find the person you want to add, and they'll show up in the list of possible users.

Click the name of the person you want to invite as a collaborator, then click the green "Add \" button. **WARNING:** The list of people that show up in this dropdown are pulled from the list of **ALL** GitHub users. Adding someone as collaborator gives them the ability to make changes to your website! **Make sure** the person you select is who you actually think they are! If you accidentally add the wrong person as a collaborator, don't worry, it's easy to remove them later.

After clicking the "Add" button, the person you selected will show up in the list of collaborators with "Pending invite" next to their name.

This means GitHub has sent them an email inviting them to be a collaborator on your repo. The email will look like below:

That user will now need to click the "View Invitation" button, which will take them to the GitHub website, which will prompt them Accept or Decline the invitation.

Once they click "Accept Invitation", they'll show up as a collaborator in your Collaborators list.

Collaborators have full access to change and modify any code in your repository! And they'll be able to view your repository if it's set to Private. However, collaborators can **not** view or change any Settings on your repository, so you're not at risk of them deleting your repo or locking you out. ### Removing Collaborators To remove a collaborator, simply go to the list of collaborators on your repository and click the red trashcan beside the collaborator's name.

GitHub will pop up a dialog asking you to confirm you want to remove this collaborator. Click the "Remove" button, and the collaborator will be removed.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://comic-git.gitbook.io/documentation/expert-editing/other-expert-tips.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.