Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compatibility matrix should use unified data/presentation files #587

Open
harding opened this issue Jun 7, 2021 · 0 comments
Open

Compatibility matrix should use unified data/presentation files #587

harding opened this issue Jun 7, 2021 · 0 comments

Comments

@harding
Copy link
Collaborator

harding commented Jun 7, 2021

For each wallet/service in the compat matrix, we have two files:

  • A file in _data/compatibility/ with the wallet's characteristics
  • A boilerplate file in en/compatibility/ that calls the template with the characteristic data

That's dumb. The idiot who designed it that way should be ashamed of himself. A better method would be to use a custom post type like we did for the topics with the _topics/en/ directory where we have two documents combined into a single file, a YAML data part and a Markdown part (which can be empty in this case). This eliminates the need for the boilerplate and ensures only a single file needs to be edited, renamed, or deleted when we want to make changes to a particular wallet or service.

This should be a pretty simple conversion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant