GENERAL: read and adhere to the Technical Restraints

[jdrever]

See https://github.com/jdrever/ShropBotSoc/blob/develop/docs/specification.md#8-technical-constraints

• [PHP 7.3] for deployment to Google App Engine for free hosting.
• [CodeIgniter 4.0.4] has been used successfully in the past and provides long term file caching.
• [Twitter Bootstrap 4.5.2] for responsive layout.
• [Leaflet 1.6.0] for interactive maps.
• [Style Sheet] is taken from https://www.shropshirebotany.org.uk/. The Online Flora is to be consistent with this website, so should where possible reuse the same CSS classes and styles.
• [No database] should be used other than the NBN Web service API, to keep down maintenance costs. Any static data (such as the list of axiophytes) should be hard coded into the application.
• [Commits to Github] since the Society will retain the intellectual property rights over any code produced. So all branching should be on the repository at https://github.com/joejcollins/captain-magenta.git.
• [CI/CD] the develop branch deploys to https://captain-magenta.azurewebsites.net/ on Azure and will be used to review progress.

[charlesroper]

@jdrever

• How hard are these requirements?

• How are decisions made?

• Is Bootstrap 4 a hard requirement or can we use v5 instead, which removes the jQuery dependency?

• How much leeway do we have with the design and CSS?

• Do the wireframes represent the target layout for the various screens? I.e. are we to copy these layouts as-is for now?

• Do we need to setup GitHub actions to deploy to Azure when commits are made to the develop branch?

[jdrever]

Hi Charles,

• How hard are these requirements?

I think we fundamentally need to develop against these requirements in terms of what we are delivering for Shrop Bot Soc (see also specific question about Bootstrap 4 below). I think we need to separate that from the much more creative process we can have in terms of developing our own generic version of the site. While we can absolutely be thinking about that future design, the delivery of the Shrop Bot version needs to come first.

• How are decisions made?

Decision-making about the Shrop Bot Soc version comes from Shrop Bot Soc – if we have any questions about the scope that needs to go back to them in the first instance.

• Is Bootstrap 4 a hard requirement or can we use v5 instead, which removes the jQuery dependency?

I’d be open to going back to Shrop Bot Soc with that question – that seems less fundamental to the scoping of the project than the CodeIgniter/PHP framework requirements (e.g. no impact on hosting arrangements and less risk in terms of increasing complexity of project), but that would be a decision for them with Joe advising them.

• How much leeway do we have with the design and CSS?

In terms of what we deliver for Shrop Bot Soc: I think the requirements doc is pretty clear: “Style sheet: is taken from https://www.shropshirebotany.org.uk/. The Online Flora is to be consistent with this website, so should where possible reuse the same CSS classes and styles.” Again, I would differentiate between delivery for Shrop Bot Soc and what we might want to create for a more generic deliverable, where we can be a lot more creative.

• Do the wireframes represent the target layout for the various screens? I.e. are we to copy these layouts as-is for now?

Yes. If we have areas of uncertainty (e.g. what is appropriate for a tablet screen size) then we go back for clarification. We need to keep things as simple as possible.

• Do we need to setup GitHub actions to deploy to Azure when commits are made to the develop branch? No – my understanding is that Joe has set all that up in his repository, so we just need to commit to that at the appropriate time.

Hope this clarifies things – we can talk further on Monday evening.

James.

From: Charles Roper notifications@github.com Sent: 27 February 2021 17:15 To: jdrever/ShropBotSoc ShropBotSoc@noreply.github.com Cc: James Drever james@careful.digital; Mention mention@noreply.github.com Subject: Re: [jdrever/ShropBotSoc] GENERAL: read and adhere to the Technical Restraints (#30)

@jdreverhttps://github.com/jdrever

• How hard are these requirements?
• How are decisions made?
• Is Bootstrap 4 a hard requirement or can we use v5 instead, which removes the jQuery dependency?
• How much leeway do we have with the design and CSS?
• Do the wireframes represent the target layout for the various screens? I.e. are we to copy these layouts as-is for now?
• Do we need to setup GitHub actions to deploy to Azure when commits are made to the develop branch?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/jdrever/ShropBotSoc/issues/30#issuecomment-787104565, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAPKYJK3KIYYHATBASUUAQLTBESBDANCNFSM4YGCAULA.