forked from holman/ama
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Is there a place where you explain how GeoGlitchies works? #126
Comments
I think the instructions page is the most we have in terms of how it works. If you look at the project code, most of it is the eleventy code:
cc @jlord if I've missed anything! |
Thank you. That is very helpful.
…-Michael
On Wed, Dec 16, 2020 at 3:01 PM Monica Dinculescu ***@***.***> wrote:
I think the instructions <https://geoglitchies.glitch.me/instructions/>
page is the most we have in terms of how it works.
If you look at the project code <https://glitch.com/edit/#!/geoglitchies>,
most of it is the eleventy code:
- .eleventy.js is the eleventy config
- watch.json has the list of watch files, which is basically anything
in css, src and some config files
- that watch file is iirc used by glitch to re-run the npm install
script when anything in those files changes. so basically, every time you
add a new post or edit one, the site is rebuilt.
- src/_data/friends.js has the "webring" functionality
- src/_data/_includes/layouts has the templates for each page
cc @jlord <https://github.com/jlord> if I've missed anything!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#126 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM6ZKSVJJGUEHDVA4BKUA3SVEG27ANCNFSM4UZF6GDQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a place where you (or Jessica Lord) explain how GeoGlitchies works?
I realize it must all be there, but I haven't been able to figure it out.
-Michael
The text was updated successfully, but these errors were encountered: