hi! >From the URL Hadar shared, I believe we are using GCS buckets to host the content. https://cloud.google.com/storage/docs/hosting-static-website has information about hosting static websites. Have we looked at that before? There's a section of that titled "Optional: Assigning pages" which has more information about editing website configuration. (you may need to change some config settings so that GCS knows it's a website before it'll give you those options)
Stephen On Thu, Nov 3, 2016 at 8:16 PM Kenneth Knowles <k...@google.com.invalid> wrote: > This is great. These menus seem really intuitive for finding what you need. > I especially like the clarity in Get Started and Documentation. A pretty > big challenge, since we have <n> runners and <m> SDKs that all need to be > called out prominently in order to let users know what Beam is about. > > I had ~3 thoughts. > > 1. "Get Started > Support " contains mostly things that I associate with > "Community". I would say only the users@ mailing list, StackOverflow, and > to a lesser extent JIRA are user facing, while the rest is contributor > facing. > > 2. "Contribute > Work In Progress" I wasn't quite sure how to interpret > until I clicked in on it. I favor slightly florid vocabulary like "Ongoing > Endeavors" but maybe there is a middle ground? > > 3. The organization of the Contribute subsections seems like it could put > together three sections for guides, miscellany, and promotion. > > Contribute > > Get Started Contributing (was "Contributor Hub", should have the > "starter" content from Work In Progress page) > ---------------- > Contribution Guide > Testing Guide (was "Testing") > Release Guide > -------------- > Team > Technical Vision (optional, from "Contributor Hub") > Design Principles > Ongoing Endeavors (was "Work In Progress") > Source Repository > Issue Tracking (was "Support" elsewhere) > Mailing Lists, etc (include Slack and dev@/commits@ lists) > -------------- > Presentation Materials (was "Talks" but "Talks" sounds like prerecorded > learning material) > Logos and Design > > Kenn > > p.s. I'd love to contribute to solving the /index.html thing. Seems like > something we should be able to engineer our way around. > > On Thu, Nov 3, 2016 at 7:42 PM Hadar Hod <had...@google.com.invalid> > wrote: > > > Hi Beamers! > > > > I'm Hadar. I've worked on Dataflow documentation in the past, and have > > recently started contributing to the Beam docs. I'm excited to work with > > all of you and to be a part of this project. :) > > > > I believe the current structure of the website can be improved, so I'd > like > > to propose a slightly different one. On a high level, I propose changing > > the tabs in the top menu and reorganizing some of the docs. Instead of > the > > current "Use", "Learn", "Contribute", "Blog", and "Project" tabs, we > could > > have "Get Started", "Documentation", "Contribute", and "Blog". > > > > I applied this new structure in a pull request > > <https://github.com/apache/incubator-beam-site/pull/62>, which is staged > > here > > < > > > http://apache-beam-website-pull-requests.storage.googleapis.com/62/index.html > > >. > > If you've worked on the website before, you've probably run into this - > > note that you'll have to append "/index.html" to each URL. > > > > Thoughts? Thanks! > > > > Hadar > > >
