Back in google groups we had a discussion about rendering for development or production. Bascially workflow issues
Several notions about how were discussed. (should we repeat the highlights, agreements?)
Just wondering where this stands and if coding is happening for v0.13/
The more I get into Hugo the more this seems to be an important workflow issue.
One big reason among others is the baseurl setting in the config file which I must change manually from dev/pro
It would be great too if render “destination” could be specifed in the config file (but till keep the command line swtich)
Here is my idea for this workflow thing.
Data in the frontmatter of documents or the config file could be triggered(used/ignored) based on a workflow switch in the CLI.
Kinda like this -w for say workflow followed by the workflow name, Then in any toml/json/yaml (config or frontmatter) any data item could have an additional parameter (none for defualt) specifying which workflow is to use this data item.
e.g -w dev, or -w pro
One thing I see is that I could have workflows for indiivduals within a project. I mean say person x, had pictures on his windows box in such a directory and person y the same pictures put in a different path on their linux box then to statsfy them both they just put -w personx or -w persony into the CL, and use personx or persony parameter in any indvidual specific data item. I’m thinking too that one could combine “workflows” in the CL as in -w dev,personx
This then totally avoids issues of custom configs for different content contributors and allows that git workflow thing to work seamless among contirbutors for a document/site.
For example I have set up a data item in the frontmatter that holds a path to a picture gallery. In this way in the document I only use the filename without path. Then for production I need that to change to the cloud based path from a local path(manually now). You can see that if I do this manually and push then anyone pulling this for dev work will get the production path unless right after rending I edit it back (not a good workflow!).
Others thoughts? How easy to code this?
Just an overall suggestion - If Steve or others would point out appropirate source locations and outline an approach/caveats to implementing feature requests then some of the rest of us might be able to jump in to actual coding of Hugo.