New homepage #1
Comments
|
Perhaps a simple GitHub page, like dashing-io.github.io |
|
Can people start collaborating on the wiki for the time being? Content can be ported to github page later. |
|
I'm willing to host/ pay for a domain name. |
|
Might be a bit tricky to have a domain name. testanything.org had problems after some years as someone forgot to pay the domain, and no one knew who to contact. One person was given permission to the nano editor, and when there were problems with the project instead of forking he used the web site to host a new version. Not saying any of this will happen to the dashing project, but I'd be less worried to contribute if I could be sure that the project will be independent. Later if the project gets bigger (and hopefully it will), we can move it under FSF like Jenkins (https://directory.fsf.org/wiki/Jenkins) or create a group like a foundation, as in the Node project (https://nodejs.org/en/foundation/). @maartendamen what do you think if we keep using GitHub for now, during the migration from the old project under this GitHub org? I'm +1 for either setting up a quick Jekyll template and using GitHub pages, or start using the Wiki as @geoaxis suggested. |
|
Hey guys. Shopify will be keeping the |
|
So with the project new name (smashing) I think dashing.io won't be used in the future. Could not see when dashion.io expires through whois. But I think we can start working with GitHub pages now. The org name is SmashingDashboard. So the web site would be https://smashingdashboard.github.io. And we would have to create a repository called smashingdashboard under that organization. Or we could rename the organization to Smashing and just add GitHub pages to the existing smashing repository (as it would serve the content for smashing.github.io). Thoughts? |
|
I couldn't name it Smashing as that Org name was taken. I would much prefer it to be named Smashing though.
GitHub pages would be awesome.
… On Dec 16, 2016, at 1:35 PM, Bruno P. Kinoshita ***@***.***> wrote:
So with the project new name (smashing) I think dashing.io won't be used in the future. Could not see when dashion.io expires through whois. But I think we can start working with GitHub pages now.
The org name is SmashingDashboard. So the web site would be https://smashingdashboard.github.io. And we would have to create a repository called smashingdashboard under that organization.
Or we could rename the organization to Smashing and just add GitHub pages to the existing smashing repository (as it would serve the content for smashing.github.io). Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Organization renamed @tylermauthe. Thanks to the GitHub team :-) the user name was not taken, though I think it was used in the past. Will update the gh-pages branch. You can go to the page http://smashing.github.io/smashing/ and see the old web site. Will try to first update it so that http://smashing.github.io/ displays that web site. Then update name, links, etc. 👍 |
|
Woot!
… On Dec 18, 2016, at 12:58 PM, Bruno P. Kinoshita ***@***.***> wrote:
Organization renamed @tylermauthe. Thanks to the GitHub team :-) the user name was not taken, though I think it was used in the past.
Will update the gh-pages branch. You can go to the page http://smashing.github.io/smashing/ and see the old web site. Will try to first update it so that http://smashing.github.io/ displays that web site. Then update name, links, etc.
👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
I did some basic renaming here: There are more improvements that could be made though. Would also like to see an org wide page for sure... |
|
Neat stuff.
Where is the repo for the site though?
I would like to help with some pull requests (starting with cleaning up
references to Shopify)
…--
Hatim
--
Shahzada Hatim
On Fri, Jan 6, 2017 at 6:46 AM, Tyler Mauthe ***@***.***> wrote:
I did some basic renaming here:
http://smashing.github.io/smashing/
There are more improvements that could be made though. Would also like to
see an org wide page for sure...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEcApmRrL85dk0h9AF08LnsZoAkWZGmks5rPdU1gaJpZM4IvpPZ>
.
|
|
@geoaxis the same repository of the project, but you have to use the branch gh-pages |
|
@geoaxis I'm curious what references you're going to remove... The homage to Dashing, which states this is a fork of Dashing should not be removed. The copyright at the bottom cannot be removed until we redesign the page entirely. We should do the latter, but I don't really want to deny our heritage... Especially not until we've made more substantial changes to warrant that disconnect! |
|
@bruno
Ah, didn't check the branch. Thanks
@tyler
Ofcourse, we must attribute where applicable.
Well copyright on index needs to be changed (as you pointed out). We can
not change the page and force the copyright onto Shopify (unless that is
what Shopify has requested)
Also Shopify name in the MIT license.
…--
Hatim
--
Shahzada Hatim
On Fri, Jan 6, 2017 at 4:08 PM, Tyler Mauthe ***@***.***> wrote:
@geoaxis <https://github.com/geoaxis> I'm curious what references you're
going to remove... The homage to Dashing, which states this is a fork of
Dashing should not be removed. The copyright at the bottom cannot be
removed until we redesign the page entirely.
We should do the latter, but I don't really want to deny our heritage...
Especially not until we've made more substantial changes to warrant that
disconnect!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEcAlivMMyaGf-Y5PWML0MG2sx7jRw2ks5rPlj9gaJpZM4IvpPZ>
.
|
|
@geoaxis Great points! Well said. Thanks! |
|
Hey everyone! great work on this project its great! Hopefully I contribute one day! I was wondering if you still use the dashing generator commands when scaffolding the project? such as dashing generate dashboard name |
|
+1 |
|
Smashing Dashboard website layout proposal (only cover, work in process)... sugestions are welcome! :)
|
|
Looks great! Would love to see this as the new home page. |
|
I absolutely love that design! More please! |
|
Thank you! :) |
|
New version of website homepage... again, suggestions are welcome! |
|
I like it! The search widgets, not sure what it would use to search them. Maybe instead it could be a list of some popular widgets, and a text saying that there are heaps of other widgets available. As a side note, I've been planning to start a separate thread to add screen shots to all widgets in the same page they are listed in the Wiki. Might plan to finish this when we have the new web site, to use the momentum :-) Thanks |
|
Cool @kinow. :) My idea when I think about a search "page" for widgets is to make easy for smashing users found an specific widget... something like Middleman extensions at this link: Then we could use the screenshots to illustrate how to this widgets works. What do you think!? Thanks for you comment by the way! :) |
|
A new version of smashing homepage proposal... |
|
I like the idea of a search box. The only issue is that we don't have any index file, or web service to search for widgets. +1 for the updated design. Thanks!!! |
|
Working at http://bivee.com.br/open-source/smashing/index.html. |
|
Right now the web site is at https://github.com/Smashing/smashing/tree/gh-pages However, we may create smashing/smashing.github.io. This way users won't have to type smashing.github.io/smashing, but simply smashing.github.io. WDYT @tylermauthe ? |
|
If there is no objection, I will create a smashing.github.io repository tomorrow, and will deploy the contnet from the gh-pages website there. @dvinciguerra in that case, you would be able to submit your pull request there. |
|
Site online now at https://smashing.github.io/ (no need to append /smashing/ anyomre). Sources at https://github.com/Smashing/smashing.github.io The content is served from master branch (this is a organization website). In case someone suggests a solution using a static site generator (which I think could be a good idea) we would have to use another branch for the sources, like |
|
Also protected the current gh-pages branch in this repo, to prevent incorrect updates happening here :-) |
|
Thanks @kinow :) |
|
Thanks @kinow and @dvinciguerra! You guys rock. I'd love to get the new designs onto the new site and start linking to that everywhere. Cheers! |
|
Indeed @tylermauthe ! @dvinciguerra if you submit a pull request to the new smashing.github.io repository, we can review, merge, update the site :) |
|
@kinow and @tylermauthe... I working on the new version of homepage in a forked repository... Follow this repository to more news about the dev process: Best, |
|
@kinow and @tylermauthe... almost done!
Is it ok? Any comment? Best, |
|
This looks awesome! Why hasn't this been merged yet? |
|
When is this getting merged in? |
|
@RonanC thanks! I fixed last week some UI and Jekyll issues. At now the new website implementation is able to be merged. I will submit today a PR. |
|
PR submitted Smashing/smashing.github.io#2 |
|
I think this PR could be closed :) |
|
Thanks @kwent, you are correct. PR was submitted and merged. Closing now. |
The fork will probably need its own homepage
The text was updated successfully, but these errors were encountered: