🍑 Spin up SSG

[tatianamac]

Simpler seems better here, something where markdown or another FMD approach can allow for easy profile creation.

[tatianamac]

What about this for approach?

1. Spin up site.
2. Create some sort of database that can be contributed to, like we've discussed via .md files or JSON or whatever.
3. Gather 10 or so user's data so we can start to have some real data to design around.
4. Design the thing.
5. Get more users to start stress testing it.

[taurean]

Sounds good to me @tatianamac

[cdvillard]

SSGs like Gatsby and Gridsome offer a simple enough GraphQL setup to work with straight markdown files. I'm new to Eleventy, so I'm not sure how to set one up there, but ultimately, a potential setup could be a directory with markdown files, ${framework}-source-filesystem to set the GraphQL relationship between the markdown and graph, and then programmatically create pages based on a template from there.

[taurean]

Sounds good to me @cdivillard, although I don’t know much about this. Curious, would we want to have stand-alone profile pages that someone could link to?

[tatianamac]

I'd prefer to use as little JS as possible to make this as performant and accessible as possible. If we want to serve communities where internet is slow and folks rely on data, that will be the best way.

Re: standalone pages: Yes, I'd love this to serve as something that folks can link to in lieu of (or in addition to) a website. That reminds me, we should consider adding a slot for Sponsor links (Patreon, GitHub Sponsors, etc)

[cdvillard]

I'm on board with serving as little JS as possible and sponsor links. Ultimately what I'm suggesting is server-side rendering or rendering at a build step on a service like Netlify. That way all that is served is static files, no unnecessary JS on the page. I believe that's what my GraphQL suggestion would accomplish, though I admit I'm still learning about it a bit. I'm fine with doing the legwork on that to confirm.

…

On Sat, Aug 31, 2019, 8:25 PM Tatiana Mac ***@***.***> wrote: I'd prefer to use as little JS as possible to make this as performant and accessible as possible. If we want to serve communities where internet is slow and folks rely on data, that will be the best way. Re: standalone pages: Yes, I'd love this to serve as something that folks can link to in lieu of (or in addition to) a website. That reminds me, we should consider adding a slot for Sponsor links (Patreon, GitHub Sponsors, etc) — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#4>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPV5ZQTTDAAAPS5BAFNWBLQHMDX3ANCNFSM4IH7ZEVQ> .

[taurean]

@tatianamac love the sponsor link idea.

How did we feel as a group with that codepen mockup thing I did? Should we keep tweaking that or should I do something in a similar style for standalone pages?

[BboyAkers]

Can you link the codepen mockup please?

[taurean]

https://codepen.io/taurean/pen/eqJOVy

[BboyAkers]

I dig it! Sorry for the late response. I can get cracking on building out some stuff if we get some tasks labeled. What do we want to use for the frontend?

[tatianamac]

Love it! I did a small remix on it. Mostly trying to make it more concise. I am trying not to get too precious about the design right now so we can reexamine it after we do some testing down the road.

https://codepen.io/tatianamac/pen/yLBKYaP?editors=1100

[cdvillard]

@taurean, I'm digging the general style of your mockup as an aesthetic, but I agree with @tatianamac's point that this can be always be rehashed down the road.

That said, assuming the attention is turning back to architecture, it sounds like Eleventy will be the SSG of choice. Is there a consensus on that? If so, how should we handle data?

(Also, sorry if I'm sounding off too much. I'm into the project, still learning the etiquette of these sorts of greenfield open-source projects.)

[BboyAkers]

Ya'll want to hop on a slack/skype/discord call? If so email me at me@austinakers.com