mottaquikarim / airgo Goto Github PK

This data ought to come from airtable, via a meta table (...or something, as part of this task you will have to make a decision and determine pros/cons of your solution).

The expectation is there ought to be two templates (representing header and footer) that are reused in all the other content templates

This template is used with the following pages:

• Gallery
• Flowers
• Photography
• Limo
• (arguably) accessories

All of these pages should use the same underlying template, so implementation of a single template knocks out a significant chunk of the work

Currently, the refresh_data script (cmd/refresh_data/main.go) hardcodes a look up to the Home table in airtable.

Background

config.json looks like this:

{
	"nav": [{
		"name": "Home",
		"key": "Home",
		"filenameRoot": "index"
	}],
}

As a part of this task, update the implementation of refresh_data to read the config.json file, iterate through each record in the JSON struct and query airtable for the tablename found in the key field.

Each key field lookup should generate a corresponding [filenameRoot].json file in the data folder.

Example

For example, if config.json looked as follows:

{
	"nav": [{
		"name": "Home",
		"key": "Home",
		"filenameRoot": "index"
	}, {
		"name": "About",
		"key": "About",
		"filenameRoot": "about"
	}],
}

and the airtable base has a second About table defined, then the script should generate TWO files in the data/ folder:

data
|-- index.json
|-- about.json

Since the first filenameRoot key is index and the second filenameRoot key is about.

Error handling

If the airtable API errors, ignore that error but do not allow the application to panic! So for instance, if there was no about table in Airtable, the expected output should still be:

data
|-- index.json

For this task, implement the pipeline necessary for formatting, building and publishing the content to the internet.

In particular,

• leverage Github Actions CRON for running a build every hour
• skip the build if no changes detected
• publish a "log record" of build statuses for debugging and sanity checking

Currently testing docker on the laptop and also making changes to see what works or doesn't.

1. Clone this repo
2. Read the README and ensure you are able to get the make targets working as expected
3. Create a new branch: git checkout -b rumman/first-pr
4. Update README and add yourself (and myself) under a new subsection (at the bottom) called CONTRIBUTORS.
5. Each name should link to the person's github repo
6. Push your branch (google this if unsure) and open a PR and add me to it.

Build the bare minimum scripts, dockerfiles, and make targets necessary to easily get up and running with this project.

Document how everything ought to work in README.