edition Project;

paths
{
    # In HMN, root would be the directory that serves up  https://hero.handmade.network/episodes where the searcher will reside
    root "/usr/local/www/test";
    # All *.hmml files below the repo_remote location are to be pulled in to the system with the directories being compared with
    # the member and project settings from the [video] node
    repo_remote "https://git.handmade.network/Annotation-Pushers/Annotation-Game";
    repo_local "/usr/local/www/repo";
    # The automatic stub creator will use the stub_base as its base directory
    stub_base "${repo_local}/projects";

    quotes_remote "";
    quotes_local "";
}

authentication
{
# NOTE(matt): Do we need any more auth stuff? Surely we will
    repo_token "";
    quotes_token "";
}

project_info
{
    riscy # Note that settings that open blocks do not end in a ; thus distinguishing them from variables set at the same scope
    {
        # We need to set member and platform in the config file so the stub generator can do its thing. Maybe consider further,
        # though, whether the [video] node in our .hmml files still needs to take them
        member = "miotatsu";
        platform = "youtube";

        feed = "https://www.youtube.com/feeds/videos.xml?user=BathtubBlogger";
        project_name "RISCY BUSINESS";
        project_unit "Day";
        title_pattern "${project_name} - ${project_unit} ${number} - ${title}";
        # TODO(matt): Work out this title_pattern with some actual stuff
    }
}

# Comment to end of line
credentials
{
    funding_platform patreon; # This determines the logo and URL-generation, and we'll need to specify the platforms we support.
                              # A more flexible, if verbose, alternative would be to make each config specify a funding_icon and
                              # the full funding_url
                              #
                              # Note that this setting cascades down to the child scopes, i.e. Miblo{}, miotatsu{}, etc

    Miblo # The single-word name we use in the .hmml files, which also matches the username of project owners
    {
        display_name "Matt Mascarenhas"; # Optional, and may optionally be surrounded by quotes
        homepage "http://miblodelcarpio.co.uk/"; # May optionally be quoted, as the admin prefers, but must be quoted if
                                                 # containing a ; (which is a valid character according to:
                                                 # https://url.spec.whatwg.org/#userinfo-percent-encode-set)
                                                 #
                                                 # For a Network Edition instance, it may be nice, although not mandatory, if
                                                 # the homepage is set to the member's profile page in the Network
        avatar "some_location.png"; # TODO(matt): Mock up the Credits Menu to determine whether or not we want this
        funding_username miblo;
    }

    miotatsu
    {
        display_name "Mio Iwakura";
        homepage "http://riscy.tv/";
        funding_username miotatsu;
    }

    _yunsup_lee # Prefixing with _ could be the convention for guests who are not in the member base of the (associated) network
                # If so, maybe throw a warning for the annotator when a _-prefixed member is not present in the config
    {
        display_name "Yunsup Lee";
        homepage "https://www.linkedin.com/in/yunsup-lee-385b692b";
    }

    _andrew_waterman
    {
        display_name "Andrew Waterman";
        homepage "https://www.linkedin.com/in/andrew-waterman-76805788";
    }
}

# NOTE(matt): Semantic characters, which may require \-escaping: ; # { " $