different pages to display content

[govindgoel]

Please describe the problem (or idea)

As we have a navbar to be added in this #420 so we can think of displaying data on different routes as of navbar, this will surely reduce scrolling on the main page and also it will be more relevant.

Example:
code.publiclab.org/contrib
code.publiclab.org/fto

Like this, and adding about the community, open-source practises on the main page.
@jywarren

---

Thank you!

Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.

To learn how to write really great issues, which increases the chances they'll be resolved, see:

https://publiclab.org/wiki/developers#Contributing+for+non-coders

[YogeshSharma01]

Hello @govindgoel and @jywarren I think we can do this for the contributor's section and the language section of the page

[jywarren]

I'm not against a long scrolling page, as long as our navbar can get us to anchor points like #fto and #contibutors -- how well do you think this works currently, and do you think there are further refinements we can make along those lines?

See how a very long page with anchors works here: https://getbootstrap.com/docs/4.4/components/navs/

What do you think?

Thank you!!!

[YogeshSharma01]

Hi, @govindgoel have you start working on this?

[jywarren]

One idea i had was to create separate pages with each section as a form of documentation -- to show how the code is modular and you can display only one at a time if you like. This would make for much simpler HTML files that might be helpful for debugging, as well as for devs who want to embed this code in their projects and don't want the "whole system" we've created.

Notice we've done a little of this with the "embed" function -- https://github.com/publiclab/community-toolbox/blob/main/examples/embed.html

What do you think of this -- not dropping the full scrolling page, but investing more in the modularity of the system and good documentation?

For one, i'm not convinced the embed page is fully functional. I wonder if we need better tests to protect that functionality?