Hello, there seems to be an issue with one of the contents on the homepage. I noticed that an image is not appearing in the designated section. I checked the demo site, and the same problem persists there as well. I attached a screenshot of the selected area where the image should be, but it's not visible. Is this an error on my part or is it a known issue?

How to enable search?
cant find setting to put content key on admin

I have configured my Ghost blog to be hosted on a subpath such as https://example.com/blog/.

However with the Source theme the link to see the next page of posts is linked as https://example.com/page/2

Whereas I believe it should link to as https://example.com/blog/page/2

Looks like the culprit is this line:

I've solved it for now by using the following Code injection in my admin panel:

<script>
  document.addEventListener('DOMContentLoaded', function () {
      var currentUrl = window.location.href; // Get current URL
      var appendUrl = "page/2"; 
      var newUrl = currentUrl + appendUrl;
      var link = document.querySelector('.gh-more a');
  
      link.href = newUrl; // Set the href attribute
  });
</script>

Hi,

Not really an issue but since I'm not a developer and don't know how to create/submit PRs, I'm dropping it here.

I've made a couple of changes to improve the accessibility rating on Google PageSpeed Insights that maybe you could look into implementing:

added title="Subscribe" aria-label="Subscribe" in email-subscription.hbs
<button class="gh-button" type="submit" title="Subscribe" aria-label="Subscribe">

added title="Menu" aria-label="Menu" in navigation.hbs
<button class="gh-burger gh-icon-button" title="Menu" aria-label="Menu">

These basically improved the accessibility rating for my website homepage to 100%!
I will look to do the same in other files that use <button> tags...
Wanted to contribute to Ghost and improve even more the amazing Source theme :)

Best,
Pedro

When scrolling the fixed navigation element on mobile, the scroll event is propagated to the rest of the page once the bottom/top is reached.

Ideally, this should not happen. The page below should retain the position that it had when the navigation menu was opened, and it should not be accidentally scrolled as a result of the scrolling on the navigation.

See the problem in action:

I was trying to fix this myself, but there are multiple ways to to tackle this problem, so I thought it would be better to open an issue first, to discuss which would be the preferable way to fix it.

Hey all, thanks for the awesome theme.

I just switched to it and it looks pretty nice.

Unfortunately, I discovered that tag pages are showing 16 articles, only, and have no way to show older articles. Therefore, people cannot see more than 16 articles per tag. You can find an example here: https://blog.while-true-do.io/tag/automation/

I am using source 1.0.0 on Ghost 5.67.0.

I hope this can be hammered out quickly. In case I can support you with the same, please don't hesitate to reach out/ping me.

Hi there! Thanks for this amazing theme.

I wonder if there is a code for https://source-newsletter.ghost.io/ to take a look at.

I notice that my 5th newest blog article and older are listed under the "Latest" section below the "Subscribe" section on the home page. I am using the "Highlight" header style. I am running Ghost v5.70.1, and Source v1.1.0.

Is this "Latest" header referring to the items below it, or above it?

This may be something very weird with my storage adapter, but when using source I have my images generated with a formats/webp path but my content directory has no formats directory and no .webp

The articles (and images) were created while using source. The srcsets for the other formats are generated.

The Source theme seems to be missing any use of the {{pagination}} helper on the front page. Because it's making a {{get}} request, it's not possible to navigate to /page/2 and beyond.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Repository problems

These problems occurred while renovating this repository. View logs.

• WARN: Using npm packages for Renovate presets is now deprecated. Please migrate to repository-based presets instead.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency postcss to v8.4.31 [SECURITY]
• Update CSS preprocessors (autoprefixer, cssnano)
• Update dependency inquirer to v8.2.6
• Update dependency gscan to v4.43.0
• Update dependency cssnano to v7
• Update dependency gulp to v5
• Update dependency gulp-postcss to v10
• Update dependency gulp-zip to v6
• Update dependency inquirer to v9
• Lock file maintenance
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

After switching to the new Source theme, the filters I've set up in my custom routes.yaml are no longer filtering posts correctly. Others in the forums also seem to have this issue: https://forum.ghost.org/t/the-source-theme-doesnt-show-posts-on-websites-with-custom-routes/41741/15

I have my routes.yaml set up to hide posts with certain tags from my homepage, which with Source no longer has any filtering. I also found that the collection pages I've set up for specific tags are only filtering up to the lazy load. The next set of posts loaded have no filtering.

EDIT: Now that I'm looking more closely, the lazy load on collection pages is loading the whole feed over again, repeating the posts already loaded.

Given the portal is getting translations now and this is the new default theme: is Source accepting translations pull-requests? I'd love to see german translation and I'd like to work on it.

I love the Source theme, but I noticed that <code></code> and <pre><code></code></pre> elements have no background colour, which is common with other themes. My website has lots of code examples within posts, and using the Source theme makes them hard to read.

This is what code elements currently look like using Source:

This is what I would expect code elements to look similar to (please excuse shonky editing):

With the fix of #10 2 new issues were introduced.

First, the new "endless scrolling" prevents that the footer can be seen properly. This might be an oversight, but the footer is no longer visible and therefore the secondary links are unavailable.

Second, when scrolling below the initial content (the moment when endless scrolling starts) the same content will be displayed again. Therefore, there is a lot of duplication when scrolling down.

As the title says, when Header style Landing is selected and choosing Use the publication cover set on the Brand tab as your background, the publication cover is not shown. It does work when selecting "Search" as header style

Would it be possible to allow an option for the post's main image to be smaller?

When uploading the theme it is showing an error in the package.json:
'package.json property "config.custom" contains too many settings'

Hi there,

I ran into a problem when I included more than four tables in a single blog post; they all appeared clustered together. It was quite odd, but I believe I've discovered a workaround.

At the end of the file changed:

main.js:

/* Responsive HTML table */
(function () {
    const tables = document.querySelectorAll('.gh-content > table:not(.gist table)');
    const wrapper = document.createElement('div');
    wrapper.className = 'gh-table';

    tables.forEach(function (table) {
        table.parentNode.insertBefore(wrapper, table);
        wrapper.appendChild(table);
    });
})();

TO:

/* Responsive HTML table */
(function () {
    const tables = document.querySelectorAll('.gh-content > table:not(.gist table)');

    tables.forEach(function (table) {
        const wrapper = document.createElement('div');
        wrapper.className = 'gh-table';
        table.parentNode.insertBefore(wrapper, table);
        wrapper.appendChild(table);
    });
})();