{"id":20330723,"url":"https://github.com/teamnewpipe/website","last_synced_at":"2026-01-26T20:11:50.626Z","repository":{"id":17250271,"uuid":"81237988","full_name":"TeamNewPipe/website","owner":"TeamNewPipe","description":"The Website for NewPipe","archived":false,"fork":false,"pushed_at":"2026-01-11T23:21:29.000Z","size":169334,"stargazers_count":141,"open_issues_count":31,"forks_count":43,"subscribers_count":15,"default_branch":"master","last_synced_at":"2026-01-12T03:10:12.334Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"https://newpipe.net","language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/TeamNewPipe.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2017-02-07T18:05:03.000Z","updated_at":"2026-01-11T23:21:28.000Z","dependencies_parsed_at":"2025-09-23T08:33:33.630Z","dependency_job_id":null,"html_url":"https://github.com/TeamNewPipe/website","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/TeamNewPipe/website","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TeamNewPipe%2Fwebsite","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TeamNewPipe%2Fwebsite/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TeamNewPipe%2Fwebsite/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TeamNewPipe%2Fwebsite/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/TeamNewPipe","download_url":"https://codeload.github.com/TeamNewPipe/website/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/TeamNewPipe%2Fwebsite/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28787161,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-01-26T13:55:28.044Z","status":"ssl_error","status_checked_at":"2026-01-26T13:55:26.068Z","response_time":59,"last_error":"SSL_read: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-11-14T20:17:27.225Z","updated_at":"2026-01-26T20:11:50.611Z","avatar_url":"https://github.com/TeamNewPipe.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"# NewPipe Website Generator\n\nRepo for the static [NewPipe website](https://newpipe.net). The code for the blog commenting system [isso](https://posativ.org/isso) is located in [this repository](https://github.com/TeamNewPipe/isso).\n\nAll sites are based on [Bootstrap](https://getbootstrap.com) 3.4.1 and [Jekyll](https://jekyllrb.com/).\n\n\n## Development\n\n#### Installation\nInstall Jekyll and Bundler gems through RubyGems:\n``` sh\ngem install jekyll bundler\n```\n\nNavigate to the root directory of this project, dev environment:\n``` sh\nbundle install\n```\n\nNavigate to this directory and build the site on the preview server:\n``` sh\nbundle exec jekyll serve\n```\n\nOpen http://localhost:4000 in your browser.\n\n#### General\n\nAs this repository includes the press kit and the blog, we prefix all layouts and includes with either `press_` or `blog_`.\n\n## Documentation\n\n#### Categories / Tags\n \nWe do not make a difference between categories and tags, but only use categories.\nCategories are used to tag posts, so they can be found easier.\nEvery tag has an overview page where you can find all posts with this tag.\nTags are also recognized as keywords by the search and posts get with these tags get an extra boost and are listed higher.\n \nYou can add a category / tag in the YAML header of each page:\n \n \n`categories: category1`\n \n`categories: [category1, category2, category3]`\n \nPost with tags get the following permalink: `/blog/category1/category2/title`\n \nThese categories are implemented right now:\n \n- release\n- announcement\n- talk\n- download\n- pinned\n \nEvery post which has the `announcement` category will also be shown in `press/announcements/`.\n\nPosts with the `pinned` category appear on the right sidebar as _Also interesting_.\n\nNew categories can be implemented via an extra HTML page named `categoryName.html` and placed in `blog/`.\nThe new page should look like this:\n \n``` yml\n---\nlayout: blog_category\ntitle: categoryName\ncategory: categoryName\n---\n```\n\n\n##### Post thumbnails\n\nPost thumbnails which are going to be displayed at the left side of the post, need to be registered in [_data/images.yml](_data/images.yml) (see [Image metadata](#image-metadata) to learn how to do this correctly). Thumbnails should be squarish.\n\n`image`          - Displays an image at the left side of the post. Use the key you registered in [_data/images.yml](_data/images.yml).\n\n`imageHidePress` - Hides the image in the announcement page of the pres kit.\n\n\n#### Image metadata\n\nImage metadata can be set in [_data/images.yml](_data/images.yml). You can display an image in a post with following snippet: \n\n`\u003cimg src=\"/img/{{ site.data.images[IMAGE_NAME].url }}\" /\u003e`\n\n``` YML\nnewpipe-beta:                          # IMAGE_NAME which is used to display it\n  url: logo_app_beta.svg               # path to the file relative to '/img/'\n  type: svg                            # file extension like 'svg', 'png' or 'jpeg'\n  size: 16583                          # file size of the image in bytes\n  name: NewPipe Beta logo              # image description \n  author: Schabi                       # author\n  origin: https://github.com/theScrabi # optional: link to the origin of this image when it is not created by one of our teeam members\n  download: /press/logo/#logo-beta     # optional: this is a link to the internal download page with an anchor to the download form '/press/logo/#logo-beta'\n```\n\n\n##### Page metadata\n\n`metatitle` - The title to display in the browser `\u003ctitle\u003e\u003c/title\u003e`\n\n`metades`   - The description to display as `\u003cmeta name=\"description\"\u003e`\n\n`metakey`   - Additional keywords for search engines `\u003cmeta name=\"keywords\"\u003e`\n\n`modified`  - The date the page was last modified. It will be displayed at the bottom of each page. Format `YYYY-MM-DD HH:MM:SS +/-TTTT`\n\n\n##### Search\n\nAt the moment there is one search engine for the press kit and another one for the blog.\n\nThe variable `search` accepts following values which modify the position in the search results:\n\n`exclude`   - exclude the whole page from the search\n\n---\n\n#### FAQ \u0026 Tutorials\n\nFAQ and tutorials are located at https://newpipe.net/FAQ/ and https://newpipe.net/FAQ/tutorials/.\n\nEssentially FAQs and tutorials have the same structure: \nBoth are collections (`faq` and `tutorials`) and can have the same attributes which are defined via the YAML front matter.\nNevertheless we make a distinction between FAQs and tutorials because there are different behaviours implemented for them.\nWhile FAQs are displayed in multiple small collapsible boxes, every tutorial has its own page.\n\n##### Writing FAQs \u0026 Tutorials\n\nSince FAQs and tutorials are collections, firstly you need to create a new `.HTML` file in either `_faq/` or `_tutorials/`. \nPlease put the category name first and then add the title behind it: `player_enable_autoplay.html`.\nIn the file, you need to define several things to get your post recognized and printed out correctly:\n- Each post must have at least one category which assigns it to one of the subpages (`FAQ/player/`, `FAQ/download/`, `FAQ/bugs`).\n```\ncategories:\n- bugs\n- player\n- download\n```\n- There are two types a post can have: `type: info` or `type: tutorial`.\n- Every post needs a title: `title: \"Enable Autoplay\"`\n\nBefore you can start writing, there are some more small things to notice to make your post look like the others. \nWriting short FAQs is quite easy and there are only few things to consider.\n1. To structure the content, use `\u003csection\u003e`s. There should be no content which is not in a `\u003csection\u003e`.\n2. To separate parts of your article with a thin line, use `\u003chr/\u003e` tags. \n3. To insert images, use the `\u003cimg/\u003e` tag inside of a `\u003cfigure\u003e` tag. Additionally, each image needs a caption (`\u003cfigcaption\u003e`).\n4. Please keep your sentences as shorts as possible. This makes it easier to follow you and your instructions.\n\n---\n\n#### Usage of Website API\nWe have an API which provides data for running the website to not require visitors contacting other servers when visiting our website.\nYou can find its source code [on GitHub](https://github.com/TeamNewPipe/web-api) and the served data [here](https://newpipe.net/api/data.json).\nIf you want to use the API for other purposes than running or developing our website, please host it yourself.\n\nTo use API data, you need to add the `data-newpipe-api` attribute to an HTML tag containing the JSON identifier of the value you want to access:\n\n``` HTML\n\u003cp\u003eNewPipe has \u003cspan data-newpipe-api=\"stats.stargazers\u003e10k\u003c/span\u003e stars on GitHub.\u003c/p\u003e\"\n```\n\nBy default, the inner HTML of tags which have the `data-newpipe-api` attribute will be replaced with the requested value. Nevertheless, you should put a value there to provide a fallback for the rare case, that our API failed to generate correct data. \nIt is also possible to not replace the HTML, but store the API data in a referred attribute by adding the `data-newpipe-api-attribute` attribute:\n\n``` HTML\n\u003ca data-newpipe-api=\"flavors.fdroid.stable.apk\" data-newpipe-api-attribute=\"href\"\u003edownload NewPipe\u003c/a\u003e\n```\nwill result in something like\n``` HTML\n\u003ca href=\"https://f-droid.org/repo/org.schabi.newpipe_953.apk\"\u003edownload NewPipe\u003c/a\u003e\n```\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fteamnewpipe%2Fwebsite","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fteamnewpipe%2Fwebsite","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fteamnewpipe%2Fwebsite/lists"}