Skip to content

Add herow source #552

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

Merged
merged 14 commits into from
Jan 30, 2020
Merged

Add herow source #552

merged 14 commits into from
Jan 30, 2020

Conversation

niallzato
Copy link
Contributor

Proposed changes

Reviewing and setting the Herow source live.

Included the Markup document.
Edited the sources.yml file, not too sure if this required though.

https://segment.zendesk.com/agent/tickets/365689
https://segment.atlassian.net/wiki/spaces/DC/pages/347111764/Herow+-+Private+Building

Copy link
Contributor

@sanscontext sanscontext left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be converted into markdown. Currently a lot of it is in HTML, and it lacks the correct frontmatter.

@@ -285,6 +285,19 @@ items:
url: ''
categories:
- Server
- display_name: Herow
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was this pulled using make catalog?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh did not realize the correct way to do this. This is a dev center source (currently have it set to private): https://app.segment.com/partner-portal/source/herow/json

I was thinking it might be best to merge the docs and then do a separate pr for the catalog update. Thinking that the customer can view the docs via the URL (sort of private beta) and then we can set it "live" via the catalog update. But perhaps that is not how this works. Totally open to suggestions on the preferred way to do this :)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We categorically do not publish docs for private beta partners, because we can't see them in the catalog. If they're ready to switch to public beta, then we can publish them.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @sanscontext , Think i confused up this pr kinda badly. Happy to close this and create a new one if that helps.

Soooo, the reason this was initially set to private is because it's part of a stream dev center review. Basically we paste in some json to the dev center to and that's how a stream is created. I set this to private initially to make sure it works. I'll avoid this workflow going forward.

I have now set to live and updated the catalog (hence extra files for review). Thanks!

@@ -0,0 +1,146 @@
# HEROW
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, please look at other docs in this corpus and match the style. This needs at minimum the title: frontmatter set and this line removed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the title, is there any more markup missing? For context this is partner created from this template: https://hackmd.io/TV8cZR6tRnKwGtkvSexeag?both

I have asked for edit access to amend the template but it would be great to get this right at source.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the idea was that we were supposed to add that frontmatter and they'd get confused by it, or possibly that it was in the runbook? But at minimum you need title: and for most of these you might also need beta: true.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh cool, I added the beta flag now too.


With HEROW simple, straightforward SaaS platform, mobile marketers and developers can:

+ Better understand how, when and where their app is being used
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you know what's going on with the spacing here? 🤔

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Didn't spot as it renders fine, but now removed.

@sanscontext
Copy link
Contributor

I think you can actually remove the updated catalog file - Xav was kind enough to add some sorting to it, so it got regenned today as part of that change. :) Otherwise, I just want to make sure that the tables render correctly, and then I think as long as its in public beta, you're good?

@niallzato niallzato force-pushed the niallb/add_herow_source branch from b2e4d3f to ac6c7a7 Compare January 29, 2020 11:34

[HEROW](https://www.herow.io) is a contextual platform for mobile application. Built around everyday behaviors and powered by location intelligence, its one-stop solution allows apps to maximize mobile engagement with their users.

With HEROW simple, straightforward SaaS platform, mobile marketers and developers can:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lines 9 through 17 are marketing content and don't belong in the docs. 🤔 Lets please remove these.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the marketing content, we good to approve and merge 🤞

Copy link
Contributor

@sanscontext sanscontext left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved, thanks for your patience. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants