Make all configs optional

[kkomelin]

Description

Walrus config and walrus site builder config should not be compulsory. Just hardcode the package value for them in the code of walrus and site-builder. Users don't need them. Otherwise we constantly need to compare our values with the documentation, why?

Component

site-builder

Code of Conduct

• I agree to follow this project's Code of Conduct.

[gordonkoehn]

Finding this package id is not a great Development Experience to get started. Took me a minute to find it in sites-config.yaml.

[kkomelin]

@gordonkoehn It's in the documentation but still https://docs.walrus.site/walrus-sites/tutorial-install.html#configuration

[gordonkoehn]

Appreciated – realized just also now. Should have read to the end of the page. 😅 Apologies for unnecessarily adding to this thread.

[kkomelin]

@gordonkoehn No, no, your feedback is very appropriate. Thank you. It just confirms my point. There should be default configuration added to the site-builder itself without the need to create the configuration file manually after installation. Who knows that package ID value better than the site-builder developers.