When done from
#3,
#4,
#5,
#17,
#33
& release 1.0 for plugins

To avoid cache issues for brand new users who have already used & abused port 3001

paths issue are breaking tons of features
and it seems to have been recently fixed

• Init from new template & migrate everything
• Fix manifest path

It would be awesome as a PWA on desktop 😍

Hi,

First of all, thanks for the awesome job.

It looks that there is a little problem with the dropdowns.
When clicking on a dropdown and hovering another element, the dropdown goes in the "background"

here are some screenshots:

use chalk background

node_modules/webdash: Appears to be a git repo or submodule. immediately after install
same for plugins

Originally reported here

• Use Wifi for now + make sure link is working from webdash
• Use generator + template for api.js
• also files: in package.json
• Design guidelines (colors from CSS, from JS, etc..)
• How to test locally
• update links from webdash <app-about>
• link www-webdash to this doc
• Finalize readme

which aliases to webdash --version

which would serve as an example dashboard

• Would some plugins break if they were accessed simultaneously while being served from a single backend? (maybe webdash-npm-scripts would break?)
• Setup livedemo
• link to subdomain
• run serve on reboot
• Email it to Paul Kinlan
• Add live demo website to webdash.xyz?

if possible

That's an easy plugin that will also be used in the documentation as well to explain to developers how webdash plugins are made

Idea of the plugin is that it reads your README.md (if exists) and then runs it through showdown to show the HTML output, just like in this screenshot

if anyone would like to work on it, let me know ❤️

For example: boxmeup-ui showed ui

Hello, currently working on a project using MeteorJS

Step to reproduce

meteor npm install --save-dev webdash-package-json webdash-npm-scripts webdash-performance-budget webdash-pwa-manifest

npx webdash serve

Output

In the project

Bug? Or I am doing something wrong?

When I try to run npx webdash serve I get an error saying that there is no package.json file even though there is one in the current directory. I installed webdash and it's plugins through yarn, as I did with the rest of my packages.

OS: ArchLinux 4.15
npx -v: 9.7.1
node -v: 9.9.0
npm -v: 5.7.1

Please let me know what else you need information wise.

Screenshot from Pixel 2

I recently upgraded (through webdash) to the version 1.2.0 of all the packages, and some of them disappeared. Concretely, webdash-npm-scripts and webdash-package-json. Also I don't find the react and react-dom ones, but I'm not sure if those 2 were present before the upgrade. In any case, they're missing.

In the package.json, the dependencies look correct.

"webdash": "^1.2.0",
"webdash-npm-scripts": "^1.2.0",
"webdash-package-json": "^1.2.0",
"webdash-performance-budget": "^1.2.0",
"webdash-pwa-manifest": "^1.2.0",

• https://github.com/jadjoubran/webdash-npm-scripts
• https://github.com/jadjoubran/webdash-pwa-manifest
• https://github.com/jadjoubran/webdash-performance-budget
• https://github.com/jadjoubran/webdash-package-json
• Also add screenshot to every readme
• Setup github repo description/link
• Also document webdash.json
• get feedback from beta testers

readableAssets": {
      "./src/assets/": "/assets/"
}

exposes ./src/assets as /assets/, particularly useful to solve jadjoubran/webdash-pwa-manifest#2 and future related issues

This would also solve #19 and #20 and probably many future issues

• webdash-package-json
• webdash-performance-budget
• webdash-pwa-manifest
• webdash-npm-scripts

They're not needed anymore since #13 is fixed

Mainly because of merging 2 objects using ... which isn't supported on Safari yet

probably needs an npm install --save-dev as well

it seems that it only shows up for the first plugin

When starting the server, change the output from Webdash running on port 3001! to Webdash running on http://localhost:3001/, so it's just a CMD+Click in the CLI to open the page
Also use chalk green bg

• Implement landing page
• Refactor into web components
• Implement grid & responsiveness
• Design review
• syntax highlighting
• Add screenshot to readme.md
• Finalize links
• setup video
• Replace placeholder images with real screenshots
• Test with Lighthouse
• Deploy using netlify
• Test with Lighthouse (hosted version)
• Add favicon
• Fix copywriting
• Test responsiveness
• test on mobile
• Setup domain
• force SSL
• redirect www/non-www
• Add sharing meta tags
• Setup webmaster tools
• Setup Google Analytics
• Design review with @nicolesaidy
• Finalize Mobile version
• Test on extra small mobile devices
• make poster the first frame of the video (vlc)
• review with @nicolesaidy on iOS & Android
• test with beta testers
• Set URL on main repository
• Fix header on mobile
• Finalize copywriting with @nicolesaidy
• Deploy final version
• Use new description of plugins in readme.md

• How it works
• Web components
• Bower & Polymer 2 (🔜 Polymer 3 & npm)
• Link to creating a plugin

allow customizing ports (webdash api and webdash frontend) + reflect on backend.js

For example internal-ip:8080 should not only reflect the port but also use internal-ip rather than hardcoded localhost

After installing when I run npx webdash serve it gives this in terminal Object.entries is not a function

Its a webpack react app directory that I am installing in.

• give a base a repo or yeoman generator which has pre-set configuration, file structure & theme
• define plugin design guidelines (this will be available as a demo once the generator is completed)

Required for #37
Will also help dev teams that plan on running this on their CI or dev server
express docs

• Temporary home for browsing plugins
• Add screenshot + name + description + installation instructions for plugins
• Update all pages linking to it (webdash + www-webdash)
• How can you become verified

Sw registration temporarily disabled until figuring out plugin structure and reaching maturity

Test in create-react-app

Example: in rails projects, bower_components are installed in vendor/assets/components

Especially for .min.js

I think the image talks by itself. Tested on FF 60.0b1 and FF 59.0.1. In Chrome works fine.

And this is how they should look:

this is causing all the icon issues in webdash and webdash plugins

Try the following:

• Try with absolute paths for elements & app + use express static fix if needed
• Another hack could consist of having both load components with ../../bower_components/
• reset playground & make sure latest of webdash is installed (npm) & retry hack
• retry another approach to fix it in api.js. Experiment locally in PWA-workshop first
• revert temporary hack in serve.js
• would moving es6-build/ into the root folder make it work? Test in PWA-workshop sample first
• checkout if polyserve can help
• Ask Polymer team