List of example sites using this app

[rmanalan]

It would be cool to add a list of sites using this excellent app. I'd love to see how others are using it and their photos as well. Happy to contribute mine if you think this is a good idea. Happy to also get it kickstarted with a PR. Here's mine: https://booshie.photo

[sambecker]

I like this idea @rmanalan with the following criteria:

• Project must auto-sync their fork, so it always shows the latest template design + behavior
• Must have static pre-rendering enabled for responsive site loading
• Photos must:
  • be family friendly, i.e., inoffensive to a general audience
  • contain full EXIF details
  • look great
• Not all submissions will be published

Once this is in the README, think I might create an issue template for submissions

WDYT?

[rmanalan]

Sounds good to me... although how do you auto-sync your fork? I manually sync my fork since I've committed a few customizations to my copy.

[sambecker]

how do you auto-sync your fork?

I've noticed some folks setup GH actions, though this may be too much to ask.

Could tweak language to "Must keep fork up to date, so it always shows the latest template design + behavior?"

[rmanalan]

Yeah that makes more sense. Are you worried of sites that are outdated? Sent with Shortwave <https://www.shortwave.com?utm_medium=email&utm_content=signature&utm_source=cmljaC5tYW5hbGFuZ0BnbWFpbC5jb20=> On Tue Sep 9, 2025, 11:42 PM GMT, Sam Becker ***@***.***> wrote: [image]sambecker left a comment (sambecker/exif-photo-blog#301) <#301 (comment)>

…

> how do you auto-sync your fork? I've noticed some folks setup GH actions <https://github.com/rajtslegr/exif-photo-blog/blob/main/.github/workflows/auto-sync.yml>, though this may be too much to ask. Could tweak language to "Must keep fork up to date, so it always shows the latest template design + behavior?" — Reply to this email directly, view it on GitHub <#301 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAEJPVW26Y6EFQAZZ4ERD3R5QWPAVCNFSM6AAAAACFIOYKIKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENZSGY2DAOJZGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[sambecker]

Are you worried of sites that are outdated?

Just want to make sure anyone checking those demos will be seeing current implementations and I imagine there will be a tendency for those examples to drift over time

[rmanalan]

It makes sense. Would you want to exclude forks that have modifications? For example, my fork has those modifications for Nikon film sims (I still want to work on a PR to push that upstream, but haven't had time). Also, someday, I'd love to add a blog/story component to my fork. I've been itching to have a place to write photo essays and it would be great if this supported this -- let me know if you're interested.

[sambecker]

Would you want to exclude forks that have modifications?

Light modifications are fine so long as the bulk of template functionality remains up to date

I still want to work on a PR to push that upstream, but haven't had time

That would be awesome! We have so many Fuji features, and would be really nice to better support heavy hitters like Nikon ...

I've been itching to have a place to write photo essays

This is part of what I'm trying to accomplish with #315—lmk if you have any builds there

[rmanalan]

That would be awesome! We have so many Fuji features, and would be really nice to better support heavy hitters like Nikon ...

I think I'm going to remove all the mods to my current set up and start from scratch. I feel like my branch has strayed a bit farther than I'd like from upstream. That's also what's been holding me back from creating a new PR for the Nikon customizations.

[sambecker]

think I'm going to remove all the mods to my current set up and start from scratch

Amazing!

Definitely wait until #315 lands, which changes hundreds of files!

Can’t wait to see this PR. Nikon users will rejoice.