Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

Repository files navigation

just-the-docs-template

This is a bare-minimum template to create a Jekyll site that:

  • uses the Just the Docs theme;
  • can be built and published on GitHub Pages;
  • can be built and previewed locally, and published on other platforms.

More specifically, the created site:

  • uses a gem-based approach, i.e. uses a Gemfile and loads the just-the-docs gem;
  • uses the GitHub Pages / Actions workflow to build and publish the site on GitHub Pages.

To get started with creating a site, simply:

  1. click "use this template" to create a GitHub repository
  2. go to Settings > Pages > Build and deployment > Source, and select GitHub Actions

If you want to maintain your docs in the docs directory of an existing project repo, see Hosting your docs from an existing project repo.

After completing the creation of your new site on GitHub, update it as needed:

Replace the content of the template pages

Update the following files to your own content:

  • index.md (your new home page)
  • README.md (information for those who access your site repo on GitHub)

Changing the version of the theme and/or Jekyll

Simply edit the relevant line(s) in the Gemfile.

Adding a plugin

The Just the Docs theme automatically includes the jekyll-seo-tag plugin.

To add an extra plugin, you need to add it in the Gemfileand in _config.yml. For example, to add jekyll-default-layout:

  • Add the following to your site's Gemfile:

    gem"jekyll-default-layout"
  • And add the following to your site's _config.yml:

    plugins:
    - jekyll-default-layout

Note: If you are using a Jekyll version less than 3.5.0, use the gems key instead of plugins.

Publishing your site on GitHub Pages

  1. If your created site is YOUR-USERNAME/YOUR-SITE-NAME, update _config.yml to:

    title: YOUR TITLEdescription: YOUR DESCRIPTIONtheme: just-the-docsurl: https://YOUR-USERNAME.github.io/YOUR-SITE-NAMEaux_links: # remove if you don't want this link to appear on your pagesTemplate Repository: https://github.com/YOUR-USERNAME/YOUR-SITE-NAME
  2. Push your updated _config.yml to your site on GitHub.

  3. In your newly created repo on GitHub:

    • go to the Settings tab -> Pages -> Build and deployment, then select Source: GitHub Actions.
    • if there were any failed Actions, go to the Actions tab and click on Re-run jobs.

Building and previewing your site locally

Assuming Jekyll and Bundler are installed on your computer:

  1. Change your working directory to the root directory of your site.

  2. Run bundle install.

  3. Run bundle exec jekyll serve to build your site and preview it at localhost:4000.

    The built site is stored in the directory _site.

Publishing your built site on a different platform

Just upload all the files in the directory _site.

Customization

You're free to customize sites that you create with this template, however you like!

Browse our documentation to learn more about how to use this theme.

Hosting your docs from an existing project repo

You might want to maintain your docs in an existing project repo. Instead of creating a new repo using the just-the-docs template, you can copy the template files into your existing repo and configure the template's Github Actions workflow to build from a docs directory. You can clone the template to your local machine or download the .zip file to access the files.

Copy the template files

  1. Create a .github/workflows directory at your project root if your repo doesn't already have one. Copy the pages.yml file into this directory. GitHub Actions searches this directory for workflow files.

  2. Create a docs directory at your project root and copy all remaining template files into this directory.

Modify the GitHub Actions workflow

The GitHub Actions workflow that builds and deploys your site to Github Pages is defined by the pages.yml file. You'll need to edit this file to that so that your build and deploy steps look to your docs directory, rather than the project root.

  1. Set the default working-directory param for the build job.

    build:
    runs-on: ubuntu-latestdefaults:
    run:
    working-directory: docs
  2. Set the working-directory param for the Setup Ruby step.

    - name: Setup Rubyuses: ruby/setup-ruby@v1with:
    ruby-version: '3.1'bundler-cache: truecache-version: 0working-directory: '${{ github.workspace }}/docs'
  3. Set the path param for the Upload artifact step:

    - name: Upload artifactuses: actions/upload-pages-artifact@v1with:
    path: "docs/_site/"
  4. Modify the trigger so that only changes within the docs directory start the workflow. Otherwise, every change to your project (even those that don't affect the docs) would trigger a new site build and deploy.

    on:
    push:
    branches:
    - "main"paths:
    - "docs/**"

Licensing and Attribution

This repository is licensed under the MIT License. You are generally free to reuse or extend upon this code as you see fit; just include the original copy of the license (which is preserved when you "make a template"). While it's not necessary, we'd love to hear from you if you do use this template, and how we can improve it for future use!

The deployment GitHub Actions workflow is heavily based on GitHub's mixed-party starter workflows. A copy of their MIT License is available in actions/starter-workflows.


About

No description, website, or topics provided.

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages