eka-foundation / website Goto Github PK

On desktop everything goes nicely and headline is smack in the vertical center. On mobile this fails (at least on safari with old iphone) and text is shown on the top of the screen instead.

Zipped video uploaded.
video.zip

This does not happen when the links on the second and third slides are clicked.

Because we are following the full screen "snap" scrolling from section to section, it would be great to be able to entirely prevent freeform scrolling. Is that possible @pdey and does it make sense?

Related with #8

Mikko, since you have control over the domain, can you add/verify the website here if not already done.

Perhaps consider these edits?

“EKA’s research focus on encouraging discovery and learning as a creative process that empowers and inspires people to use technology in a meaningful way.Thriving towards the success of our mission, Everything we do puts the people in the communities first. We are also responsible for technology developers, designers, and other professionals who work with us to make it possible to reach our audacious goals. We thrive to provide inclusive and inspiring career opportunities, where personal and work values are naturally aligned. In addition to the communities we work in, we share the wider concern with the future of key internet technologies, and the way in which such technologies influence people and affect their lives.”

Right now when the person comes to the site, there is a fade-in animation that is applied for texts, but it does it only upon going down the first time. Then after that the text becomes static. We want to get the fade-in effect every time there is a transition to the section where the text is.

On desktop, upon scrolling down, the images fade into the next slide's image, but on mobile, the images don't fade but rather scroll. Should we just scroll the text and keep the image static (perhaps the third one) for mobile?

Right now, the three slide's images are roughly 1MB each, leading to a page load size of around 3MB.

One idea could be to use svg versions of these images to reduce load time. Also, we could then animate the svg's instead of fading one png into another.

With mouse/touch actions we could make certain items appear or disappear.

Just a thought.

Me and @mikkokotila discussed about putting a link to joining the discord channel to contact a real human.
I've already privately shared the discord invite link and we just need to put it on the website.

Right now the full page transition takes place when scrolling with mouse wheel or clicking the dot navigation on the right side of the screen. The current code that does it is here:

<script>
( function( $ ) {
 
  $( document ).on( 'mousewheel DOMMouseScroll', function( event ) {
 
    if ( ( $( '.et_pb_side_nav' ).length === 0 ) || $( 'html, body' ).is( ':animated' ) ) return;
 
    event.preventDefault();
 
    var direction = event.originalEvent.wheelDelta || -event.originalEvent.detail;
    var $position = $( '.et_pb_side_nav' ).find( '.active' );
    var $target;
    
    if( direction < 0 ) {
      $target = $( $position ).parent().next();
    } else {
      $target = $( $position ).parent().prev();
    }
    if ( $( $target.length ) !== 0 ) {
      $( $target ).children( 'a' ).trigger( "click" );
    }
  } );
} )( jQuery );
</script>

Basically it piggy-bags on the automatically created Divi dot navigation, where each page section gets an element in the dot navigation.

We want to extend this script so when a user moves downwards on touch screen, it does the same as mouse wheel.

As evident in the screenshot, the bottom part of the image on the main website is cropped, and should be fixed.

@mikkokotila I was wondering that in the keeping with the spirit of this project, we should think about open sourcing the eka.to website code. One potential issue I see is that if there are security vulnerabilities, they may be exploited.

Another thought might be to look at jekyll, which can be directly hosted within github. The website we have seems to be very well suited to a semi-static/static kind of engines, the kind which jekyll supports. Maybe it is better than going for proprietary/paid softwares (like divi, which we are using right now).

It seems right now, that a significant amount of engineering, design and creative efforts have gone into a website which is:

• not fully functional/has issues.
• seems to be difficult to edit in case modifications are required.

Perhaps we should rethink trading glitz for agility.

Thoughts?

As evident in the screenshot.

Perhaps this is a WIP, but still opening the issue anyway.

The second slide's text breaks at:

• decentraliz--ed on Galaxy S5
• decental -- ized on Iphone X
• decetraliz -- ed on iphone 6/7/8

Maybe there is a way to keep this consistent. Like break it at a certain place in all cases.