You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current setup of this repo is that there is a single Markdown file, holding all information. As discussed with @DavidLambauer, there could be a huge benefit of splitting up the resources into smaller files (Markdown, CSV, JSON) and using a build tool to parse these resources into the main README.md file. The smaller resource files (like an events.json, an extensions.csv file or simply a about-magento.md file) could then be used elsewhere (remote feeds, website generators) as well.
The text was updated successfully, but these errors were encountered:
Perhaps add all of the resources into a folder called resources/. The MVP for this would be two Markdown files in that resources/ folder that are then merged together by a build tool, to override the README.md file. The build tool could be built with Laravel Zero, and automatically run via GitHub Actions with every PR.
The current setup of this repo is that there is a single Markdown file, holding all information. As discussed with @DavidLambauer, there could be a huge benefit of splitting up the resources into smaller files (Markdown, CSV, JSON) and using a build tool to parse these resources into the main
README.md
file. The smaller resource files (like anevents.json
, anextensions.csv
file or simply aabout-magento.md
file) could then be used elsewhere (remote feeds, website generators) as well.The text was updated successfully, but these errors were encountered: