Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strava Routes Page Injection Plugin #1405

Open
Checkroth opened this issue Aug 3, 2024 · 0 comments
Open

Strava Routes Page Injection Plugin #1405

Checkroth opened this issue Aug 3, 2024 · 0 comments

Comments

@Checkroth
Copy link

What is this issue?

I am opening a new issue, as per the REAME on this repository, about a plugin I have been working on.

If you have come here to submit a pull request to add your plugin, please consider instead moving your plugin under the Pelican Plugins organization. To get started, create a new issue under this repository with the details of your plugin, after which a Pelican maintainer will guide you through the process.

If there's interest, I'd like it to be included in Pelican Plugins

What's the Plugin?

The plugin is strava-runmap.

It takes some configuration to connect to the Strava API, and will create an SVG digest of every activity you have ever done in strava that includes a map.

It can be seen live on my own pelican site: https://checkroth.com/pages/strava-runmap.html

Status of the Plugin

The plugin is far from perfect. I would like to tidy it up a bit, if it were going to be added to an official registry of pelican plugins.
If it isn't, then I probably won't go through the effort.

  • The build is failing -- could fix it if needed.
  • The plugin itself is injecting a page in a sort of nasty "raw html with inline CSS in a single python string", as I couldn't find a way to use real templating. Happy to improve that, if pelican maintainers can offer some guidance
  • The plugin has not been published. Currently it uses the structure that assumes it has been published, but can only actually be incorporated with git submodules, which also means that the nested plugins path has to be updated to find the actual plugin (seen here )

Again, happy to work on all these issues if needed. Its currently in a working state, and I've decided to leave it there for the time being; if I'm the only one who's going to end up using it, it's not much worth the continued effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant