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

Identify application settings #30

Closed
orvn opened this issue May 12, 2021 · 2 comments
Closed

Identify application settings #30

orvn opened this issue May 12, 2021 · 2 comments
Assignees
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week kind/architecture Core architecture of project need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up status/in-progress In progress

Comments

@orvn
Copy link
Collaborator

orvn commented May 12, 2021

In addition to the model for projects/entities, a data structure is needed to set parameters around the application's functionality.

This should be extensible, and should include a list of required settings.

Some of the settings that will be proposed in this issue will be quality-of-life in nature; i.e., they won't be absolutely necessary for this instance of the project (however, it's good to think of them in advance to ensure the most extensibility).

@orvn orvn self-assigned this May 12, 2021
@orvn orvn added dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week kind/architecture Core architecture of project need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up labels May 12, 2021
This was referenced May 17, 2021
@orvn
Copy link
Collaborator Author

orvn commented May 19, 2021

@jessicaschilling: Some of these are simple checkers to enable/disable a feature we're already building. Those should be pretty straightforward. Others are more of an extension of the app for forking/future-proofing.

I don't know how many of these we'll have time to implement, but I'm writing them out as we've been thinking of them (the list below also covers the topics we've discussed on our calls with you, as well as within the development process).

I'll add a few more after doing a once-over of the app, and then I'm thinking we can convert them into checkboxes and you can check off which ones you feel are absolutely critical?


  • Setting: Entity term
    • The name for a singular entity (default = project)

  • Setting: Primary category
    • In operations where only one category must be used, which one should be treated as primary? This specifically applies to the segment chart

  • Setting: Exclude singulars
    • Skip from the ecosystem index directly to external resources (if selected, this version of the app wouldn't compile singular pages at all)

  • Setting: Enable embedded view
    • If this is selected, the site will serve up an embeddable object, for inclusion in 3rd party web pages

  • Setting: Use internal header and footer
    • Uses the header and footer content specified within this app, not an external source

  • Setting: Singular common button
    • Set the text and path of the button that appears on each Singular page (e.g., "Explore ecosystem")

  • Setting: Default view
    • Default to list view or grid view on the index page?

  • Setting: Hide non-default view
    • Disable grid view or list view, depending on which is selected for the default

  • Setting: Chart
    • Show or hide the segment chart

  • Setting: Featured slider
    • Show or hide the featured slider

  • Setting: Breadcrumbs
    • Show or hide the breadcrumbs

  • Setting: Control search bar
    • Show search on index page only / filters panel only / both / neither

  • Setting: Enable link icons
    • icons (ideally SVG) for each link type

  • Setting: External links new tab
    • Toggle if external links open in a new tab

  • Setting: CTA new tab
    • Toggle if CTA area opens in a new tab

  • Setting: CTA button text
    • Default text for CTA buttons (case study)

  • Setting: Open video in modal
    • Toggles whether the video is played in its container in the page layout, or if it opens in a modal (or even if it links off-site)

  • Setting: Singular tag links
    • Toggle whether tags on a singular project page link back to that search state

  • Setting: Reduce transition

  • Setting: Disable pagination

  • Setting: Set num results
    • Set default results-per-page count

  • Setting: Disable num results
    • Disable option to change results per page

  • Setting: Disable sort
    • Disable sorting option for results

  • Setting: Set sort
    • Set default sort

  • Setting: Set default results per page count

  • Setting: Disable filter panel

  • Setting: Hide filter button
    • Hide the button that applies filters (if hidden, filters will be automatically applied)

  • Setting: Show counts
    • Show count (n occurences) next to labels and filters

  • Setting: Alt text for link types
    • Define alt attribute for each type of link

  • Setting: Alt text for media
    • Enable alt attibute for logos and video

  • Setting: Truncate URLs
    • URL gets truncated with elipses, and a tooltip is displayed that shows the full URL

@orvn orvn added the status/in-progress In progress label May 19, 2021
@jessicaschilling
Copy link
Contributor

@orvn Sounds good. Let me know when you're ready.

@orvn orvn closed this as completed Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dif/expert Extensive knowledge (implications, ramifications) required effort/days Estimated to take multiple days, but less than a week kind/architecture Core architecture of project need/analysis Needs further analysis before proceeding P1 High: Likely tackled by core team if no one steps up status/in-progress In progress
Projects
None yet
Development

No branches or pull requests

2 participants