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.

Sign up for GitHub

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

Jump to bottom

Can we avoid having to edit conf.py by hand? #5

Open
odscjames opened this issue Apr 24, 2018 · 1 comment
Open

Can we avoid having to edit conf.py by hand? #5

odscjames opened this issue Apr 24, 2018 · 1 comment

Comments

@odscjames
Copy link
Collaborator

  1. Copy the bits from add-to-conf.py into the real conf.py ( TODO we need to do better with this step! )
odscjames added a commit that referenced this issue Apr 27, 2018
@odscjames
Add notes to add-to-conf.py to make clear these bits should replace e…
771ee71 
…xisting bits and not be put at the end

(We haven't done #5 yet but we can at least document it better!)
odscjames added a commit that referenced this issue Apr 27, 2018
@odscjames
Start python folder to hold code used in theme. Moved pygments stuff …
5cbb774 
…to it.

Now pygments changes needed to conf.py are minimal, and any updates to pygments will appear in peoples builds with no conf.py edits needed.

May help with #5
@odscjames
Copy link
Collaborator Author

With the latest changes this is almost done!

This issue might have now become part of a bigger issue - the work is split across this repo and https://github.com/openownership/data-standard . The vagrant stuff is in this repo. At least one requirement is duplicated across the repos ( https://github.com/OpenDataServices/sphinxcontrib-jsonschema ) - that's not great. Can we tidy all this up a bit?

@stevenday stevenday mentioned this issue Mar 20, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@odscjames