Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨ Bring back Grid of the Week #720

Open
Tracked by #899
jefftriplett opened this issue Sep 25, 2021 · 5 comments
Open
Tracked by #899

✨ Bring back Grid of the Week #720

jefftriplett opened this issue Sep 25, 2021 · 5 comments
Assignees
Labels

Comments

@jefftriplett
Copy link
Contributor

jefftriplett commented Sep 25, 2021

I was browsing logs and noticed that our top-10 most-searched-for grids weren't marked to be included in the header, so I added them. Now I'm wondering if bringing back the Grid of the Week (gotw) feature wouldn't be a nice way to highlight some of these.

The homepage exposes a gotw variables and at some point, support was pulled for this. Based on git history in the _homepage.html template, it looks like we could easily support it again. This is an approximation of what the old theme looked like:

  <div class="row">
    <div class="col-sm-4 col-lg-4">
      {% if gotw %}
        <!-- start GOTW panel -->
        <h2>{% trans "Featured Grid" %}</h2>
        <h4><a href="{{ gotw.get_absolute_url }}">{{ gotw.title }}</a></h4>
        <p>{{ gotw.description }}</p>
        <p>
          <strong>{% trans "Packages" %}:</strong> {{ gotw.gridpackage_set.count }},
          <strong>{% trans "Features" %}:</strong> {{ gotw.feature_set.count }}
        </p>
        <!-- end GOTW panel -->
      {% endif %}
    </div>
  </div>

For the curious, here were the top searched for grids:

- https://djangopackages.org/grids/g/cms/
- https://djangopackages.org/grids/g/ecommerce/
- https://djangopackages.org/grids/g/themes/
- https://djangopackages.org/grids/g/calendar/
- https://djangopackages.org/grids/g/wysiwyg/
- https://djangopackages.org/grids/g/admin-styling/
- https://djangopackages.org/grids/g/blogs/
- https://djangopackages.org/grids/g/caching/
- https://djangopackages.org/grids/g/cron/
- https://djangopackages.org/grids/g/crm/
- https://djangopackages.org/grids/g/forms/
- https://djangopackages.org/grids/g/cookiecutters/
- https://djangopackages.org/grids/g/maps/
- https://djangopackages.org/grids/g/websockets/
- https://djangopackages.org/grids/g/mongodb/
- https://djangopackages.org/grids/g/wikis/
- https://djangopackages.org/grids/g/admin-interface/
- https://djangopackages.org/grids/g/reporting/
- https://djangopackages.org/grids/g/messaging/
- https://djangopackages.org/grids/g/storage-backends/
- https://djangopackages.org/grids/g/ticketing/
- https://djangopackages.org/grids/g/webhooks/
- https://djangopackages.org/grids/g/chat/
@jefftriplett
Copy link
Contributor Author

This needs another look but mostly needs a schedule and a plan for announcing weekly grids.

@ryancheley
Copy link
Member

In order to do this we need to determine if #112 is something that needs to be done OR if we should just keep it as is for now. I'm not sure that the refactor that we'd need to do for #112 would be worth it

@ryancheley ryancheley self-assigned this Oct 19, 2023
@ryancheley
Copy link
Member

With the closing of #112 I've started working on this. PR coming soon(ish)

@ryancheley
Copy link
Member

@jefftriplett is there anything left to do for this? I think that 99fda7d completed it

@jefftriplett
Copy link
Contributor Author

It needs some elbow grease and some grid cleanup. Let me push out the last bit of the scoring refactor, and we can try to prioritize this next.

I also ran the whole website through a bootstrap to tailwind scripts, and the results are good, but not quite good enough to move it over. I think that would help to get over my "why is this so hard to style?" thoughts that are tripping me up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🏗 In progress
Development

No branches or pull requests

2 participants