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

Remove or extract doctor command #867

Open
jaredcwhite opened this issue Mar 17, 2024 · 0 comments
Open

Remove or extract doctor command #867

jaredcwhite opened this issue Mar 17, 2024 · 0 comments
Labels
process Improve the development process for the repo question Further information is requested
Milestone

Comments

@jaredcwhite
Copy link
Member

Once of the goals of Bridgetown 2.0 is to streamline the codebase and improve maintainability, outside of key functionality site authors rely on. I must confess I've personally never used the doctor command on any of my sites, and I don't fully understand its rationale. (Seems very much a holdover from past Jekyll days.) Unless there's push back to the contrary, I'm thinking of either extracting it out to a separate community-maintained gem or removing it entirely. I do like the idea of including more diagnosing/troubleshooting functionality in Bridgetown, but I think it makes more sense to be part of the site build process via flags/settings in development, rather than a specific command.

@jaredcwhite jaredcwhite added the process Improve the development process for the repo label Mar 17, 2024
@jaredcwhite jaredcwhite added this to the 2.0 milestone Mar 17, 2024
@jaredcwhite jaredcwhite added the question Further information is requested label Mar 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
process Improve the development process for the repo question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant