Exclude unsupported files from JupyterLite build in documentation site

[arjxn-py]

Description

Shall close #917

Checklist

• PR has a descriptive title and content.
• PR description contains references to any issues the PR resolves, e.g. Resolves #XXX.
• PR has one of the labels: documentation, bug, enhancement, feature, maintenance
• Checks are passing.
  Failing lint checks can be resolved with:
  • pre-commit run --all-files
  • jlpm run lint

---

📚 Documentation preview: https://jupytergis--919.org.readthedocs.build/en/919/
💡 JupyterLite preview: https://jupytergis--919.org.readthedocs.build/en/919/lite

[github-actions]

👈 Launch a Binder on branch arjxn-py/jupytergis/exclude-99-explore-nb

[github-actions]

Integration tests report: appsharing.space

[arjxn-py]

cc @mfisher87 I have been unable to exclude these files so far!

[agriyakhetarpal]

How about using LiteBuildConfig.ignore_contents in a jupyter_lite_config.json file?

[arjxn-py]

How about using LiteBuildConfig.ignore_contents in a jupyter_lite_config.json file?

Hi @agriyakhetarpal, Thanks I can try that quickly but since @mfisher87 recently added mapping to jupyterlite-sphinx jupyterlite/jupyterlite-sphinx#309 - I am thinking that it would be an optimal solution?

[mfisher87]

I do like keeping the information about content inclusion/exclusion together! But it's interesting to know there's another option. Maybe jupyterlite-sphinx should use jupyter_lite_config.json as the only location for build config instead of providing a new API in conf.py? 🤔

I think I know why this isn't working, will apply a change and see if that fixes the build.

[mfisher87]

That worked fine!

[mfisher87]

LGTM ⭐

[agriyakhetarpal]

Maybe jupyterlite-sphinx should use jupyter_lite_config.json as the only location for build config instead of providing a new API in conf.py? 🤔

I think the API is fine in this case, as we have a jupyterlite_contents option and the jupyterlite_ignore_contents option complements it pretty well! However, I think we should indeed have some discussion on which options should make it to conf.py and which ones shouldn't – for advanced options and configuration, we already support jupyterlite_build_command_args.