-
Notifications
You must be signed in to change notification settings - Fork 278
project blog: setup #1884
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
Comments
I think it's a good idea generally, and doing it in this repo with the URL theupdateframework.github.io currently just redirects to the project-wide theupdateframework.io, which also seems fine. |
I suppose enabling Project Wiki might be another option but I think blogs are more what I'd like.
There is a workaround for this: github pages can be set to publish from a |
Continuing on that, I think we might be able to live with docs/ being the blog root. It does make the docs directory again a little more cluttered (see #1849) but not horribly so. This is what I think the structure looks like:
I'll still have to test this but if that works I think the simplicity is pretty great (no automation required, everything is in python-tuf repo, GitHub just handles everything) Still can't understand why they couldn't make the location configurable??? |
It would be nice to have a place to publish project related things that are not quite documentation but something we want to be able to link to (maybe workflow examples or updates on PyPI work, etc ). This sounds like a blog so let's investigate how to have one.
I think the path of least resistance might be Github Pages right here in the python-tuf repo. Other options include reviving the
theupdateframework.github.io (currently archived project in theupdateframework organization) or a third party blog platform.
Issues to investigate:
/
and/docs
: these might not work for usThe text was updated successfully, but these errors were encountered: