New Website #1964
Comments
|
I'm happy to help out where I can. Will clone and check things out. Feel free to contact me to coordinate :) |
|
@hbrysiewicz Good to hear! I've opened some issues on the repository to keep track of everything. Feel free to work on them and submit a PR. |
|
Thank you @angeloashmore for putting this together and thanks @hbrysiewicz for offering to help. We really badly need help on the marketing / website / community side. A few related links:
Is this effort related to the efforts @wikimatze was working on a separate? |
|
@nesquena This is a separate effort as it uses a different build system (Middleman, which uses padrino-helpers, instead of Jekyll) and a different design. I did take some of the Markdown resources from the It's also a bit more simplified version of the current site rather than a complete port with a new design. I feel we can remove some of the cruft of the current site and keep it simple and light. |
|
Hi @angeloashmore thanks for putting up a second design, think now that we have two versions of the old website, we can surely put up either your or mine site. Of course, can you take markdown of my site to your version. I've no problem with it. Beside, middleman would be something new to learn for me. Hope to get it out this year, since I start it last year. Let's finally make a decision about the new website and where we are gone to host it. Best Matthias |
|
@wikimatze I think GitHub Pages will be the simplest approach since we would be hosting the code here anyway. It's also free! 😄 Building and deploying the site is as easy as: middleman build && middleman deployThis will build the site and push to the |
|
If you want to preview the site, check it out here: http://angeloashmore.github.io/padrino-web/ Note: I'm having issues setting up Middleman to build link URLs properly, so you'll need to add |
|
I'll have a look and help porting some of my stuff to your project (I like your design much more the more often I look at it 😄 ). |
|
I ported most of the blog posts to your repository: padrino/padrino-web#4 |
|
@wikimatze @angeloashmore I really like this site, what steps are left for us to be able to deploy this? what content is missing? I think our website badly needs a refresh and I'd like to roughly time it with the release of 0.13.0. Do you have a sense of what's remaining for us to finally get this out the door. Overall, I really like the @angeloashmore work here. Nice job. Do you guys agree @namusyaka @ujifgc @padrino/collaborators ? |
|
@nesquena Not much else is needed:
|
|
@angeloashmore I'll take care of porting the blog posts over to the new site. Anything else you'd need from me to complete the remaining items? Thanks again for helping us have a new and modern site! |
|
@nesquena Awesome! I can complete the other two bullet points later today. There are some other changes I would like to implement down the road (better guide organization, search, …), but its current state is launch-ready. Regarding hosting, how would we go about getting padrinorb.com connected? Should we move the repo to the padrinorb group? |
|
@angeloashmore sweet, will port over blog posts this weekend. Regarding hosting, I will host the site on an existing VPS I have and we will just need to work with @DAddYE to switch over DNS once it's all ready. |
|
One little thing before switching over. http://www.padrinorb.com/ is now indexed by Google and things. Do we just don't care about it or do we add a redirect map for the old URIs? |
|
@angeloashmore @ujifgc we have the blog, guides, pages all here https://github.com/padrino/padrino-framework/tree/master/padrino-docs what should we do with that in contrast to https://github.com/angeloashmore/padrino-web/tree/master/source? I moved over the 0.13.0 related posts to the docs folder here and here |
|
@angeloashmore can you add me as a collaborator to https://github.com/angeloashmore/padrino-web so I can transfer the repo to the padrino org? |
|
Awesome news to see that it is going on with the new website. The point from @ujifgc is a good one: do we care about the google index and write some rewrite rules? Or should we just skip this step and consider the new indexing? |
|
@wikimatze @angeloashmore I think it'd be best if we would setup redirects for posts and guides at least but if that's going to be a huge blocker we should let it go and not let it hold us up for too much longer. I have added a few issues here: https://github.com/angeloashmore/padrino-web/issues in particular about making sure we have the correct content for blog posts and guides. Also about consolidating content. Right now, we have the content in padrino-docs as well as source. I also moved all the latest guides from padrinorb.com (which has separate changes) to this temporary repo. What do you all think is the best way to move this forward? |
|
@nesquena Just added you as a collaborator. Guides/Docs: It seems best to keep guides/docs in a separate repo from the website. The website repo can reference the docs repo as a submodule. This way contributors can maintain docs separate from the website structure (so long as the frontmatter follows a certain standard). URL Redirects: On first glance, it looks like most of the pages will share the same URL as long as the page titles/filenames are the same. We can do a quick audit, but I vote we don't worry too much about it. Or am I misunderstanding what a redirect does? |
|
@angeloashmore I am not able to switch the repo to the padrino org since only the owner of the repo can do that. I have just invited you as a member of our padrino org so you can transfer over the repo. Can you move it over as outlined in that guide? I agree we should make the guides/docs a separate repo. What do you think about having it stored in the padrino-framework repo as it is now in padrino-docs? Or should it be it's own repo. Either way, can you and @wikimatze help merge the blog, guides, etc into a repo which becomes a submodule for the site? |
|
Sorry for the late reply, I agreed. |
|
I disagree on moving guides away from main repository to a separate one. For me it's much more convenient to work with one repository. |
|
I would also would like to have one repository for the website. We could just add a subfolder with the guides/doc and one with posts. |
|
@ujifgc just to clarify, are you recommending we leave the posts/guides in the main repo as it is now and then have this website display the content from that folder? @wikimatze are you suggesting that we keep the website as it is now with guides/posts as part of the website repo or are you saying the website should live inside the padrino-framework repo? @namusyaka which approach did you think made sense? If I could pick, I would say it is nice having the docs in the main repo and then the website in it's own repo which sources the guides / blogs from the main repo but I am fine with any of these approaches. Hoping we can time the release of the new website with 0.13.1 if we can get it ready soon enough. |
|
@nesquena yes. I think website should import main repository and compile it's pages from padrino-docs. If it's inconvenient for the access rights reason, we could move padrino-docs back to https://github.com/padrino/padrino-docs and have it subrepoed to both padrino-web and padrino-framework so the docs are always from one source. |
|
👍 on the idea of having it as a submodule for both padrino-framework and padrino-web so it can be accessed from either source. What do the rest of you think? |
|
@nesquena Just transferred the repo to padrino/padrino-web-new Next steps:
It also looks like padrino-docs/pages is no longer needed. I believe the content is specific to the website and belongs directly in the padrino-web repo. |
|
@angeloashmore Great!
Moved to: https://github.com/padrino/padrino-docs
Done. 82bbd03
Done. padrino/padrino-web@058bbd5 Can you or @wikimatze help with consolidate the blog posts to make sure we don't lose the tags and other metadata in the front matter of the docs posts. The other posts in new-web have some posts missing from the docs though. I moved over the latest 0.13.0 blog posts that were missing to the docs content. Then we need to do steps 3 and 4. |
|
I'm with the submodule approach now, but we need to update the README and explain how to check out the subrepo and how to commit those changes. I preserved the tags (categories) of the posts under https://github.com/wikimatze/padrinorb-website/tree/master/_posts and could check, if they are still existing on the new repo. It seems like we get things get going much faster then the last years - we are actually making bis progress. I can take care of step 4. Think step three shouldn't be a problem in middleman. |
|
It's a bit sad that two people have contributed new & updated websites (already over a year ago) and still nothing changed... http://www.padrinorb.com/ has still the old and outdated website... What's the reason that nobody adopts @wikimatze's or @angeloashmore's design and work to the official website? |
@Kuraiko we are very close now, but have a few more steps before completing the conversion, mostly just ensuring we have all the content in the new website. Would you like to help us get to the finish line? Final steps:
|
|
As soon as everything is ready, feel free to publish on heroku or let me know if you guys need a vps. I’ll then change/setup the dns change and certs (https). — |
|
@Kuraiko thanks for bringing this up. I'll try to work on those things and try to get it ready till Christmas. |
|
@wikimatze we should do it within few days since the current hosting is expiring |
|
@wikimatze Meld dich wenn man dir bei etwas helfen kann! |
|
I'll work on 1. Ensuring all posts are there and preserving the tags. I'll push the changes to https://github.com/wikimatze/padrinorb-website and we can put them later on to the middleman repo. @Kuraiko das erste mal, das ich Deutsch auf github rede :). |
|
@wikimatze ok great thanks, if you can get all the posts with tags correct and then move them into https://github.com/padrino/padrino-docs/tree/master/posts that would be super helpful. @angeloashmore can you help with 2 and 3? |
|
@nesquena I'll put them there, when I'm finished. Can you give me contribution rights? |
|
@wikimatze yep you should have full access now. |
|
@nesquena it is working, thanks. |
|
@wikimatze @angeloashmore @DAddYE We had to switch over the website to the new version:
How do we deploy updates from https://github.com/padrino/padrino-web-new to gh-pages? Looks like it may be as simple as running a rake task in the project? Appears to be working but we need to add the updated posts and guides. |
|
Just wanted to follow up as I figured this out. The site is live and ready to go! /cc @padrino/core-members
Now, changes can be made in padrino-docs and committed. Once changes are committed to that repository, we can run |
|
Since the site is live, are we planning to do some tracking (e.g. Piwik and/or Google Analytics or does github pages offers something like this) or do we not care about it? And how is the API page build? I know it's build on YARD (which was done in the past from @postmodern). Just want to understand how things work. |
|
@wikimatze Yep, we should definitely add GA tracking http://stackoverflow.com/questions/17207458/how-to-add-google-analytics-tracking-id-to-github-pages. That is definitely an important action item.
Good question: http://www.rubydoc.info/github/padrino/padrino-framework appears to be built last on Nov 29th. I think it can be re-built anytime by going to http://www.rubydoc.info/find/github?q=padrino-framework and clicking the "reload" icon. |
|
I clicked "reload" icon and now we got a fresh version under http://www.rubydoc.info/github/padrino/padrino-framework/master. Can we automate this task for every commit we made to the master? Think a github hook should be suitable for this. |
Late last year, a discussion started to create a new Padrino website (#1826). It looks like things have paused since February, but let's pick it up again.
There were discussions to get the site site up with the 0.13.0 release so let's make that the goal.
Repo: https://github.com/angeloashmore/padrino-web
Please clone and try it out.
Current Screenshots
Desktop
Mobile
TODO
See the issues on the repository: https://github.com/angeloashmore/padrino-web/issues
Please let me know if I am missing anything.
The text was updated successfully, but these errors were encountered: