Discussion: Information architecture for jamstack.org v2 about jamstack.org HOT 10 CLOSED

I'd like to add two thoughts here the first one is related to the Resources section, the second one is just a general idea

1. Currently I find the resources section a bit hard to navigate so I think it would make sense to drill a little bit down: there are articles/blogposts, video tutorials, e-books and other resources available. Maybe a subpage per resource would be a good solution?

2. I'd love to see a "journey" added. What do I mean by this I hear you ask? Think about a new comer who googles 'what is the jamstack' and lands on this page (which seems to be the official Jamstack page since it's a .org domain). If such a user arrives today, they get some information and two links. I'd work on providing a better user (first-time user) journey. (This means that you can think about different personas as well, not just the first-timers).

from jamstack.org.

Great @tpiros!

Good food for thought here. We already have the example sites contributed tagged with some of the tools that were used on them. Perhaps we can make these tags navigable somehow.

Some charts and diagrams are likely to be useful too. I've also found these very helpful in my own workshops and presentation.

from jamstack.org.

Totally with you about the resources page, @tpiros! When this site was first assembled, there were few resources out there. These days they are abundant and so need far better organisation. Perhaps that page might have this sort of structure:

• Resources /resources
  • Videos and presentations
    • Featured - a curated selection of of videos and presentations
    • More videos and presentation → /resources/videos-and-presentations
  • Tutorials and training
    • Featured - a curated selection of of learning resources
    • More tutorials and training → /resources/training
  • Articles
    • Featured - a curated selection of of articles
    • More articles → /resources/articles
  • Add your resources - info on how to add to this list

I'm in favour of having a small number of curated items in each category displayed a little larger than the rest, since this helps make a long list become much more digestible for those trying to get to grips with the content. We could also perhaps rotate those for each view or deploy.

And agreed about the different user needs. Hoping that we can design the content to serve both theses needs, with good summary content, and obvious routes to dig deeper. Always keen to hear thoughts on specifics there. Plus we can consider that lens when we start seeing some content and structure arrive on a staging site soon.

from jamstack.org.

Idea to utilize some cool tech for "demo" purposes: Github Action that deploys at least once daily, the code that generates the features does so at random, so daily it will update with a new random selection.

from jamstack.org.

Yeah I like that @colbyfayock. I suggest that we still have a way to mark a resource or example as "featured" or similar, and then the site generator pulls a random selection from that featured pool at build time.

Regular builds both based on when content is updated, and also once or twice a day is all good.

from jamstack.org.

That structure looks great @philhawksworth!

Regarding the user journey, I have a few ideas; Not sure how much of it can be implemented. You could have different routes: is the visitor new to Jamstack? Have they used React? Show Next/Gatsby related resources. But I suppose doing it this way you'd end up having a lot of rabbit holes. (Vue > Nuxt, Angular > Scully, JavaScript > 11ty etc etc).

Another approach would be to clearly define each "component" that the Jamstack has. Static site generation, APIs, Markup, security, Hosting & Deployment and link out from each of these sections to more resources.

I'd also add some flowcharts - and more charts/figures in general! I found that using those during my presentations in slides help!

I'd be more than happy to review any documents that you have (if, publicly available) and send feedback :)

from jamstack.org.

You can see this content structure taking shape in the work in progress along with trying out iteration of the new logo in this site:

https://next--jamstack-site.netlify.com/

More to come.

from jamstack.org.

from jamstack.org.

Thanks @tpiros!

The glossary will no doubt grow over time. And probably get refined based on discussions and trends. I'll aim to have it populated enough to be a useful starting point, and then grow it over time with help.

from jamstack.org.

Closing this discussion now that the new jamstack.org has launched.
Thanks for all the helpful input everyone.

Specific issues, suggestions, and discussions are of course welcome as the site continues to evolve.

from jamstack.org.