- From: Coralie Mercier <coralie@w3.org>
- Date: Fri, 15 Nov 2019 19:01:34 +0100
- To: Joe Daddario <joe@shrthnd.org>
- Cc: public-website-redesign@w3.org
Dear Joe, Thank you for expressing interest! I have answers for some of your questions and I will follow-up with the rest when I am able. Please, see below. > On 13 Nov 2019, at 18:27 , Joe Daddario <joe@shrthnd.org> wrote: > > Coralie et al., this sounds like a fantastic project. The RFP does a solid job outlining the goals, objectives, and expected outcomes--kudos to the contributors. > > Here are my immediate questions: > > 1. What are the biggest challenges currently faced when administering W3C members and managing W3C group operations? Our current website relies on a solution developed in-house that aggregates HTML fragments coming from different sources (Wordpress, Symfony, manually maintained files, in-house tools, etc.). Maintenance of this "CMS" is difficult, so we are looking for a replacement. Suggestions for a replacement are welcome. > 2. Where/how the current website hosted? Has the organizations business processes and/or technology "stack" been documented? We host the website ourselves and most of the processes are documented. > 3. About how much does it cost (yearly) to operate and maintain the website and related business processes (i.e., hosting, transactional emails, uptime monitoring services, etc.) Have you discussed a specific budget for this project or upper limits for operating costs moving forward? The current maintenance costs are hard to compute as we host the website ourselves. There isn’t a fixed budget, but we think for a project of this magnitude, we may get proposals reaching USD 200K. > 4. Have you had any internal discussion about appropriate CMSs and/or ideal editorial and administrative workflows? We have. We are aware of some of the constraints and advantages of solutions but have not made any resolutions and are expecting the vendors to advise, pursuant to the item “Advice on software” listed under “Consulting” in the RFP. > 5. Besides leveraging an open-source analytics library and MFA based on the webauthn specification, does the W3C have guidelines or preferences related to platforms/technologies? > > 6. How has the legacy website being preserved? (Version control? Database backups? Big ol' zip files on tape-drives in a closet somewhere?) > > 7. Is website content separate from the presentation-layer (the theme and global UI) of the website? It sounds like culling/crafting a good bit of content may be necessary but I'm wondering what could/should be automatically migrated to preserve legacy and save on manual content entry.... I don't see how the final process won't be a mix of both processes. “A mix of both processes” sounds about right. > 7. When the redesigned website launches in Dec. 2020, will this include the areas noted in the RFP as "future phases": Member and team spaces, internal (non-restricted) Work Groups homepages, specifications template, mailing lists archives, W3C Community Groups and Business Groups, wikis? No, but for the phase 1 endeavour, the rest of the site should be taken into account so as to scale well for future phases redesign work. > 8. How will tough decisions be handled? Is the advisory committee purely democratic or is there a single individual who will be responsible for "signing off" on decisions made about the design/architecture/implementation of the redesigned website moving forward? For some tough decisions I may consult internally as appropriate, including with the W3C systems team Lead, the W3C CEO and COO, and the W3C Business Development Lead. Coralie > > Thank you, > Joe Daddario > Resilient Systems, LLC -- Coralie Mercier - W3C Marketing & Communications - https://www.w3.org mailto:coralie@w3.org +337 810 795 22 https://www.w3.org/People/Coralie/
Received on Friday, 15 November 2019 18:01:37 UTC