jwwheeler commented

(Migrated from gitlab.com)

Summary

<!17.0 migration by porting the flocktofedora.org content into Fedora's static website using Nuxt, DecapCMS and Weblate on fedoraproject.org.

Background

<!2034-2022, the Fedora homepage website was completely revamped. This included the migration to a static website using Nuxt, DecapCMS and Weblate. As part of that revamp, it was always believed that the Flock website would one day be moved there ([_see the proof!2038 (i.e. fedoraproject.org/events/flock/2024/). First, you will need to work with community peers in the Websites & Apps Team to build consensus for a namespace dedicated for all events in the Fedora community, something that we could model out for extending later with other events. Once you gain consensus on the approach, migrate the existing flocktofedora.org website content for 2024 into a new page on the fedoraproject.org website specifically for Flock in the year 2024.

A mentor can provide guidance for reaching out to the Websites & Apps Team, working with your community peers, and considering user requirements in the existing website (or what can be simplified/removed).

Details

<!15: Architect your approach.

Familiarize yourself with documentation about the static website toolchain (see GitLab source repository). Learn more about Weblate and the Fedora Weblate server.
Work with the Websites & Apps Team to propose a new namespace on the static site for Events. A page for Flock 2024 will be the first page to go live in this namespace. The old /flocktofedora/ page will be deprecated in favor of this.
Conduct informal user interviews with different stakeholders on needs and requirements of the Flock to Fedora website. What information is useful, what information is important, what information is too much? Collect feedback from users to inform changes and improvements when migrating the existing website. Convert feedback into user requirements/stories.
Propose a timeline for completing the remainder of the project with any key milestones and deadlines noted.

Part 2: Build it, do it.

Make changes to page layout and styling based on user requirements/stories.
Integrate existing content on flocktofedora.org into the static website using Nuxt, DecapCMS and Weblate.
Publish changes in staging, get final round of feedback from stakeholders.
Implement remaining feedback and deploy to production.
Test support for localization.
Work with Fedora Infrastructure to redirect flocktofedora.org to fedoraproject.org/events/flock/2024/.'
Delete the flocktofedora.org website from fedora-websites repo.
Announce the new Flock website to the community in a Fedora Magazine article.

Outcome

The Flock website is easier to maintain and update. It can be done with git or it can be done with a GUI.
The Flock brand is more closely united to the Fedora brand. It also strengthens the search significance of the Fedora website with a redirect of the old site to the new site.

# Summary <!17.0 migration by porting the [flocktofedora.org](https://flocktofedora.org) content into Fedora's static website using Nuxt, DecapCMS and Weblate on [fedoraproject.org](https://fedoraproject.org). # Background <!2034-2022, the [Fedora homepage website](https://docs.fedoraproject.org/en-US/websites/rvmp/) was completely revamped. This included the migration to a static website using Nuxt, DecapCMS and Weblate. As part of that revamp, it was always believed that the Flock website would one day be moved there ([_see the proof!2038 (i.e. `fedoraproject.org/events/flock/2024/`). First, you will need to work with community peers in the Websites & Apps Team to build consensus for a namespace dedicated for all events in the Fedora community, something that we could model out for extending later with other events. Once you gain consensus on the approach, migrate the existing `flocktofedora.org` website content for 2024 into a new page on the `fedoraproject.org` website specifically for Flock in the year 2024. A mentor can provide guidance for reaching out to the Websites & Apps Team, working with your community peers, and considering user requirements in the existing website (or what can be simplified/removed). # Details <!15: Architect your approach. 1. Familiarize yourself with documentation about the static website toolchain (see [GitLab source repository](https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0)). Learn more about [Weblate](https://weblate.org/en/) and the [Fedora Weblate server](https://translate.fedoraproject.org/). 2. Work with the [Websites & Apps Team](https://docs.fedoraproject.org/en-US/websites/) to propose a new namespace on the static site for Events. A page for Flock 2024 will be the first page to go live in this namespace. The old `/flocktofedora/` page will be deprecated in favor of this. 3. Conduct informal user interviews with different stakeholders on needs and requirements of the Flock to Fedora website. What information is useful, what information is important, what information is too much? Collect feedback from users to inform changes and improvements when migrating the existing website. Convert feedback into user requirements/stories. 4. Propose a timeline for completing the remainder of the project with any key milestones and deadlines noted. ### Part 2: Build it, do it. 1. Make changes to page layout and styling based on user requirements/stories. 2. Integrate existing content on `flocktofedora.org` into the static website using Nuxt, DecapCMS and Weblate. 3. Publish changes in staging, get final round of feedback from stakeholders. 4. Implement remaining feedback and deploy to production. 5. Test support for localization. 6. Work with Fedora Infrastructure to redirect `flocktofedora.org` to `fedoraproject.org/events/flock/2024/`.' 7. Delete the `flocktofedora.org` website from [fedora-websites repo](https://pagure.io/fedora-websites/). 8. Announce the new Flock website to the community in a Fedora Magazine article. # Outcome  - The Flock website is easier to maintain and update. It can be done with git or it can be done with a GUI. - The Flock brand is more closely united to the Fedora brand. It also strengthens the search significance of the Fedora website with a redirect of the old site to the new site.

jwwheeler commented

2024-05-15 06:22:04 +00:00

(Migrated from gitlab.com)

changed due date to July 12, 2024

jwwheeler commented

2024-05-15 06:22:05 +00:00

(Migrated from gitlab.com)

added to epic &1

MoralCode commented

2024-05-30 19:43:43 +00:00

(Migrated from gitlab.com)

added #21 as child task

MoralCode commented

2024-05-30 19:43:53 +00:00

(Migrated from gitlab.com)

added #22 as child task

MoralCode commented

2024-05-30 19:44:13 +00:00

(Migrated from gitlab.com)

added #23 as child task

MoralCode commented

2024-05-30 19:44:23 +00:00

(Migrated from gitlab.com)

added #24 as child task

MoralCode commented

2024-05-30 19:44:29 +00:00

(Migrated from gitlab.com)

added #25 as child task

MoralCode commented

2024-05-30 19:44:37 +00:00

(Migrated from gitlab.com)

added #26 as child task

MoralCode commented

2024-05-30 19:44:41 +00:00

(Migrated from gitlab.com)

added #27 as child task

MoralCode commented

2024-05-30 19:44:52 +00:00

(Migrated from gitlab.com)

added #28 as child task

MoralCode commented

2024-05-30 19:44:56 +00:00

(Migrated from gitlab.com)

added #29 as child task

MoralCode commented

2024-05-30 19:45:05 +00:00

(Migrated from gitlab.com)

added #30 as child task

MoralCode commented

2024-05-30 19:45:12 +00:00

(Migrated from gitlab.com)

added #31 as child task

MoralCode commented

2024-05-30 19:45:21 +00:00

(Migrated from gitlab.com)

added #32 as child task

jwwheeler commented

2024-05-31 19:32:46 +00:00

(Migrated from gitlab.com)

mentioned in issue #9

jwwheeler commented

2024-05-31 19:42:59 +00:00

(Migrated from gitlab.com)

assigned to @MoralCode

jwwheeler commented

2024-06-01 02:07:27 +00:00

(Migrated from gitlab.com)

@darknao @gregory.lee.bartholomew I wanted to bring this issue to your attention as an early heads-up. @MoralCode will work to migrate the flocktofedora.org website to the fedoraproject.org website with a target go-live date for July 12th, 2024. He outlined a plan for how to do this using child tasks from this GitLab issue. You can share general feedback in this issue, or you can comment on any of the child tasks linked from this issue if you have feedback or questions about his plan and timeline for the project.

@darknao @gregory.lee.bartholomew I wanted to bring this issue to your attention as an early heads-up. @MoralCode will work to migrate the `flocktofedora.org` website to the `fedoraproject.org` website with a target go-live date for July 12th, 2024. He outlined a plan for how to do this using child tasks from this GitLab issue. You can share general feedback in this issue, or you can comment on any of the child tasks linked from this issue if you have feedback or questions about his plan and timeline for the project.

MoralCode commented

2024-06-03 14:41:00 +00:00

(Migrated from gitlab.com)

@jwflory is there a FLOCK SIG, design, or other groups that should be aware of/approve/give feedback on this? im specifically working on #22 (the namespacing) right now but also trying to gather a list of stakeholders for later

also was this change something that the FLOCK team is aware of/something that originated from them? or would this need approval by them since their website is kinda getting scooped up into the main site?

@jwflory is there a FLOCK SIG, design, or other groups that should be aware of/approve/give feedback on this? im specifically working on #22 (the namespacing) right now but also trying to gather a list of stakeholders for later also was this change something that the FLOCK team is aware of/something that originated from them? or would this need approval by them since their website is kinda getting scooped up into the main site?

MoralCode commented

2024-06-03 15:22:22 +00:00

(Migrated from gitlab.com)

marked this issue as related to fedora/design/team/wwwfpo-2022#15

MoralCode commented

2024-06-04 17:48:06 +00:00

(Migrated from gitlab.com)

success criteria:

finish the redesign efforts (merge the current content and structure with the start of the redesigned effort)
migrate the redesigned flock site to nuxt layers to separate the build process per the web team suggestions
redirect the flocktofedora.org site to the completed fedoraproject version

success criteria: - finish the redesign efforts (merge the current content and structure with the start of the redesigned effort) - migrate the redesigned flock site to nuxt layers to separate the build process per the web team suggestions - redirect the flocktofedora.org site to the completed fedoraproject version

MoralCode commented

2024-06-04 17:59:47 +00:00

(Migrated from gitlab.com)

marked this issue as related to #53

jwwheeler commented

2024-06-05 01:20:09 +00:00

(Migrated from gitlab.com)

@MoralCode There is not a Flock SIG or working group. There is a team, but it is informally structured. As Fedora Community Architects, the flagship event falls in our domain to organize and build a team of volunteers around. Otherwise, the list I already provided in #23 for user interviews is the best place to start from.

jwwheeler commented

2024-06-05 01:21:32 +00:00

(Migrated from gitlab.com)

changed due date to August 09, 2024

jwwheeler commented

2024-06-05 01:21:39 +00:00

(Migrated from gitlab.com)

changed health status to on track

changed health status to **on track**

jwwheeler commented

2024-06-05 01:30:26 +00:00

(Migrated from gitlab.com)

Sprint themes

Sprint 2: Research

#21, #22, #23. End-goal for this sprint is to be ready to complete #24.

Understand the tool chain. Review the feedback from the Websites & Apps Team. Set up a reusable development environment on your machine. Explore Nuxt Layers for improved build time. Focus on building the timeline and proposal for work required to complete the project.

Sprint 3: Hacktime

#24, #25, #26. End-goal for this sprint is to deploy to a staging environment to complete #27.

Implement changes. Hack on the site and work toward a MVP.

Sprint 4: Iteration & deployment

#27, #28, #30, #31, #29. End-goal for this sprint is to launch the site in time for Flock.

Sprint 5: Outreach

#29, #32. Project complete.

Spread the word. Announce the new site and its features. Use it as additional promotion for Flock. Share plans on how to create event websites like it in the future.

# Sprint themes ## Sprint 2: Research #21, #22, #23. End-goal for this sprint is to be ready to complete #24. Understand the tool chain. Review the feedback from the Websites & Apps Team. Set up a reusable development environment on your machine. Explore Nuxt Layers for improved build time. Focus on building the timeline and proposal for work required to complete the project. ## Sprint 3: Hacktime #24, #25, #26. End-goal for this sprint is to deploy to a staging environment to complete #27. Implement changes. Hack on the site and work toward a MVP. ## Sprint 4: Iteration & deployment #27, #28, #30, #31, #29. End-goal for this sprint is to launch the site in time for Flock. ## Sprint 5: Outreach #29, #32. Project complete. Spread the word. Announce the new site and its features. Use it as additional promotion for Flock. Share plans on how to create event websites like it in the future.

MoralCode commented

2024-06-12 14:36:56 +00:00

(Migrated from gitlab.com)

added #69 as child task