I think the README covers pretty much everything you're probably looking for. https://github.com/apache/thrift-website/blob/main/README.md
Specifically, it contains: 1. instructions on how to set up your local environment with all the prerequisites 2. specific commands to run to test locally 3. explanation about automatic staging of stuff committed to the main branch (so you never actually *need* to build locally) 4. instructions on how to publish the staged site to production On Sat, Oct 31, 2020 at 5:41 AM Jens Geyer <je...@apache.org> wrote: > > Hi, > > Good work! > > Removing the sitemap until we don't have an replacement in place seems not > like a great idea to me. Right, it does look pretty strange now as it is, > but there are certain pages that are either only linked though it, or the > links to these pages are so well-hidden it makes one preferring going > through the sitemap instead to find it quickly. > > Question: Is there any "executive summary" available what I have to install > and do to build the whole thing? > > Have fun, > JensG > > > -----Ursprüngliche Nachricht----- > From: Christopher > Sent: Saturday, October 31, 2020 1:33 AM > To: Duru Can Celasun > Cc: dev@thrift.apache.org ; Mario Emmenlauer > Subject: Re: Your project's website > > It looks like it's published now. Nice. (probably an INFRA person > watching this thread. :) > If so, they might want to fix the default branch in GitBox, so that > the following works correctly: > git remote set-head origin -a > (assuming origin points to > https://gitbox.apache.org/repos/asf/thrift-website) > > On Fri, Oct 30, 2020 at 8:19 PM Christopher <ctubb...@apache.org> wrote: > > > > Everything looks okay to me on the staging site. I see you pushed the > > asf-staging branch to the asf-site branch, but the main site didn't > > publish. > > I think you will have to put in a ticket with INFRA to disable CMS > > now, and use the asf-site branch from this repo. > > > > Once it works, you should be able to tell that the site is drawing > > from git, and not CMS, because: > > > > 1. I added "Accumulo" to the "Other Apache projects using Thrift" > > section of the about page, and > > 2. The new .htaccess file should force a redirect from > > http://thrift.apache.org to https://thrift.apache.org > > > > I can see both of these on the staging site, but not yet on the main > > site. So, INFRA will probably need to switch you over. > > > > Follow-on things: > > > > 1. You can delete all the CMS website stuff in SVN now > > (https://svn.apache.org/repos/asf/thrift/), and replace it with a > > README saying you switched everything to git. The SVN history will > > still be preserved, but removing it will be less confusing. > > 2. I do recommend that in future, you find a way to remove the > > "snippets" copied from the main repo. That part will be hard to > > maintain in future, and it's probably better to just link to the > > tutorial stuff in the main repo (or move the tutorials to the website > > and remove them from the main repo). It also requires a live > > connection to test the site locally (and might even trigger rate > > limiting for unauthenticated users), so it's not very reliable. > > 3. You can probably just remove the sitemap page... it's not very > > useful, and doesn't look very good right now. If you want a "standard" > > sitemap.xml, there's Jekyll plugins for automatically generating that, > > but the HTML one isn't that useful. > > 4. Some of the documentation on the pages still refers to the > > lib/paths.pm Perl stuff from CMS. I didn't update those developer > > docs, but they can probably be removed, since the thrift-website repo > > now has a good README of its own. > > > > Christopher > > > > On Fri, Oct 30, 2020 at 6:53 AM Duru Can Celasun <dcela...@apache.org> > > wrote: > > > > > > All right, this should be all done now. > > > > > > https://thrift.staged.apache.org/ > > > https://thrift.apache.org/ > > > > > > I've pushed all branches to the new repo [1] and it seems the Github > > > Action and asf.yml are both working correctly, > > > > > > Christopher, thank you once again for working on this. Please take a > > > look and let me know if anything is wrong or missing. > > > > > > Best, > > > Can > > > > > > [1] https://github.com/apache/thrift-website > > > > > > On Fri, 30 Oct 2020, at 10:36, Mario Emmenlauer wrote: > > > > > > > > Hi guys, > > > > > > > > thanks for the great move forward! Can you send a link to the page > > > > as soon as something can be seen? I'm still pretty new to the project > > > > and might have missed if you sent it already, sorry for that :-( > > > > > > > > All the best, Mario > > > > > > > > > > > > On 30.10.20 11:19, Duru Can Celasun wrote: > > > > > I've created the repo using self-service > > > > > https://github.com/apache/thrift-website > > > > > > > > > > Once I get write access (I'm assuming it's automated) I'll push all > > > > > 3 branches and we can take it from there. > > > > > > > > > > On Thu, 29 Oct 2020, at 20:33, Christopher wrote: > > > > >> I finished the syntax highlighting, but didn't get to the > > > > >> sitemap... > > > > >> I'm not sure it's all that important. > > > > >> > > > > >> I pushed 3 branches to my repo (main, asf-staging, asf-site). Once > > > > >> you > > > > >> get the official repo created, all three branches should be moved > > > > >> over, as-is, in order for everything to work smoothly. You may need > > > > >> to > > > > >> ask INFRA to set the "main" branch as the default branch, though. > > > > >> > > > > >> If everything is working correctly, you should see the site at > > > > >> https://thrift.staged.apache.org ; if that is working correctly, > > > > >> then > > > > >> you can use the _scripts/publish.sh script to push the staging > > > > >> branch > > > > >> to the publish branch (see README for explanation), and then you'll > > > > >> be > > > > >> completely off of CMS and can do whatever you want after that. :) > > > > >> > > > > >> On Thu, Oct 29, 2020 at 4:08 PM Duru Can Celasun > > > > >> <dcela...@apache.org> wrote: > > > > >>> > > > > >>> This looks excellent Christopher, thank you for working on this so > > > > >>> quickly! I'll see if I can create an official repo tomorrow and we > > > > >>> can take it from there. > > > > >>> > > > > >
