The vendor is required to provide website is outdated and hosts thousands of pages of content, some of which are redundant, no longer relevant, or do not need to be public.
- The website is a critical tool for both stakeholders and the general public, offering features such as access to online licenses, seasonal reports, regulations, interactive maps, and educational resources.
- The new website will also be scalable, allowing for future growth and technological advancements, ensuring it remains relevant and functional for years to come. 
- The new site should be:
• Modern: updating the design to align with current web design trends and ensuring the website is mobile-responsive, accessible, and visually appealing. updating the architecture and infrastructure in alignment with modern best practices.
• Navigable: identifying and eliminating redundant or outdated content while improving overall site navigation and usability to ensure all content is relevant and up-to-date.
• Efficient: implementing a more efficient backend system to allow for easier updates and content management by non-technical staff.
• Enhance the user experience:  improving site performance, search functionality, and accessibility, ensuring the site is user-friendly for a wide range of visitors, state residents, including all hunters, anglers, and wildlife enthusiasts.
- The office of information technology services (its) maintains high-level administrative access and manages all servers, providing hosting for the current website.
- Development, production, and launch
1. Development and production
a. Content and data migration and management
• Continue to record any new content and data that may have been published prior to the website launch.
• Produce a plan for accounting for every instance of a URL, what URLs need to be 404 not found, 301 redirected, etc., while accounting for the link portfolio for the content that was identified in the initial site scan and any newly publish pages on the current live site.
• Coordinate with agency staff to perform migration of existing content and data, as needed, and based on the proposed content strategy determined in section 1.
• Use consistent templates that support SEO, accessibility, and mobile responsiveness, ensuring that all migrated and new content and data meets quality standards.
• backup existing content and data, and deliver archives that could be accessed, if necessary, in the future.
b. DevOps implementation
• Set up distinct environments for development, staging and user acceptance, and production to ensure that code is properly tested before going live.
• Implement a continuous integration and continuous deployment (CI/CD) pipeline that automates the building, testing, and deployment of code changes to ensure frequent and reliable updates.
• The CI/CD pipeline must include automated testing suites to catch bugs early and ensure code quality before deployment. more on CI/CD preferred best practices listed in 9.14, implementation.
• The process and timelines for deploying changes to development, staging, and production environments, including rollback strategies in case of failed deployments.
• Implement comprehensive monitoring solutions to track the performance, uptime, and security of the website. 
• This must include monitoring for server health, traffic load, malicious attacks and application performance.
• Implement caching solutions, lazy-loading content, and feature throttling for improved performance.
c. Frontend development 
• Develop the frontend of the website using modern, standards-based framework(s).
• Ensure the website is optimized for fast load times and performance, incorporating best practices such as lazy loading, compression, and content delivery networks (CDNS).
• Implement mobile-first, responsive design principles to ensure full compatibility across various devices and screen sizes.
• Accessibility compliance: design with accessibility standards to ensure inclusivity for all users, including those with disabilities. 
• Act compliance statement must be placed on the footer of the site.
• SEO optimization: integrate SEO best practices, such as semantic html, metadata, and structured data, to improve search engine visibility.
• Component-based architecture: utilize reusable, modular components within the framework to improve maintainability and streamline future updates.
• Cross-browser compatibility: test and optimize the website to ensure consistent behavior across all popular browsers, such as google chrome, safari, Firefox, and microsoft edge. 
• Testing must include mobile-specific browsers, like chrome for android and safari for iOS.
d. Backend development and content management system
• Implement a flexible and user-friendly content management system (CMS) that enables non-technical staff at agency to manage and update content easily. more requirements for the CMS are below in 9.14 implementation.
• Create a site structure/backend that requires a single title, meta description, header 1 (h1), header 2 (h2), and canonical tag to be loaded on each page.
• Place schema code with more robust organization info, wiki data, and freebase ids on high value landing pages.
• Provide a data retention and archiving system to support agency.
• Build a content publishing workflow. details of this request are identified below in 9.14, implementation.
• Ability to import content from various sources (json, xml, csv, etc.).
• Integration with third-party applications and various APIs.
• Contains an html and xml sitemap.
• Scalable architecture: design the backend to scale with traffic and data volume, employing practices like load balancing and database partitioning.
• Role-based access control (RBAC): implement RBAC within the CMS to manage user permissions, protecting sensitive areas and ensuring secure content management.
- Contract Period/Term: 3 years
- Non-Mandatory Pre-Proposal Conference Date: June 16, 2025
- Questions/Inquires Deadline: June 23, 2025