The content folder for Pelican
Content files can contain a number of different variables to be parsed by pelican.
While you should not have to directly edit these most times you might have to use the variables for pathing relative to server root.
The configuration file sets what the site url will be which may change based on if it is being published to production or a qa site or based on the content.
For example production will all be starting at / like /images or http://thelab.ms/images but the qa site might start with /website-content/ line /website-content/images or http://thelab-ms.github.io/website-content/ and the makers area content will be starting with /makers/ like /makers/images or http://thelab.ms/makers/images
So in order to make sure internal links work properly you should use the {filename} variable on content pages.
Do not simply create an internal link to content such as href="/images/abc.gif" and expect it to work! Use the proper variable format of href="{filename}/images/abc.gif" and it will work fine.
We have some project pages in the /makers/ content that have been highlighted by placing them in thier own directory which will be linked from web root (e.g. /makers/tap/ is also /tap/).
It is important to note that the content for these highlighted projects is located in the website-makers repository and NOT in the website-content repository.
It is also important that internal links are still referenced with the {filename} directive listed above. This will allow the pages and all thier internal links to images etc. to work from both locations where an absolute path might break in one of the locations.
See the website-pelican repository README.md file for more details.