Code Monkey home page Code Monkey logo

fluidproject.org's Introduction

Fluid Project Website

Netlify Status

This repository contains the files needed to build a copy of the Fluid Project website, it is not an immediately deployable version of the website. 11ty is used to build the site from source files.

To Build Locally

  1. Get the required node modules: npm install
  2. Run 11ty from the fluid-website directory npm run start.
  3. Open http://localhost:8080/ to see the website.

To build locally using Docker

You can serve the website from a Docker container.

Once you have Docker installed, run the following commands to build a Docker image and start a container:

  • Build the image: docker build -t fluidproject .
  • Run the container: docker run --name fluidproject -p 8000:80 fluidproject

The website will be available at http://localhost:8000

If you make changes to the website, repeat the steps to build the image and start a new container.

To deploy to a personal webserver

  1. Run: npm run build
  2. Copy the contents of ./_site/ directory to your server.

Notes

  • Modifications can be done to any source file or directory except for the contents of the _site directory.
  • The _site directory is not versioned since it contains the generated output made by 11ty from the source files, and the files in _site are overwritten at build time.
  • The changed source files in _site directory gets overwritten at build time.

License

The Fluid Project website is available under Creative Commons Attribution License.

fluidproject.org's People

Contributors

aashimgarg avatar acheetham avatar blueslug avatar chosww avatar dependabot[bot] avatar github-actions[bot] avatar greatislander avatar gtirloni avatar jhung avatar jobara avatar sachin10101998 avatar waharnum avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fluidproject.org's Issues

Link to Privacy Policy

Is your feature request related to a problem?

There is no direct link to the Privacy Policy.

Describe the solution you'd like

We should add a link to the Privacy Policy, probably in the footer.

Poor UI for the navigation links on Mobile view

Is your feature request related to a problem?

Viewing https://fluidproject.org/index.html on mobile device renders text contents of nav links very small.This leads to low accessibility and poor UI.

Describe the solution you'd like

The Nav links should collapse into something like hamburger menu.I think with a collapsible menu,the nav links can easily be viewed and accessed.

Describe alternative solutions you've considered

A menu button that displays all the nav links and collapses them based on user preference

Update references pointing at the "master" branch to now point at "main"

Describe the bug

Now that we've updated the default branch name to "main" from "master" we need to update CI and other references to point at "main" instead.

Expected behavior

CI should run on pushes and PRs to the "main" branch. Other references to master should be replaced to main as needed.

improving the visibility of navbar active tag

The navbar tag element ui can be optimized so that the active tag can be visible to the user and also it also matches with the website theme. @jobara if it looks good then it can be improved according to your point of view.

Describe alternative solutions you've considered

the current active hover color can be changed to the current theme as it will match the current website theme.
Current navbar active tab view
old

updated view with the matching website UI
updated

Is github code latest?

Describe the bug

I had started working on the fluid project and wanted to simply extract every file(that are html,css, js files) and then convert them into my own custom made website(completely identical to the original fluid website) and then migrate it to Hugo.
While trying to understand the code,I made a local folder and started recreating the project but the index.html file in the fluid repo is somewhat different to what is hosted on fluidproject.org/index.html
I believe the code on github is not the latest,though there are very minor differences.

Screenshots

Though this is a minor issue that displays Learn More link ahead of the first line but its different than the actual fluid website where there is a link only ahead of the second line
fluid

Desktop

  • OS: Windows
  • Browser : Chrome
  • Version 80

Additional context or notes

I believe that issue is the version of the github code,apologies if I am wrong.

Add analytics tracking code

Add this code to the section:

<!-- Matomo -->
<script type="text/javascript">
  var _paq = window._paq || [];
  /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
  _paq.push(['trackPageView']);
  _paq.push(['enableLinkTracking']);
  (function() {
    var u="https://analytics.inclusivedesign.ca/";
    _paq.push(['setTrackerUrl', u+'matomo.php']);
    _paq.push(['setSiteId', '7']);
    var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
    g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s);
  })();
</script>
<!-- End Matomo Code -->

The upper line of the link collides with the fluid community icons.

Describe the bug

When we click the fluid community icons , the upper line of the rectangle enclosing the link collides with the icons.

To reproduce

Steps to reproduce the behavior:

  1. Go to https://fluidproject.org/
  2. Click on Fluid community web icon
  3. See error

Expected behavior

The upper line of the rectangle enclosing the link should not collide with fluid community web icon

Screenshots

Screenshot from 2020-02-26 22-42-51

Desktop

  • OS: [Ubuntu 18.04 ]
  • Browser [e.g. chrome]

"UI Options" of navigation bar splits into UI and Options in mobile devices.

Describe the bug

"UI Options" of navigation bar splits into UI and Options in mobile devices making it look like News Options.

To reproduce

Steps to reproduce the behavior:

  1. Go to floeproject.org on iPhone 5/SE
  2. See error

Screenshots

Screenshot from 2020-03-02 07-08-17

Expected behavior

UI Options should not split and should move together if a new line is to be used to display the whole of navbar items.
Screenshot from 2020-03-02 07-12-29

Desktop

  • OS: Ubuntu 18.04
  • Browser : Chrome
  • Version: Version 80.0.3987.122 (Official Build) (64-bit)

Additional context or notes

The links overlapped when the UI Options link goes into the next line as shown.
The overlapping UI Options and News link, when hovered over, is solved by adding a margin to links.
Screenshot from 2020-03-02 07-20-39

The slider gets covered by the two lines of the input field.

Describe the bug

When we click the slider , the slider gets covered by the input field lines rather it should have more z index so that it should not be covered by the input field lines.

To reproduce

Steps to reproduce the behavior:

  1. Go to 'https://fluidproject.org/'
  2. Go to Adjust text size.
  3. Observe the changes.

Expected behavior

The slider should have more z-index so that the two input field lines should not overlap the slider.

Screenshots

Screenshot from 2020-02-28 23-17-10

Desktop

  • OS: [e.g. Ubuntu 18.04]
  • Browser [e.g. chrome]

Page is not Responsive : not visible on phone

Is your feature request related to a problem?

A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternative solutions you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context or notes

Add any other context or screenshots about the feature request here.

netlify-plugin-checklinks fragment check errors

Describe the bug

Netlify's check-links plugin is complaining about this in many files:

8:37:06 PM:   โœ– FAIL fragment-check dist/news/index.html --> #fluid-web-content
8:37:06 PM:   | operator: fragment-check
8:37:06 PM:   | expected: id="fluid-web-content"
8:37:06 PM:   |       at: dist/news/index.html:4:922 <a href="#fluid-web-content">...</a>

The fragment seems to be located in src/_includes/partials/header.html

Screenshots

https://app.netlify.com/sites/fluid-fluidproject-org/deploys/5f9f4681dc2f17e6f931ba98

CSSMin plugin for grunt.

CSSMin plugin for grunt will be very useful for the code as this repository contains a lot of css content in it.
This plugin is the CSS equivalent of Uglify. It simply gets any specified CSS files and minifies them.

Add the uglify plugin in the gruntfile.js

This plugin is not present in the gruntfile .
This plugin is very much important as it helps to minify or uglify all the javascript code, removing all the blank spaces so that when we request it from the server it takes much less time to compile.And i think that it is very much useful.

API call to fonts.googleapi blocked due to http connection

Describe the bug

The page at 'https://fluidproject.org/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Roboto+Slab:400,300,700,100'. This request was blocked since the content must be served over HTTPS.

To reproduce

Steps to reproduce the behavior:

  1. Go to 'https://fluidproject.org/'
  2. Right-click and Click on Inspect.
  3. Go to Console
  4. See error

Screenshot:
Screenshot from 2020-03-04 06-39-59

Expected behavior

The API call should not be blocked

Technical details

http is not secue and https calls must be based since the base host i.e. fluidproject.org is using https connection and api calls to http cannot be made.

Desktop

  • OS: Ubuntu 18.04
  • Browser: Chrome
  • Version : Latest

remove dark circle from Infusion mug

Describe the bug

We're not exactly sure where it came from, but there's a dark circle on the Infusion Mug drawing that shouldn't be there.

To reproduce

Steps to reproduce the behavior:

  1. Go to the Infusion page

Screenshots

If applicable, add screenshots to help explain your problem.

Screenshot of Infusion page with the Infusion Mug drawing containing a dark circle

Additional context or notes

New SVG image to replace the current one.

Infusion Mug 2-11

Preference Exploration Tool Demo does not contain anything.

Describe the bug

When clicking on the Peference Exploration Tool Demo the link that is opening in the new tab it opens with a page that says error 404 page not found.

To reproduce

Steps to reproduce the behavior:

  1. Go to 'https://fluidproject.org/'
  2. Click on 'View all projects '
  3. Click on "Preference Exploration Tool Demo"
  4. See error

Expected behavior

The link should redirect to a page that should contain some content related to it.

Screenshots

Screenshot from 2020-03-01 23-50-19

Desktop

  • OS: [e.g. Ubuntu 18.04]
  • Browser [e.g. chrome]

The links in the footer collide with the text.

Describe the bug

The links in the footer collide with the text when we click on the links.

To reproduce

Steps to reproduce the behavior:

  1. Go to 'fluidproject.org'
  2. Click on links present in the left side of the footer.
  3. See error

Expected behavior

The links should not collide when clicked.

Screenshots

Screenshot from 2020-03-02 00-04-13

Technical detail

Desktop

  • OS: [e.g. Ubuntu 18.04]
  • Browser [e.g. chrome]

Update NPM dependencies

Describe the bug

NPM dependencies for this project hasn't been updated for a while, which needs some maintenance work.

Additional context or notes

Will update Eleventy to the latest version and update other dependencies as needed.

The problems in PR #35

Describe the bug

The PR #35 has some problems with the anchor tag.

To reproduce

Steps to reproduce the behavior:

  1. Go to home page of fluid project
  2. Change the contrast
  3. The images disapperar but #35 has got it covered.
    But a slight UI error still persists.

Expected behavior

On changing the contrast, rectangular boxes appear behind the anchor tags in the fluid-web-showcase section.

Screenshots

The encircled bits are the errors that occur
ss1
With #51 , I believe I have got it covered.
ss3

Additional context or notes

Please review the changes.

Add Hewlett to funder info

Is your feature request related to a problem?

Hewlett is missing from the funder information.

Describe the solution you'd like

The funder information should mention the Hewlett Foundation who have been providing much of the funding for on going Fluid work.

Adding the social media icons in the footer.

Is your feature request related to a problem?

No this issue is not related to any problem. But by this issue the user can easily come to know more about the floeproject.org and can contribute to it too.

Describe the solution you'd like

We can add three icons or even more :-

  1. Twitter icon :- This will help the user to read the tweets of the the organization.
  2. Github icon :- This will help the user to contribute to the organization directly by clicking on the icon.
  3. Mailing icon :- If the user has any query he can directly mail it to the org.

`cleanall` script fails on Windows

Describe the bug

Depends on #56 . Running the npm run cleanall script on Windows fails and throws an error. See stack trace below:

To reproduce

Steps to reproduce the behavior:

  1. Check out this project
  2. Run npm i, and then npm run build
  3. Then run npm run cleanall
  4. An error occurs.

Stacktrace

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Users\\jhung\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'cleanall'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'precleanall', 'cleanall', 'postcleanall' ]
5 info lifecycle [email protected]~precleanall: [email protected]
6 info lifecycle [email protected]~cleanall: [email protected]
7 verbose lifecycle [email protected]~cleanall: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~cleanall: PATH: C:\Users\jhung\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\jhung\development\fluidproject.org\node_modules\.bin;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Git\cmd;C:\ProgramData\chocolatey\bin;C:\Users\jhung\AppData\Local\Microsoft\WindowsApps;C:\Users\jhung\AppData\Local\atom\bin;C:\Users\jhung\AppData\Roaming\npm;C:\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files (x86)\wp-cli;C:\Program Files\nodejs\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\jhung\AppData\Local\Programs\Python\Python38;C:\Users\jhung\AppData\Local\Programs\Python\Python38\Scripts;C:\Program Files\PostgreSQL\12\bin;;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Users\jhung\AppData\Local\Microsoft\WindowsApps;C:\Users\jhung\AppData\Local\atom\bin;C:\Users\jhung\AppData\Roaming\Composer\vendor\bin;C:\Users\jhung\AppData\Local\GitHubDesktop\bin;C:\Users\jhung\AppData\Roaming\npm;C:\Users\jhung\AppData\Local\Microsoft\WindowsApps;C:\Users\jhung\AppData\Local\Programs\Python\Python38;C:\Users\jhung\AppData\Local\Programs\Python\Python38\Scripts;
9 verbose lifecycle [email protected]~cleanall: CWD: C:\Users\jhung\development\fluidproject.org
10 silly lifecycle [email protected]~cleanall: Args: [ '/d /s /c', 'rimraf node_modules && rimraf dist' ]
11 silly lifecycle [email protected]~cleanall: Returned: code: 1  signal: null
12 info lifecycle [email protected]~cleanall: Failed to exec cleanall script
13 verbose stack Error: [email protected] cleanall: `rimraf node_modules && rimraf dist`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (C:\Users\jhung\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack     at EventEmitter.emit (events.js:223:5)
13 verbose stack     at ChildProcess.<anonymous> (C:\Users\jhung\AppData\Roaming\npm\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:223:5)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid [email protected]
15 verbose cwd C:\Users\jhung\development\fluidproject.org
16 verbose Windows_NT 10.0.19041
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\jhung\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "run" "cleanall"
18 verbose node v12.14.1
19 verbose npm  v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] cleanall: `rimraf node_modules && rimraf dist`
22 error Exit status 1
23 error Failed at the [email protected] cleanall script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

Technical details

Desktop

  • OS: Windows 10

Add the SASS plugin in the gruntfile.js

Adding the sass plugin in gruntfile.js . This could be very helpful as the fluidproject.org contains a lot of css in it.
Sass files compile into well-formatted, standard CSS to use in your site or application.It adds nested rules, functions, selector inheritance, and more to CSS.

The space is left behind when the hide button slides down.

Describe the bug

When we resize the window by decreasing its windows width to its minimum the hide button slides down leaving the area as it was before

To reproduce

Steps to reproduce the behavior:

  1. Go to 'https://fluidproject.org/'
  2. Resize the window width to minimum.
  3. See error

Expected behavior

The hide button should go down with no space leaving behind.

Screenshots

If applicable, add screenshots to help explain your problem.
IMG_20200226_230933 (1)

Desktop

  • OS: [e.g. ubuntu 18.04]
  • Browser [e.g. chrome]

Adding viewport for responsive design of the site.

Is your feature request related to a problem?

The site is not adapted for small/mobile view as the viewport meta tag seems to be missing.
The font size is not relative to the screen and appears to be small at various places. Specially footer.
This is not with regard to Infusion as per the explanation #23 (comment)

Describe the solution you'd like

The viewport meat tag has to be added and code has to be optimised accordingly.

Additional context or notes

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.