A micro front-end for creating onling photography zines to share.
I'm exhausted by photography being crowded in an algorithmically-curated feed, limited by the platform's available tools, compressed, and viewed on a tiny screen.
It's sad.
Much like a physical book will always be better than a Kindle 🤮, the Zine framework will always be inferior to printing a zine and sharing it with your friends. I fully intend to find a way to bridge the gap, and turn Zine into my own automated printing pipeline.
Until that day, what Zine does do is creates an easy framework to work within when designing and deploying my online zine. With the included CLI, I can extend the app endlessly by creating new templates, new extensions, and new components within my framework ✨ a u t o m a g i c a l l y ✨!
🔸WIP - In forthcoming work, I will be building tools to create a zine, and deploy the updated front-end via the CLI.
- Language(s):
TypeScript,JavaScript - UI:
reactviacreate-react-app - Styling:
styled-components - CLI:
commanderto runcommonJSin the terminal
Basing the template system on react meant that I'd be drowning in a mix of my terms and their terms: template, component, element, block, provider, etc. I took a moment to define the elements of the Zine ecosystem:
- Template - A zine page layout that can enforce rules (checks) on props to allow highly-specific code (i.e. no need for any conditional rendering,
undefinedchceks, etc.) - Block Component - Element made with
styled-componentsas a building block for templates - Logic Component - Element, often JSX, that the app uses to perform logic checks and conditionally render templates
- Rule Function - Function that enforces prop rules and throws a custom error if the props do not meet the rule's assertion
- Feature Hook - React hook that plugs into a template or logic component to provide new functionality
Additionally, Errors, a group of custom error classes, and Configs, where the potential of the Zine ecosystem truly expands.
The intent is to deliver a zine over the air. The ZinePageConfig is the expected shape of the incoming data from my zine delivery service. However, this does mean that if I want to extend the functionality to template out other types of pages, I could introduce a new config and a new set of logic components to handle it, and render the pages all the same - taking full advantage of the prop validation rules system, and the safe templating system.
To subvert the need for conditional checks inside templates, leading to bloated JSX, I opted to build a safe templating system. Instead of writing a condition in my template, I write a Rule Function! This will throw a nice error for me whenever my rule is broken, with a customizable message out of the box.
When a rule is added to the exported array of rules in my template file, I can rest assured a prop is present, or contains only an acceptable value, and write my template without worry.
I decided to build a cli to assist in the generation of new templates, components, and extensions. It's built using commonJS in a node environment using the commander npm package to run it as a cli.
To set up:
yarn cli:init
component <name> -t <type>- Generates a new Zine componenttemplate <name>- Generates a new Zine templateextension <name> -t <type>- Generates a new extension (rule or hook)
To unlock debug features, utilize the -d or --debug flag with any command. Debug features are exported from the debug.js module for use in all modules.
To add a component to Zine, I can use the new zine component <name> command. The required -t or --type flag is how I indicate whether I want a block or logic component. Names must follow be strictly alphabetical and extended names must be hyphenated.
zine component --type logic myNewThing ❌
zine component --type logic my-new-thing ✅
This generates a component file in the proper subdirectory with the filename structure, following the above example input, of MyNewThing.ts or MyNewThing.tsx. It'll also add the exports to components/index.ts
To set up a new template, I use the new zine template <name> cli command. Names must follow be strictly alphabetical and extended names must be hyphenated. The template generator handles appending template to your desired template name.
zine template awesomeSauce ❌
zine template awesome-sauce ✅
This generates /AwesomeSauceTemplate.tsx, and exports the setup from templates/index.ts. Inside the new template file, there is an empty rules array, a pre-made generator, and an empty template.
To set up a new extension, I use the new zine extension <name> cli command. The required -t or --type flag is how I indicate whether I want a new rule or hook. Names must follow be strictly alphabetical and extended names must be hyphenated. The template generator handles name transformation, including appending the use prefix for hooks
zine extension -t hook use-new-hook ❌
zine extension -t hook new-hook ✅
zine extension -t rule newRule ❌
zine extension -t rule new-rule ✅
If creating a rule, it'll output the new file in framework/extension-rules, and likewise it'll output to framework/extension-hooks for hooks. In both cases, the exports will be generated inside of framework/index.ts.