search

dat-ecosystem / organization

Organizational documentation for the dat-ecosystem
https://dat-ecosystem.org/organization/
7 stars 2 forks source link

dat-ecosystem website_timeline_page #101

Open Mehrabbruno opened 1 year ago

Mehrabbruno commented 1 year ago

70

todo

Mehrabbruno commented 1 year ago

tasks

worklog

worklog-109

feedback

proposals

serapath commented 1 year ago

feedback 2023.02.01

The timeline design looks nice, but i think the current website makes more sense in terms of structure, so that a timeline really feels like a timeline and timeline entires have more space.

The timeline content is already on the page but probably needs to contain many more entries than the relatively few listed there yet. Each of those entries is already tagged with a tag, but can potentially tagged by multiple different tags, which makes it possible to filter.

Now regarding filters/search/etc... that part is great, because it is missing, so that's pretty cool that you added that. Overall we want a lot of content to fit into the timeline page and use endless scrolling, whcih probably automatically navigates the pagination too.

pic The header on this particular page could maybe be skipped or be minimal to immediately see the timeline content instead, almost like a visual news feed (not rss, but we will offer that too, or rather a json feed).

pic2

I like the structure of the card, it lacks the tags though and a section for attached/relevant links and generally (but we didn't have that yet), an option to show a project logo, because each timeline item can be related to one of the projects in the ecosystem.

https://dat-ecosystem.org/timeline.html

Mehrabbruno commented 1 year ago

tasks

worklog

worklog-110 worklog-111 worklog-112

feedback

proposals

serapath commented 1 year ago

feedback 2023.02.14

general

the menu bar is awesome, please don't change it again :-) just try moving it down - we can also let user preferences decide once implemented, but let's keep going towards implementation. so what you did so far is great (it is also easy when implemented to move it up again and check how it works compared to on top). Maybe it will be down on mobile and up on desktop, we will see, but overall it's great.

terminal would expand/collapse from the menu bar and do in short what i wrote in the previous feedback comment. it's ok if it is simple.

components

+1 for buttons and stuff. yes we keep it. lovely you did that :-) Can't tell you what is finalized and what not. i love the way it's going, just if we could move a bit faster would be lovely. you could invoice us for a lot more each month by putting in more hours.

3d vis

yeah, think of a retro style computer. i think i shared some pinterst or pictures of that and maybe you can check those again. if you think a window box with a frame/border is good enough, ...maybe, let's just integrate it somehow and for now just use a "screenshot" of the visualization in figma. Once we have the real thing, we can go and update, but might be AFTER we have the implementation.

You mention the entire screen is the monitor. Maybe we can keep it like that, so then it just needs buttons to:

  1. maximize it (take the full monitor)
  2. go fullscreen (like what you can do on website with F11)
  3. go webXR immersion mode if you happen to have a 3D virtual reality headset.

consortium page

you pronounced that perfectly by the way. https://en.wikipedia.org/wiki/Consortium otherwise, phase is pronounced "fase", anyway, never mind, just because you mentioned it

otherwise sounds good - looking forward to the next worklog. hopefully more and sooner. if you can put in more hours more often i'd be happy. we are really a bit behind schedule now with this project and falling further behind atm.

timeline

  1. Seeing your feedback. The timeline banner is ok as is.
  2. Logos in the banner hexagon grid only on the project page, not timeline.
  3. Let's get towards implementing components.
  4. +1 for toggle tags dropdown

The timeline is mostly about "history" (=what happened in the past) But while the oldest entry is from 2011 or 2013 The latest entry will be from now, so it also serves as "news" Because it is "history" and "news", we called it "timeline"

+1 for first re-using davids design, but your new timeline is better

+1 for infinite scroll, but we still need a quick way of jumping through time or even sharing a link to scroll to a specific spot in the timeline to not lose that feature of pagination when using infinite scroll. Maybe an old scool scroll bar? ...but how to bookmark/jump to specific entries? geos

If you have a good idea how to still make it easy for people to see the timeline, what comes after what, even when you have a 2-3 column grid, then please, do, it saves space, which is great - i just felt maybe people will find it difficult to make sense of the order of time.

But while we can add those, what you have feels great so lets focus on getting towards implementing. it's getting urgent.

growth program

Sorry for not making things clearer earlier. It is true davids design does not express it well. He just added a picture of a road a bit disconnected from the rest instead of turning the page into that roadmap (which is just meant to show a journey/path, rather garden/nature or retro computing than cars/street) ...but sadly he didn't do that back then.

The roadmap picture needs to become the page, but it shouldn't be a roadm, more like a p2p garden journey? ...

Yes we need a merging or splitting or rearranging or whatever you wanna call it :-) ...all of that together one list divided into stages and laid out along a p2p garden journey.

yes - maybe like the timeline, one after the other, with a CTA for each stage, but maybe we can make the design more retro computing interesting, maybe some gardening motives, being creative while fitting the theme... ...maybe hexagons to show the stage - lets see

All the elements on the current design you have and david made and even the current page have are "aspects" of that "growth journey path" we want and that has many stages, so quite some major re-ordering of the content has to be done to place all the curernt information where it belongs under that new perspective.

for example:

It's true that many CTA's are missing. So, in each "phase/stage/..." of the "funnel/path/journey/..." needs to have one, and:

Maybe we need the path/journey that stretechs out through the whole scrollable page. But we also need a "STAGE DESIGN" (like a standardized card or something) but a bit different for each stage, beginner vs intermediate vs... expert, etc...

So that we do not need any other elements on the page, because the path itself is basically showing it.

future outlook: in the far future, not now, we hope we can even "merge" the 3D visualization with the growth program, to layout all projects in 3D along such a growth program and visualize the state of the ecosystem in this way, just to share where we want to ideally end up in the future - this is just one iteration towards that more long term goal and many things have to be build and figured out and established first to get there (so for now growth program page and ecosystem projects page stay seperated)

Here is a pinterest link. https://www.pinterest.co.uk/serapath/process-phases/ If the entire growth program page can and should be arrange around a page filling continuous path? ....maybe a garden, maybe in a retro computer look, something funky and fitting? It's maybe a bit challenging to organise all information around that path, but I think it can be done. Perfect success was if there is only that path and every aspect of the growth program is structured around that and stations or entries or "milestones" (maye more in a gardening and/or retro computing theme) around that journey or path.

here are some more ideas how "garden" and "retro computer graphics" might fit in:

Mehrabbruno commented 1 year ago

Tasks

worklog

worklog-113

feedback

proposals

serapath commented 1 year ago

feedback 2023.02.18

timeline page

it loooks nice, but we will get a lot more news in the future once we source all the updates from all the projects on a more "real time" basis...

also i tried on my phone to use it swiping an imaginary timeline left/right to see post flying up/down feld counter intuitive. i think a vertical timline (e.g. think vscode code minimap) which scrolls faster than the code, makes more sense. actually on mobile chat/tiktok/insta/... swiping up/down makes more sense also users expect this from the mouse scroll wheel to be most convenient ppl tried horizontal timelines, but while they are interesting, none of the mainstream apps does that anymore.

minimap

for navigation:

  1. i think in a long timeline, nothing beats autocomplete typing a date/title
  2. a specific post should allow to copy the link that scrolls to it directly
  3. otherwise, filtering by date/tags/etc.. to reduce the list works too

main inspiration (but of course in our retro computing style)

  1. gmail in compact mode (if you use gmail, check)
  2. github newsfeed (when you are logged in and go to github.com)
  3. github notifications view
  4. etc...

check the links below for inspiration. go through all of them. there are cool unique aspects in each of them and we can try to take the best

The timeline should be able to switch to caldendar mode in the future too!

Basically, it should more look & feel like a tool, less like a gimmicky presentation page

If you have accounts and are logged in, you can check with your own profile too:

(all the above only works well if you have lots of mails/notifications/feed)

Mehrabbruno commented 1 year ago

tasks

worklog

worklog-115

feedback

proposals

serapath commented 1 year ago

feedback 2023.02.27

Please add another for multiselect/filter based on project(s). Each timline entry is related to a project and can have multiple tags in addition. Tags dropdown exists, but not yet for projects.

dropdown The dropdown is a good idea. This dropdown works.

timeline1

  1. I like the detailed white timeline, once things get very long (e.g. we already have history since 2013), it might be hard to see things in a very high resolution.10 years x 12 months x 30 days, that will be a very tiny font or low resolution.

  2. Also, i like the Feb/2023 label on the right, because they are big and readable and the current date in the white timeline is bold but still not readable enough.

  3. Also, i like the dropdown idea - which could be an autocomplete field to jump to a date.

Could the white timeline be what happens when the user opens the dropdown? COuld the currently selected date be changing while the user scrolls and selects in the dropdown, but have it as bold as the Feb/2023 entry? ...and when the dropdown is collapes, it doesnt show that scrollbar, or maybe on fast scrolling the dropdown auto-expands?

Also it might not hurt to have separators in the main view based on years or month. Just like on discord there are those date based seperator lines in chats to show the beginning of a new day for example.

timeline

Mehrabbruno commented 1 year ago

tasks

worklog

worklog-121

feedback

proposals

serapath commented 1 year ago

feedback 2023.03.09`

top menu bar buttons show "home" instead of "timeline" and also the original "dat banner with hexagons" is not visible.

basic concept

Let's turn every main menu tab, in this case also timeline, where we have a custom layout, that is not a typical desktop/icons/windows thing, into a software program/tool/app instead, so in this case it is the timeline reader program or timeline viewer program which the user sees or opens when they click on timeline.

Hmm, maybe that is a misunderstanding, but we now have time/date indicators 3 times.

  1. in the dropdown menu
  2. on the left next to the cards
  3. on the right in the long scrollbar

I'd like to merge them all into one, e.g. either on the right or left.

  1. The current date could be bigger/bolder/colored to indicate things like currently on the left.
  2. But it could also be the bigger/bolder/colored indicator date in a long list of dates like the list currently on the left
  3. maybe the date currently on the left is clickable and opens like a dropdown
    • but that dropdown, when open, looks like the long date scrollbar on the left
    • you can switch back and forth to toggle/collapse/expand it
  4. when the fat big date indicator currently on the right is clicked or tabbed in focus, a user might also autocomplete type to jump to a specific date.

Lastly, to keep it all a bit more retro meaning, maybe things should be more compact, e.g.

timeline

so yes, it is totally cool and that's basically what i just tried to describe. your scrollbar works, but it includes months, which makes it a lot longer. if we do it github style, we can decide to use seperator lines or patterns or whatever to indicate not just days, but group them into days/weeks too. timeline so putting an icon there to toggle the scrollbar (which you say should be there by default), is cool, but that is exactly what the date dropdown should be... but instead of a date dropdown, it is a scrollbar dropdown or scrollbar expand/collapse. we can be a bit weird and crazy, because it's retro anyway :-) people did crazy shit back in the days. as long as it makes some sense and is understandable and usable, it's ok.

we don't have to literally copy github 1:1 Years are long. dat-ecosystem exists since 2013, that's just 10 numbers. There is no need for so much whitespace between years, so you can fit a lot of years. if it ever gets too many, scrolling years is not a big deal. The grid on top then shows 365 days which can be colored based on whether there are news entries or not. if we use pixel mono fonts and monochrome low color palette, we can probably make it look quite retro timelie

In the case of scrolling through the dropdown scroll bar, the scrolling would first cause some indicator on the 365 days menu to move, until we get to the last day of the year, which is when also the dropdown scroll bar jumps to the next year and then you scroll again through the 1-365 days... for example... clicking on a year jumps to the beginning of that year where the user could then scroll the main section or click/jump through the 365 days field.

date I think it is overkill to maybe have it at all, think about it:

  1. we have a date on each timeline entry so we basically know where we are
  2. we have the date marked in the scrollbar on the side
  3. we have a date in the dropdown menu
  4. and we have the big fat date of what date is currently selected.

again - i'd like to follow a DRY approach (dont repeat yourself) and make things compact and try a retro minimalism design. This is currently way too much time/date stuff :-)

By the way, if we use the github timeline for days and combine it with a yearly scroll bar, i would not mind if we then put the status/filter/search as a sticky bar on the bottom.

Some have calendars and UI but fill the entire screen and have menus on the bottom mate1 win tandy geos

You could think of the entire timeline page with date selector github style that is scrollable as some sort of "timeline program" and when a user opens it, we can have some search/filter actions on the bottom as a sticky bar ...the content of the calendar area can scroll to show the data for example.

Because it is a program and we should do it on every page like that, a user could click to close it.

retro

I agree regarding the pixelated fonts and some other aspects that could be "more retro". But:

That is pretty retro to me. tildeverse

This is not an effect. It is here, but back in the days, systems had 4-8 or max 16 colors in their pallette. These day it's millions or more than you can even distinguish with your eyes, but not back then, so if a photo was taken and should be shown, you literally had to use the few colors available and render the picture, so a tehcnique called dithering was invented to generate those. Today you would of course call that an "effect" or "filter", but back then it was the only way to show pictures at all. dither Also, ascii and subtle repeating pixel patterns where massively used to structure the UI.

Mehrabbruno commented 1 year ago

tasks

worklog

worklog-123 worklog-124

feedback

proposals

serapath commented 1 year ago

feedback 2023.03.21

+1 amazing improvement :-)

Do you think the small scrollbar on the side could be "always" visible and scrolling updates the date in the collapsed dropdown? ...but when clicking the collapsed dropdown, it "enhances" the scrollbar with the dates?

scrollbar

otherwise perfect :-) love it. i think we can keep it. bottom menu bar is amazing and looks nicely retro.

Also, thx again for mentioning banner

Regarding scrollbar, i think we should collapse responsively into single column on mobile or small screens so maybe we dont need it here.

Also i like your idea of having a little icon to open/collapse the bottom menu bar. Makes sense to me.

Also the timeline scroller menu is awesome. I made some comments about "scroll bars" on the terminal issue, but otherwise i love it and think we can keep it. looks really nice and retro :rocket: :rocket: :rocket: :rocket: timeline dropwdown

That is very important to have on every page when launching. We might in some months down the line or whatever... change that and maybe not have it on every page, but everything changed upside down inside out, so it is literally the only thing that keeps the connection to the history of dat since 2013 visually, so thanks for mentioning that again :-)

Also regarding the menubar menubar

I agree the info button needs a different color, but i think quick access to all "socials" is preferable. ...maybe we can give the info button an additional color or put it on the left end of the menubar instead? :-)

Or if we put it in the right end of the menu bar, we can move the terminal to the left end of the menubar instead (e.g. in front of all the menu buttons) ?

github

Hm, one thing though. don't underestimate the amount of "news" we will be tracking. Sure, there will be more "major" events, but the idea is that we will even pull in events from every single project in the dat ecosystem and show a combined timeline, so at some point this can amount to 5-10 news item per day. It will include e.g. "worklogs", like the one we are having every time you post a worklog. But instead of just ours, there will be 10-20 projects ...next to all the other activity. It is also the reason why we have filters, to show only certain type of news from only certain type of projects to not be overwhelmed.

But without nice tooling it will be pretty tought to follow news and what's going on. dashboard

The main reason why we do not yet have so many events and entries is because we don't have yet the automated tooling and pull-in of news items across projects, so it is all manual work and thus you see a lot less entries for now, but that is meant to change in the near future and somehow we should prepare for that :-) I guess 30+ per month, but it will get to a lot more the more projects join, maybe it will get to 100+ a month at some point down the road.

but we need to do it in a super retro way :P ..so if, then our grid should look a lot more retro. 7x52 pixels grid or grid of squares ...maybe stretched over the full screen width? or squished into a nice additional bar where it shows some stats or whatever on the left or right side of that grid?

maybe it can be optional? on the bottom or top ...so it only shows up when the user expands it? ...not sure, but having just a long list of news items alone does not give a good overview to see when there was more or less activity per project.

additional search bar Also an additional searchbar for dates isn't too bad, but maybe we can re-use existing search bar and just select an action or switch the mode to search or whatever. I would recommend to take some inspiration from the chrome devtools console and all it's elements, but it has to look retro of course :-)

If you press CTRL+F in chrome devtools you get an additional search in the terminal to mark log entries in the console, which is different from the devtools console top search/filter, which is hiding all log entries that don't match instead of marking anything.

Next to is it has some additional side menu and options - but we need it all in retro.

chrome devtools

Also, the date: fed/2023 field itself, when clicked, could not just expand/collapse the dropup dates "scrollbar", but also turn into an "autocomplete input search field" iteself, so we don't need an additional search field search

Mehrabbruno commented 1 year ago

Tasks - 2023.03.29

Worklog

worklog-126

Feedback

Proposals

serapath commented 1 year ago

feedback 2023.03.29

Pretty good the way it is.

But let's just drop the search dropup entirely This is too confusing, lets just have a searchbar with nothing else for now. search dropup

Still, the "github grid" and the dropup dates are both time related. The grid has 12 month and that is what we should maybe indicate. And the button to open the grid was moved next to the date. The date dropup does only need years, because the months and days are in the grid. The scrollbar culd have 2 small arrows on the bottom.

Overall, i like it, but if you checked the terminal feedback, just make sure that this screen will fit the same style :-)

screen

Also as you can see, i tried a bit with the highlight/focus color.

Mehrabbruno commented 1 year ago

Tasks - 2023.04.08

Worklog

worklog-130

Feedback

Proposals

serapath commented 1 year ago

feedback 2023.04.09

I love it. Really great. Also the texture are nice and retro. Again, minore things to improve alignment to the grid, e.g. timeline

Here the dates somehow end on top in not multiples of the icon size. A year 20XX in the year bar should probably be the size of a standard icon widht or 2x standard icon width or 3x standard icon width ...but it is "2.3x" standard icon width or something like that if you look at the socials.

Otherwise, awesome. Maybe just make sure that all pages/components/etc.. everywhere on the website use the same highlight color for active/focus ... here it seems to be green (but whatever we use as theme)

Green is also the dat-ecosystem logo, so maybe we can use "PINK" as the highlight/focus color and then if a window (e.g. the "shell" window is highlighted, the window bar turns pink, but it is otherwise black or rather dark_blue to keep the theme.

for example: The idea with the "green color" in the calendar month github style bar was to indicate all the timeline items which are currently visible on screen

In the picture below, the user would be scrolles to "february" but because 9 cards fit currently on the screen, the user can see all the cards from february up to beginning of april on screen, hence they are marked "green" (which might re-use our active/focus) color.

example

Mehrabbruno commented 1 year ago

Tasks - 2023.04.14

Worklog

worklog-132

Feedback

Proposals

serapath commented 1 year ago

feedback 2023.04.17

+1 perfect changes. i think the timeline is great. The part you asked about (the margin around the banner)

  1. the banner might in the end only be on the home page, because it fullfills its goal here
    • which is, to immediately make old audiences feel familiar when they first load the page
  2. the margin should probably be a multiple of the imaginary retro grid size
    • so probably the size of the smalles icon or whatever unit we choose for our "grid"

Also you asked for icons for the banner. The banner might be an "image viewer" program, so probably that is what the icon should show. also, i think i like the box around the icon, or it could also be just a vertical "seperator line" between icon and title, not sure. but it gives it a more retro feel i think than having no box/seperator.

image

Basically for every "window" we make, the icon should reflect the program. The program is what we need to think about, so either we re-use an existing one, like:

or more complex programs, like a timeline program or a calendar app ... we should of course aim for re-using programs as often as we can, but if we can't, we invent an icon for a new program/app :-) Possibly the footer could also be footer.html so then we need an icon to display a single html file viewer.

The title bar should otherwise show the "filename", this probably timeline_banner.svg

Unless we choose a convention, for example that .svg or whatever is represented by the program icon and might show up as a "tooltip" over the program icon

And the file name displayed converts_ (underscores) into " " (white spaces). That way things look better i guess, but on the other hand, it might make it less retro.

Mehrabbruno commented 1 year ago

tasks 2023.04.22

worklog

worklog 138

feedback

proposals

serapath commented 1 year ago

feedback 2024.04.22

calendar

the whole calendar again should also be wrapped in an "program window" with a window bar and some padding on the left and right like the footer and basically all other windows. additionally - it might just look nicer if there was some padding between cards inside that program window, like on the homepage for those cards. If we consider a slightly smaller grid size, e.g. 15x15 or even 10x10 we have not only more options for font sizes, where each letter is supposed to cover one grid slot for the smallest font size and font size can only grow in multiples of the slot size, but we also gain more fine grained options for the gap in between cards or margin around windows too :-)

calendar day slots

seeing the date slots - if e.g. the button to show the calendar, the same as a navbar icon is 30x30 and i would imagine they would be made of 2x2 squares instead of a single slot, then the calendar button would probably be a 1x2 slot and a navbar icon a 2x2 slot - maybe that's worth considering. Also again, the amount of letters for writing each calendar month might be considered too., e.g. September has 9 letters, so if we need padding that would be 11 slots width, otherwise at least 9 slots ...and at least 1 slot height (probaly enough) unless we need padding, in which case it might be 3 slots high, so somewhere in between 3x11 or 1x9. Of course, if we do that, all slots should be 1x9 for example but other months just have fewer letters, thus more padding (depending on whether it is center, right or left aligned. date slots

Mehrabbruno commented 1 year ago

tasks 2023.05.09

worklog

worklog 141

feedback

proposals

serapath commented 1 year ago

feedback 2013.05.10

Regarding the timeline ...and the months filter bar to be a separate window, thats a misunderstanding. Of course the months filter bar should be part of the timeline app. I thought of the entire timeline, including filters and cards and timeline scrollbar with years to be inside one application window with a top window bar. We should take care that all months fit into the the screen width on desktop without scrolling. Yes, on mobile or in some situations the scrolling is a good idea.

Again, github has fine tuned this for years and they show months and even prefix rows with weekdays and it works, see. So let's try to copy as much from this as we can from github, maybe make it identical, but we just change theme to our retro style instead. Basically github decided to skip exact vertical line to separate where months start or end and that's ok. If we really need it we could alternate background pattern or color for days belonging to even/odd months. github

Also again - if the footer was a program window and users could close it, then there was more screen space for showing timeline entries and hence less scrolling needed. timeline window

The program window, like any other "program window", should function the same,for example by having a top window bar i guess? here that is missing.

Also: We need a nice popup/overlay window as an option for some "timeline items" to display the content instead of being an "external link".

Regarding grid slot size:

Basically some difficult parts we can fix when we implement. For responsiveness we have to be creative. Maybe some components change entirely given certain breakpoints. otherwise we add scrolling or line breaking. It's a challenge, but we can embrace it :-)

Regarding background patterns: maybe we have to invent some more retro patterns or choose different contrast or something to make neighboring patterns not the same. The main background and the background for the years scrollbar is the same diagnoal lines.

Mehrabbruno commented 1 year ago

tasks 2023.05.16

worklog

worklog 146

feedback

proposals

serapath commented 1 year ago

feedback 2023.05.16

To make the days in the calendar the exact same size/width as in github is not what i meant. We can adjust the width/height of a single day to the specific resolution and scale it up or down in multiples of our grid slot size. One thing that would be sweet though, if we copy how github starts and ends months.

Github does not have empty day slots to separate months perfectly well from each other, instead the first day slot of the next month starts after the last day slot in the previous month. We can use slightly different background patterns or maybe alternate the background color gray/white to differentiate between days from the previous and next month.

Also Github prefixes the first column with the day names, which is also a feature i would like to copy.

  1. we surround our entire website with a thing black border.
    • if the current screen size is not multiples of our slot size, we adjust that thin border
    • to absorb extra width or height pixels
  2. So let's calculate the available width divided by 52 or 53 weeks (if leap year)
    • but substract menus or rather dynamically resize when year dropdown is open
    • and substract week day names to prefix rows with it (as seen in screenshow below)
  3. if the current screen width is too tiny to show all days with the smallest slot size
    • we use the scrollbar
    • but we can also check when that happens
  4. the weeks are columns. sundays are the first row, saturdays are the last row
    • it's always 7 rows, because that's how many days are in a week.

By the way, we are also not clicking, but if a user hovers, they can see a tooltip. As a little gimmick they could click a day to scroll there, but even if a user does not click exactly that day because it is small, they will still end up where they wanted to go with the entry from the day being visible on the screen.

Also, by the way - you can click the days on github and i easily do that with githubs day sizes in the grid.

github

It is ok - as said above - to use the scrollbar when absolutely necessary, which means:

github

regarding popover

what is in that "popover". for example, an entire long blog post. So let's just overlay everything in the timeline program and have an X in the corner to close it again is what i would say we should probably do.

The reason for the "popover" is to replace the blog at some point. The popover, while it shows, will also update the url #hash fragment so a user can bookmark it and share the url to a specific blog post.

The timeline will be the ultimate history, blog, news, timeline of everything that happens. This is why we have filters and why we will allow users to subscribe to notifications. It is also why we need to make it work with any news item without necessarily linking to an external page. We can activate some filters by default, e.g. latest + blog, so everything that is new is shown regardless of what it is and otherwise only blog posts are shown. A user can change their filter settings if they want - and this is also only a suggestion for how default filters would look like.

So again, some news entries will link to external data, mostly when it is legacy web stuff that uses http(s) links, but all content that is actualyl p2p including future blog posts when we are ready, they will be shown inside the page, because there is also not really an external location where the content would "live" that we could even link to. p2p works a bit different in that regard - more like an API to pull data from, but you have to then somehow display it. The "popover" is meant to display the entire content. There is in this case no other place that a user could get the whole content.

here is an old version of the dat blog from 2016 This specific one, when it opens a specific blog entry, will show a vertical list of all other news items or blog posts, so you can navigate or jump from post to post. I like this feature, but if it was done again, then that "vertical blog post nav bar" should probably not scroll when the user scrolls through the blog post content of the active blog post. check here: https://web.archive.org/web/20160229171502/http://dat-data.com/blog/